Wadood Docs

Appearance

Wadood DocsAdmin portal handbook

Step-by-step guides to every module of the Wadood site builder — from Pages and Layouts to the prebuilt components.

Get started with Pages
Browse components

Build pages

Create static and dynamic pages, manage versions and languages, and use the page builder.

Layouts & shared elements

Reusable shells that wrap pages, and content blocks you can drop in anywhere.

Components

The prebuilt wd- components — sliders, tabs, accordions, the form engine — and how to style them.

Data & forms

Data Store schemas, option groups, and the schema-driven form builder.

Navigation & content

Menus and localization to structure your site and translate its text.

Sites & access

The site dashboard, sites and environments, users, roles and privileges, and the file manager.

AI Assistant (MCP)

Drive Wadood from an AI assistant — connect ChatGPT or Claude to build pages, manage data, and sync environments in plain language.

What this is ​

User-friendly guides that teach portal administrators how to use each module of the Wadood site builder. Every module is a self-contained guide; use the sidebar to browse, or the search box to jump straight to a topic.

How these docs are produced ​

For each module:

  1. A screen-recording of the module's journey is captured.
  2. The spoken narration is transcribed offline (see tools/transcribe.py) to capture the author's intent and the "why" behind each step.
  3. The journey is verified against the live portal and the application source code to confirm exact labels, validation rules, and edge cases.
  4. A professional, step-by-step guide is written using a consistent template (Overview → Prerequisites → Tasks → Reference → Tips → Known issues).

Conventions ​

  • Screenshots live in each module's assets/ folder.
  • Privilege codes (e.g. CAR) are shown alongside friendly names where they help administrators understand access control.
  • Each guide ends with a Known issues section capturing anything observed in the current build that the product team may want to address.