Content and editing
Pages and articles
Manage paths, descriptions, language pairs, publication and the content lifecycle.
On this page
Page structure
A page stores its title, description, path, language, content and publication state. The current content body is sanitised HTML, not a fully portable framework component tree. Articles use the same underlying Page entity with a different content kind. Paths are absolute, lowercase and end with a slash. Preserve existing paths when replacing an indexed website. A path change does not automatically guarantee a redirect from the old address.
/services/
/en/services/
/articles/example-article/Edit and view
Open Pages or Articles and choose Edit. Visual editing opens by default, with an HTML/source option available. One Save action keeps you in the editor. View page opens the frontend or an authenticated draft preview in another tab. The editor's bottom feedback area indicates unsaved changes and offers access to the last saved view. Viewing the saved page is not a live preview of unsaved edits. Save deliberately after reviewing your changes.
German and English
The supported content locales are de-AT and en-AT. A translation key pairs related pages or articles. Creating an English draft is optional; it copies content for editing, not a reviewed translation generated automatically. Language versions have independent content and publication. English article duplication preserves the category but clears language-specific header/footer overrides so the wrong-language shared layout is not reused.
Publication and trash
- Publish only reviewed content. Private draft previews require a content-editor session.
- Deleted content first moves to recoverable trash; restore it when necessary.
- Permanent deletion is a separate action. Recovery data is removed with permanently deleted content.
- The public API excludes drafts and trashed records.
Layout and category fields
Use the Layout tab to choose a specific shared header or footer, or retain global assignment. Explicit selections must match the content language. Articles also have a category; category-based layout rules can provide consistent article presentation.
Something unclear? Contact me about this guide.