Dynamic Publishing System

Working Example

Agenda at a glance

The challenge: Keeping up with constant agenda updates

At Region One ESC, workshops, events, and conferences take place throughout the week. As each conference approached, staff regularly updated dates, times, speakers, venues and hotel discounts across conference websites. Initially, each department assigned a lead to update its own Google Site. Because the sites lacked shared branding, colors and information hierarchy, web, and print materials often contained conflicting information.

The Solution: The Agenda-at-a-glance module

To address the problem, I created the Agenda-at-a-Glance module, an all-in-one, tabbed element designed to house the critical information for each conference. The module could be placed on any page and, once implemented, became a familiar feature that users came to expect. Eventually, people began asking, “When will the Agenda-at-a-Glance be ready?”

First Hurdle: Nontechnical Competency

The initial version of the module was static. Although many department web leads were comfortable working with rich media in a content management system, they were not technical staff with experience in web development. That limited adoption, created a queue of review requests, and brought the organization back to the original problem: slow, inconsistent updates.

The Solution: Using Google Sheets

I needed a way for users to update conference information without requiring them to work directly with code. Drawing on a previous Webflow project, I developed a system that used Google Sheets as the data source. The module reads a publicly published Google Sheet in CSV format and uses that information to populate the Agenda-at-a-Glance interface. Department leads can update the sheet without touching the code, while my team retains immediate access to the key information and can make changes quickly when necessary.
The agenda module was added to 30+ conference pages, it took much less time to review as I only needed to inspect a couple of cells. Ultimately dev time was cut to 1/4th of the time it took to copy and past ordered lists and containers.


View a live example

Dynamic Sponsor System

The challenge: Keeping up with constant updates to images

During the follow-up to the conference, we solicit sponsors for them. This brings a lot of small challenges like making sure the images are of correct size and quality, what tier of sponsorship are they and so on. The other issue was sizing, many logos were simply different sizes and had no hierarchy, the smallest exhibitor had the same real estate as a top paying sponsor, which led to a lot of client questions and requests.

The Solution: Another publishing solution

Learning from what observed from the agenda system, I made another system specifically for sponsor images, team members would fill in data cells via Google Sheets, and have their images appear on the component above. later on we had a reactive agenda for larger sites that considered tiers and adjusted their hierarchy based on that. it lead to easier uploading and faster uploads as no one had to consider sizes or manual placement.