Your Definitive Source of Corporate Truth

The smartest and most cost-effective method of handling customer support is proactively answering questions before they are even asked. The Knowledge Base (KB) module is the robust content center functioning as your corporate Wiki or public Help Center. Operations teams draft deep technical guides, FAQs, and step-by-step onboarding walkthroughs — all without touching a single line of frontend code.

📄 WYSIWYG Article Editor

Create rich, professional articles using the built-in WYSIWYG editor with support for headings, bold/italic formatting, bullet and numbered lists, blockquotes, code snippets, embedded images from the Media Library, hyperlinks, and tables. Articles can be saved as Draft for internal review before publishing to the public Help Center.

🗂️ Hierarchical Categories

Organize articles into a nested category tree with unlimited depth. Categories support parent-child relationships, allowing structures like "Getting Started" → "Account Setup" → "Two-Factor Authentication". Each category has its own title, description, icon, and display order. The category management dialog allows creating, editing, and reordering categories with drag-and-drop.

🌐 Multi-Language Content

Every article and category supports multiple locales. Write the English version first, then switch to the Turkish tab and provide a localized translation. The public Help Center automatically displays the correct language based on the visitor's locale preference. Untranslated articles gracefully fallback to the default language.

💬 Community Comments

Published articles include a Comments section where readers can ask follow-up questions or provide feedback. Support administrators moderate comments from the admin panel — approving helpful contributions, marking answers as resolved, or removing spam. This creates a living knowledge base that evolves with user input.

🔍 SEO & Metadata

Each article includes configurable SEO fields: custom slug, meta title, meta description, and tags. This ensures your Help Center articles rank well in search engines, driving organic traffic and reducing the need for direct support contact.

👁️ Visibility Controls

Articles support Draft (invisible to public), Published (visible on Help Center), and Internal (visible only to logged-in team members) statuses. This allows maintaining both a public-facing knowledge base and a private internal wiki within the same system.

Article Fields Reference

Field	Type	Required	Description
Title	Text	✅ Yes	Article headline displayed in listings and search results
Slug	Text (auto-generated)	✅ Yes	URL-friendly identifier used in the public Help Center URL
Category	Select (hierarchical)	✅ Yes	Parent category for organizational grouping
Content	Rich Text Editor	✅ Yes	Full article body with WYSIWYG formatting
Status	Select	✅ Yes	Draft, Published, or Internal
Meta Title	Text	❌ No	Custom SEO title (falls back to article title)
Meta Description	Textarea	❌ No	SEO meta description for search engine snippets
Tags	Multi-select	❌ No	Keywords for search and filtering
Featured Image	Media picker	❌ No	Thumbnail displayed in article listings

Step-by-Step: Creating a Help Article

Navigate to /admin/knowledge-base.
Click "New Article" to open the editor.
Select Category: Choose the appropriate category from the hierarchical tree.
Write Title: Enter a clear, searchable headline.
Write Content: Use the WYSIWYG editor to create the article body with formatting, images, and code blocks.
Add SEO Metadata: Optionally customize the slug, meta title, and meta description.
Set Status to Draft: Save as draft for team review.
Review & Publish: After approval, change status to "Published" to make it live on the Help Center.
Translate: Switch to the Turkish locale tab and add the translated version.

Enterprise Use Case: Zero-Touch Issue Resolution

A B2B software platform releases a massive dashboard redesign. Over 2,000 users will encounter confusion the following Monday. The Support Manager logs into the Knowledge Base on Friday. They draft an exhaustive "New Dashboard Layout Guide" filled with annotated screenshots, organized under the "Getting Started" → "Dashboard" category. The article is published to the top of the Help Center. Monday arrives, and instead of 2,000 complaint tickets, the system logs 2,000 article views and literally zero "How does this work?" tickets. The KB article also appears as a suggested solution when customers start typing in the Feedback Widget — deflecting tickets before they're even created.

Knowledge base