Content and your team

Create, preview and publish

1. Create the right content type and save a draft before leaving the editor.
2. Set title, slug, excerpt and language. A parent page contributes to the child page’s public path.
3. Use the content preview and compare desktop and narrow layouts. Builder pages keep their section document and rendered page together; edit them through the builder.
4. Publish only when ready. If a save reports a conflict, keep your proposal, reload the current version and reconcile changes instead of blindly submitting again.

Menus, translations and media

• Create separate Arabic and English content and link the translation pair. Translating a menu label does not translate the destination page.
• Edit the appropriate language’s menu and verify every destination publicly. A saved page is not automatically a menu item.
• Upload media with meaningful alternative text. Reusing a file means it may appear on more than one page.
• Page password/access controls gate the page, not previously public media URLs. Treat confidential files as a separate storage and access-control problem.

Give people the access they need

Use named accounts and the smallest role that can do the job. A contributor can prepare content without publishing; an author can publish their own permitted content; an editor has broader editorial access. Administrative settings and credentials should remain with authorized administrators.

The actual role permissions and content ownership checks remain authoritative. Hiding a sidebar item or moving it to the dashboard changes your personal navigation, not anyone’s permissions.

1. Create the account with the intended role.
2. Sign in as that user or review their actual permitted screens.
3. Confirm they can perform the needed work and cannot open unrelated private content.
4. Revoke unused accounts and keys when access is no longer needed.

Forms and private reports

Use the form directory to find the public form and the inbox to review stored submissions. A contact entry’s associated page is navigation context, not forensic proof of where a visitor came from. A stored submission does not prove an email notification was delivered.

Private reports use their separate protected workflow. Do not copy sensitive report bodies into public content or AI prompts.