CEBKUN content system

Make useful Bits.
Ship the good ones.

This guide shows how to create CEBKUN blog posts with local MDX files, keep drafts private, preview them locally, and publish only after the content is ready. The Blog Studio workspace below is an optional offline helper — no CMS account required.

Start the guide Try the offline Blog Studio

Short answer: yes, an offline helper is possible. A browser cannot silently scan or edit a folder beside an HTML file because of security rules. This page can ask you to choose the drafts folder, list its .mdx files, edit them with permission, and download new files when direct folder access is unavailable.

01 · Quick start

Your first CEBKUN post

The normal source of truth is a file in content/blog/. Strapi is not required for blog publishing.

Pick one useful problem

Start with a real question: a setup that confused you, a tool that saved time, a coding lesson, a game design thought, or a digital-life fix.

Copy the template

Copy content/blog/_template.mdx and rename it with a stable filename such as better-downloads-folder.mdx.

Write the frontmatter

Fill in the title, slug, excerpt, category, tags, date, and draft state. Reading time is calculated automatically from the article body.

Write the useful part

Use normal Markdown first. Add a short intro, clear sections, steps, examples, warnings, and a conclusion. Keep the jokes controlled; useful Bits first.

Preview locally

Run yarn dev, open /blog, then check the article at /blog/your-slug.

Publish deliberately

Keep draft: true during review. Change it to draft: false only after the checks pass and the post is approved.

02 · File anatomy

Use this MDX shape

Frontmatter is the metadata between the two --- markers. The article starts after the second marker.

Starter template

---
title: "A useful Bit title"
slug: "a-useful-bit-title"
excerpt: "A short card and SEO summary."
category: "code-bits"
tags:
  - Next.js
  - workflow
featured: false
draft: true
author: "CEBKUN TECH"
publishedAt: "YYYY-MM-DD"
updatedAt: "YYYY-MM-DD"
seoTitle: "Optional search title"
seoDescription: "Optional search description."
coverImage: "/images/blog/example.jpg"
---

# Your headline

Start writing the useful Bit here.

Field rules

title is the visible article title. Make it specific and human.
slug becomes the URL. Use lowercase words separated by hyphens.
excerpt appears on cards and helps describe the article in metadata.
category must use one of the CEBKUN category slugs below.
tags are short, useful labels. Avoid stuffing keywords.
draft controls visibility. Drafts stay out of public pages, sitemap, and RSS.
readingTime is calculated automatically. Do not add it manually.
coverImage is optional. Confirm the path and alt context before publishing.

03 · Taxonomy

Choose a Bit lane

The UI uses branded labels while the file uses stable SEO-friendly slugs.

04 · Writing the article

A reliable post structure

Readers should understand the problem and get a usable next step without digging through a wall of cleverness.

Recommended outline

Opening: what problem are we solving?
Context: why does this happen or matter?
Steps: show the fix in an order someone can follow.
Example: include commands, screenshots, code, or a small scenario.
Caveats: say what can go wrong and who should not use the advice.
Conclusion: summarize the useful takeaway.

Markdown and MDX

GitHub-Flavored Markdown is supported: headings, lists, tables, task lists, links, images, and fenced code blocks.

## Quick fix

1. Back up the file.
2. Change the setting.
3. Restart the app.

```bash
yarn dev
```

<Callout title="Quick Bit" tone="tip">
  Keep the useful part visible.
</Callout>

Callout tones are tip, note, and warning.

05 · Review and publish

Do this before a post goes live

Publishing is a deliberate state change. Keep the source in Git and make the public state obvious.

Content

Does the opening answer the reader's question?
Are instructions tested on the stated stack?
Are facts, dates, prices, and links current?
Is the Taglish voice helpful rather than forced?

Metadata

Is the slug short, stable, and unique?
Is the excerpt useful on a card?
Is the category correct?
Are SEO fields clear without keyword stuffing?

Checks

Run yarn lint.
Run yarn typecheck.
Run yarn build.
Review git diff.
Set draft: false only when approved.

CEBKUN / Local-first authoring

Draft. Validate. Ship useful Bits.

One focused workspace for the whole writing loop: choose your local MDX folder, shape the metadata, write in the source editor, and keep the rendered article beside you while you draft.

Private by default Safe Markdown preview No CMS required

No folder selected yet. Open Drafts to choose a drafts folder or load individual MDX files.

Source editorNo file selectedChoose a folder or file to begin.

Validation waitingNo file

Select an MDX file to validate its frontmatter before publishing.

Post fieldsEdit frontmatter without leaving the workspace.

Title

Slug

Your article will appear here

Choose a draft to keep the writing and reading views in sync.

———

Select an MDX file to preview its article body.