DokuNetz Wirtschaft
At DokuNetz Wirtschaft, the public website and editorial work belong together. We develop the platform from drafting through publication, connecting the reading experience to the tools needed to maintain content.
- Challenge
- Publish business content and organise editorial work in one shared system.
- Our contribution
- Information architecture, interface, website and editorial features for roles, versions and publishing.
- Result
- A platform with public article pages and a dedicated editorial workspace.
Different interfaces for reading and editing
Readers want to discover topics and read articles, while the editorial team needs tools to prepare and publish that content. We developed both sides of DokuNetz together, shaping each interface around its task so the editorial work feeds into a coherent public website.
A traceable publishing workflow
An article develops from its first draft through to publication and still needs to be editable afterwards. The management interface supports this process through distinct states, roles and version history, bringing images and structured content together in the same workspace.
Multiple formats on one foundation
Using Next.js and React, we connect the website and management interface with several publishing formats. MDX supports structured articles with embedded content, while RSS, video and podcasts offer further ways in. People who want the newsletter confirm their subscription through a double opt-in process using Resend.
A shared structure for different content
Readers can enter DokuNetz through a topic category, search or an individual article. To help them find related content from there, we developed content types and their relationships as a shared foundation. This structure also accommodates supplementary news formats and connects the different ways into the platform.
An article’s title, category, author, image and publication status are maintained in one place and shared by listings and detail pages. When the editorial team updates a post, these views use the same information. Maintenance therefore stays focused on the content itself rather than requiring the same change in several places.
From draft to publication
The management interface follows a post from an editable draft through scheduled publication to a published article. Roles determine who can use each function, while publication status identifies the version intended for the public website. This connects editorial decisions with the delivery of the content.
After publication, the editorial team still needs room for corrections and additions. Version history preserves earlier versions and allows them to be restored, while images can be uploaded during editing. We connected these functions to the backend logic so text, media and publication state can be handled within the same workflow.
Reading, subscriptions and other formats
Business content does not have to be limited to a text article. MDX allows structured and embedded elements within a post, while the platform also accommodates video, podcasts, RSS and external content sources. Its shared structure provides a framework for these formats without treating each one as a separate website.
The newsletter offers another way to receive posts and stay in touch with the platform. Subscription confirmation uses a double opt-in process with Resend, integrated on the same Next.js, React and TypeScript foundation as the public pages and content management interface.
Design and technology in context.
Next.js, React and TypeScript with MDX, Tailwind and Radix. Roles, content versions and scheduled publication support editorial work.
Planning something similar?
Tell us about your project. Together, we can work out where our design and development skills can support your team.
Discuss a similar project
