Blog module — from writing to publishing in 3 steps | HYPE Foods

The most important thing about a CMS system is not the technology. It is the speed at which an idea becomes a published article.

In most systems it looks like this: log in, find the new post button, fill in 15 fields, select a category from a dropdown menu, upload a title image, set up SEO... only then can you write.

In Modulo CMS, it is different.

Step 1: Open the Editor

Click "New Article" in the admin panel. A TipTap editor opens — clean, full-screen, distraction-free. The left side is your text, the right has only the essentials: name, description, category, author, date, publish/save draft toggle.

The editor supports Markdown syntax — if you type ## Heading, a heading appears. **bold** makes bold text. You can also simply click the buttons in the toolbar.

Step 2: Write

This is the step that most CMS systems get wrong. The editor is either too simple (just plain text) or too complex (full DTP with dozens of options).

The TipTap editor in Modulo CMS hits the sweet spot:

Headings H2, H3
Bold, italic, link
Bulleted and numbered lists
Block quote
Inline and block code
Horizontal rule

Nothing more. Nothing less. For editorial content, that is more than enough.

Step 3: Publish

When you are satisfied, toggle the "Publish" switch and save. Done.

Under the hood: the admin panel saves the article to the database. The public web merges translations and renders content on the fly. No waiting for a deploy.

Time from "new article" to "live on the web": typically less than a minute.

What Happens to the Content?

Each article is stored in D1 with its metadata: title, description, category, author, date, cover image, body in Markdown. The advantage: content is portable, backupable, and readable without the CMS. Your content is truly yours.

Categories and Filtering

The blog module supports categories; on the public website, filtering works in real time — without page reload. The reader clicks a category and the grid instantly filters. This is possible thanks to Vue 3 reactivity.