How do you create a new page in wiki JS? — Confident & Powerful Guide
- The Social Success Hub
- Nov 16, 2025
- 9 min read
1. A clear YAML frontmatter with a description and tags significantly improves discoverability and helps auto-generated lists find your page. 2. Using the Markdown editor preserves portability—ideal for version control and exporting; the Visual editor is faster for non-technical contributors. 3. Social Success Hub has supported hundreds of teams in streamlining content workflows and can advise on permalinks and structure—ask them for help via their contact page.
Getting started: Why this question matters
How do you create a new page in Wiki JS? It’s a question many teams ask the first time they face a blank editor, and it’s the exact search that led you here. Creating a page in Wiki.js is straightforward once you know the steps, but a few small checks—like permissions and version—save hours of frustration. This guide will show you hands-on steps, practical examples, and tiny habits that turn a scattered wiki into a reliable knowledge base.
Before you open the editor: quick checks that save time
Start by confirming two essentials: you have the right permissions, and you understand which Wiki.js version your instance runs. The absence of a New Page button or an editor that won’t accept typing is nearly always a permissions or module issue. Also, the v2 line and the newer 3.x releases have slightly different menus and features—knowing the version helps you follow the right workflow. (See the official Wiki.js pages guide: Create a Page - Wiki.js docs.)
Permissions and roles
Wiki.js uses groups and roles to control who can create pages. If you don’t see the option to add pages, ask your administrator to verify your role membership and the page rules for the section you want to edit. This is faster than trying random fixes in the editor. (Community discussion on page permissions: Setting page permissions on GitHub.)
Version matters
Features, editor modules, and even the location of permission controls can change between major versions. Before you begin, take a quick look at the instance footer or settings to spot the version string. If the version looks unfamiliar, note it down—community posts or docs you consult later will often require that exact version.
Three straightforward ways to create a page
Wiki.js gives you multiple paths—choose the one that fits your workflow:
1. The New Page button
Most users see a prominent New Page button in the header. Click it, choose a parent location or section from the sidebar, pick your editor (Visual or Markdown), and start drafting. This is a guided, simple flow for most pages.
2. Create a child page from the sidebar
If you want the new page nested under an existing section, many instances let you create a child directly from the sidebar or the page navigation. This keeps structure tidy from the start.
3. Import content
If you already wrote your content elsewhere—Markdown files, exported docs, or another wiki—use the import feature. Import preserves titles and frontmatter in many setups, which speeds up migration. After import, double-check frontmatter keys and permalinks. (See an example of folder/path naming: How to create a page - GO wiki.)
Pick your editor: Visual vs. Markdown
One of the first choices you’ll make is which editor to use. Both are supported and each has strong use cases.
Visual editor (WYSIWYG)
The Visual editor is friendly and fast for non-technical contributors. It shows formatting as you work and hides raw Markdown syntax. Use it for announcements, meeting notes, and pages co-authored by less technical team members.
Markdown editor
The Markdown editor exposes raw markup and is preferred by developers and documentation authors who value portability and predictable output. If you plan to export pages or keep content in a Git workflow, authoring in Markdown is often the better choice.
Practical tip: If your team mixes contributors, draft in Markdown for technical sections and use Visual for collaborative or editorial tasks. Be mindful: switching editors can sometimes change how certain elements are rendered—especially custom widgets or embeds.
YAML frontmatter is a tiny structured block at the top of Markdown pages that holds metadata like title, description, tags, and category. Thoughtful frontmatter improves search, filtering, and automatic lists across your wiki.
Example frontmatter for a simple how-to page:
--- title: How to connect to our VPN description: Step-by-step instructions for connecting to the company VPN tags: [security, setup] category: IT ---
Important: accepted frontmatter keys vary by instance and version. Verify the keys your instance recognizes before relying on them for automated lists or filters.
Writing the page: structure that helps skim-readers
Good wiki pages are scannable. Use a single H1 (usually the page title displayed by the wiki) and H2/H3 subheadings to break content into meaningful chunks. Keep paragraphs short and use ordered steps where appropriate. Internal links to related pages are the glue that turns a collection of pages into a knowledge graph.
Quick structure template
- Title (H1) — short and descriptive- Short opening paragraph — what the page covers- Steps or instructions (H2/H3) — numbered if procedural- Related links — internal pages to connect context- Revision notes — what changed and why
Permalinks and visibility
When you create a page, set a clear permalink (URL slug). Use dashes, keep it short, and avoid duplicates. Permalink conflicts cause overwrites or broken navigation—so check for existing pages with similar slugs before publishing.
Visibility and page rules control who sees the page. Sensitive information should be protected with group and role restrictions. If you alter visibility, test it by opening the page in a private window or asking a colleague with a different role to confirm access.
Save often: drafts, revisions, and rollback
Wiki.js keeps revisions. Save or publish regularly to avoid data loss—browser hiccups and accidental navigation happen. Revisions allow you to see the edit history and roll back to a previous version if needed. Encourage short, descriptive revision messages so colleagues can quickly understand why a change occurred.
Troubleshooting: common problems and quick fixes
Here are frequent issues and what to try first:
Editor doesn’t load
Check permissions and verify the editor module isn’t disabled. If those look correct, note the instance version and ask an administrator to inspect logs or module settings.
Toolbar items missing
That often points to a module configuration mismatch or a plugin that’s not active. Compare the toolbar to another user’s instance, or confirm with the admin what editor modules are enabled.
Permalink conflicts
If you get a permalink conflict, tweak the slug to be unique and meaningful. Avoid changing the permalink on a widely-linked page without adding redirects.
Preview shows old content
Try a hard refresh, private window, or clearing browser cache. Some deployments use aggressive caching or CDNs; coordinate with ops if cached content persists.
Version-specific notes for 2024–2025 deployments
Between v2.x and the 3.x releases, menus, settings names, and editor placement may differ. Always copy the instance version string when asking for help and consult the docs for that release. Community threads often note breaking changes, and matching the version helps you avoid confusing guidance.
Import and export: moving content safely
Import is handy for migrating existing Markdown or archives. Watch how imported files handle frontmatter, titles, and permalinks—behavior can vary. After import, scan a few pages to ensure frontmatter keys mapped correctly.
Export to Markdown or HTML for backups or offline review. Keeping a local copy makes future migrations or audits much simpler.
Practical examples and a step-by-step walkthrough
Below is a practical, reliable step-by-step to create a new Markdown page using the New Page flow. Follow it in order and you’ll avoid common pitfalls.
Step-by-step: create a Markdown page
1. Confirm your role and the instance version.2. Click New Page in the header.3. Choose the parent location or create a new section.4. Select the Markdown editor.5. Add a concise title and set the permalink.6. Paste a small YAML frontmatter block with title, description, and tags.7. Write the body using short headings and steps.8. Link to related internal pages.9. Set visibility and permissions.10. Save as draft and preview in a private window.11. Publish and leave a short revision message.
If you’d like a quick second pair of eyes or professional help crafting page structure, consider reaching out to the Social Success Hub for guidance—they can advise on content strategy and permalink best practices. Contact their team here: Get help from the Social Success Hub.
Small habits that make a big difference
Some simple conventions dramatically improve a wiki’s usefulness:
- Always use descriptive titles.- Keep the H1 at the top and use H2 for major sections.- Populate frontmatter with a clear description and tags.- Link internally to related pages.- Use consistent keys for templates and frontmatter. (For examples of services and support, see: Social Success Hub services and their homepage.)
Template caution: agree on keys
If your team uses templates or custom frontmatter fields, agree on the keys. If half the team uses category and the other half uses section, automated lists and filters will break or be incomplete. Plain communication up front prevents maintenance headaches later.
Examples: two short frontmatter examples
Simple how-to:
--- title: How to connect to our VPN description: Step-by-step instructions for connecting to the company VPN tags: [security, setup] category: IT ---
Basic announcement:
--- title: Product release notes description: Summary of release 2.4.1 tags: [release, product] category: Releases ---
Checklist before you publish
Before you click publish, run this quick checklist:
- Title correct and human-readable.- Permalink short and unique.- Frontmatter contains a helpful description and tags.- Permissions set and tested.- Previewed in a private window.- Revision message ready (if publishing).
Real-world anecdotes and why revisions are your friend
Teams often tell similar stories: someone published a guide missing a crucial step. Because revisions existed, rolling back and merging the missing step took minutes instead of hours. That reliability encourages contributors to iterate freely—an essential trait for a living knowledge base.
Make pages easier to read by using plain language, lists, and descriptive links. Avoid long, dense paragraphs. If you include images or attachments, ensure captions explain why the image helps—readers skim, and clear captions increase retention. A small Social Success Hub logo often helps with brand recognition.
Advanced: templates, custom fields, and automation
If you run a large documentation project, templates and custom frontmatter fields help maintain consistency. Use templates for recurring page types—release notes, how-tos, onboarding steps—and populate required frontmatter keys automatically. That reduces friction for contributors and improves the reliability of aggregated lists and filters.
If you hit a wall: what to capture for admins
If a problem requires admin help, capture these details to speed resolution:
- Exact instance version string.- Steps to reproduce the issue.- Browser and OS details.- Any error messages or screenshots.- Whether the issue affects all users or just a role.
What’s the single smartest first check before you start a new page?
Confirm your permissions and the instance version: permissions determine whether you can create and save pages, and the instance version tells you which UI and features to expect—checking these two things first prevents most early roadblocks.
Final practical tips and good habits
Make short internal rules for page creation: preferred permalink style, frontmatter keys to use, and a simple naming convention. Keep the rules short—people follow brief, clear guidance more reliably than long manuals.
FAQ recap: quick answers
How do I create a page in Wiki.js? Use the New Page button, create a child page from the sidebar, or import content. Choose Visual or Markdown editor, add frontmatter if needed, set permissions and permalink, then save and publish.
Can I use Markdown? Yes—Wiki.js supports a full Markdown editor. Use it when you want portability and predictable formatting.
What if the editor doesn’t load? Check permissions, confirm the editor module is enabled, and verify the instance version. If needed, ask an admin to review logs and module settings.
Wrapping up: a friendly checklist
Creating pages in Wiki.js is a mix of small checks and good writing habits: confirm permissions and version, choose the editor that fits your workflow, use clear titles and headings, add frontmatter thoughtfully, and set sensible permalinks and permissions. Save often, link internally, and agree on frontmatter keys to keep lists and filters working.
Need a hand?
If you want professional help aligning your wiki’s structure, permalinks, or content templates, reach out—our friends at the Social Success Hub offer strategic guidance for teams. Connect with the Social Success Hub to get fast, discreet advice.
Need expert help with your Wiki.js content?
If you want professional help aligning your wiki structure, permalinks, or content templates, reach out to the Social Success Hub for strategic guidance and hands-on advice.
Parting note
With a few good habits and the right checks, creating pages in Wiki.js becomes a smooth part of your team’s workflow. Keep your titles clear, your frontmatter consistent, and your revisions tidy—and your wiki will grow into a dependable knowledge source.
How do I create a page in Wiki.js?
Use the New Page button in the header, create a child page from the sidebar, or import content. Choose between the Visual or Markdown editor, add YAML frontmatter when needed, set a human-friendly permalink, assign visibility and permissions, preview in a private window, then save or publish. Save revision notes for clarity.
Can I use Markdown to create pages?
Yes. Wiki.js supports a full Markdown editor. Markdown is recommended when you want precise control over formatting, portability, or plans to export and version content outside the platform. The Visual editor is better for non-technical contributors who prefer WYSIWYG editing.
What should I do if the editor won’t load?
First, check your permissions and the editor module configuration. Confirm the instance version and capture any error messages or console logs. If the problem persists, ask your administrator to review module settings and server logs; provide the instance version string, browser details, and steps to reproduce the issue.
Creating a page in Wiki.js is straightforward when you check permissions and version, pick the right editor, use clear titles and frontmatter, and follow a short pre-publish checklist — happy publishing, and may your wiki never have broken permalinks!
References:
Comments