

The work behind each monthly update
Editors had to enter each page one component at a time. Recurring updates meant repeating that process across the page before the content was ready for review.
Importing a page in one pass
I built a full-page import tool to replace that component-by-component entry, then refined the workflow with feedback from the team using it.
My wider Toolkit work includes React page modules, GraphQL content integrations, and contributions to content validation and the publishing-status dashboard.
Less time spent entering content
The team adopted full-page imports for recurring updates. I estimate that monthly content-entry time fell from 7 days to 1 day. This estimate covers content entry, rather than the entire publishing process.
What changed for editors
A full-page import replaced repeated component entry within the existing publishing workflow.
Before Component by component
- Enter content for a component
- Repeat across the page
- Review the assembled page
After One full-page import
- Import the full page
- Review the imported content
- Continue the publishing workflow
Workflow overview. The 7 days → 1 day estimate covers monthly content entry.
From CMS content to published pages
GraphQL connects structured CMS content to the React modules that render each page. Preview and final content are prepared before Gatsby generates the public pages, giving editors a way to assemble and review recurring updates within the existing publishing workflow.



Built at TVGla with content, design, production, and the technical lead.