1Doc corporate website

1Doc builds a digital process platform used by municipalities and public bodies. Solutions ship at a fast pace, and the corporate site is the first door for anyone researching before opening a public tender.

The problem

The site had to keep pace with the product. Every solution released needs its own page — that’s the page that shows up for someone putting a tender together — and a page that only goes live when a developer has spare time goes live after the moment it would have been worth. The project had to take publishing out of the technical team’s path without giving up server-rendered content, which is what makes that page findable in the first place.

What was built

A corporate site in Nuxt with Strapi as a headless CMS. Marketing began publishing solution pages, downloadable material and content without opening a ticket with the development team.

• Complete corporate site, with manageable solution pages
• Strapi configured with the content types marketing actually uses
• Deployment and production environment

Decisions worth knowing

What separates a portfolio from an album of screenshots is the reasoning behind each choice.

1. 01

   Headless CMS rather than a coupled site

   Separating content from presentation is what gave marketing its autonomy back. Strapi holds the solution pages and the material; Nuxt assembles the site from that. Changing the layout doesn’t require migrating content, and publishing doesn’t require a deploy.

2. 02

   Server rendering, because of who the site serves

   Visitors arrive from organic search and from word of mouth inside the public sector. A page that needs JavaScript to show its text starts at a disadvantage in that scenario, so the content is rendered from the very first response.