A CMS is only as good as the habits around it. Noderyx CMS gives you drafts, categories, a visual builder, revisions, and backups. This guide turns those features into a repeatable workflow you can run for every article.
1. Sign in and set up the basics
The admin lives at /nodecms. The first account comes from npm run seed, which reads CMS_ADMIN_EMAIL and CMS_ADMIN_PASSWORD from .env. Before writing, check three screens:
- Settings: site name, tagline, meta description, and whether search engines may index the site.
- Categories: a small, stable set of topics. Readers browse by category, so fewer and clearer is better.
- Menus: the primary menu controls the header navigation on every public page.
2. Start every article as a draft
Create a post from Posts > Add new and keep its status as draft. Drafts never appear in the feed, category archives, or at their public URL, so you can save as often as you like.
Write the title and excerpt first. The excerpt appears on story cards and as the lead paragraph, and it is the default search description. If you cannot summarize the article in one sentence, the outline probably needs more work.
3. Structure the body with the Visual Builder
Open the full-screen builder from the editor. Long-form articles need only a few widgets:
Use the desktop, tablet, and mobile previews before you save. Tables and long words are usually the first things to break on a narrow screen.
On this theme, enter code-sample in a Text widget's CSS classes field (under Attributes). It then renders as a monospaced, scrollable code block that follows light and dark mode.
4. Fill in SEO fields deliberately
The SEO title and description are optional. When left empty, the title becomes "Post title — Site name" and the excerpt is used as the description. Override them only when the search-result wording should differ from the on-page wording.
5. Review, then publish
- Read the preview from top to bottom on a narrow screen.
- Check every link and every code sample.
- Confirm the category. The article will appear in that archive.
- Change the status to published and save.
Published posts appear in the home feed, sorted newest first, and in their category archive at /category/<slug>.
6. Edit safely with revisions
Every save of an existing post stores the previous version as a revision. This covers its title, excerpt, content, builder blocks, and status. If an edit goes wrong, open the post's Revisions screen and restore an earlier version. There is no need to remember what you changed.
7. Moderate the conversation
Reader comments arrive as pending and stay hidden until you approve them on the Comments screen. You can reply from the same screen. Messages sent through the Contact page also land there, but they never appear publicly, even if approved by mistake.
8. Back up before big changes
The Backups screen creates a snapshot of all content that you can download or restore. Take one before changing themes, importing content, or running maintenance scripts. It takes seconds and turns a disaster into a minor inconvenience.
Publish small, review often, and keep a way back. That workflow beats any single feature.
Comments