German 
English Awyiss Features at a Glance
Pages & Contents
In Awyiss, Pages are the fundamental unit of a website. An unlimited number of Pages can be created and organized hierarchically, resulting in a clear structure in the Backend. This hierarchy is reflected in the Frontend and influences elements such as Breadcrumbs and the URL structure. Each Page defines data such as title, URL path, and – via the assigned Page Template – the available Content Areas.
The actual Content is managed per Page in a dedicated section. There, all Content elements of a Page are visible at a glance and organized according to their Column Structure. Content can be created in unlimited quantity, arranged via Drag and Drop, and flexibly combined or nested.
Content is based on Content Templates and can include Text, Images, Videos, or custom Widgets. For Text Editing, Rich Text Editors such as TinyMCE or Jodit are available, offering extensive Formatting Options. In addition, CSS Classes, Styles, and Data Attributes can be defined to control Presentation and Behavior precisely.
Page Roles
In Awyiss, Page Roles form the foundation of all Pages within the system. They define what type Page is, which fields are available for it, and how it is displayed both in the Backend and on the website. This creates a clear structure in which every Page has its own purpose and layout – ranging from simple text pages to complex content modules.
Typical Page Roles include news articles, products, events, or references – each with its own fields, structures, and presentation options.
Media Manager
In Awyiss, the Media Manager serves as the central hub for all files used within a website. Images, videos, and other media files are collected and organized here and are then available throughout all areas of the system. A customizable folder structure ensures transparency and makes it easy to locate files again.
Media can be uploaded via Drag-and-Drop and stored within the appropriate structure. The system supports various file types and ensures that images are automatically delivered in the correct size for the Frontend. The File Name serves as the title and can be adjusted if needed. Additionally, an Alternative Text (Alt Text) can be added, which is used for accessibility purposes and as a fallback when images are not loaded.
The Media Manager is closely integrated with all editorial areas of Awyiss. Files can be inserted directly into Contents, Forms, or Rich Text Editors without leaving the current workflow.
Customizable Backend Interface
The User Interface of Awyiss offers various options to visually and functionally adapt the Backend to your individual working environment. A custom Login Logo can be added to align the system with a specific project or brand. In addition, a Dark Mode is available to provide an optimized display under different lighting conditions.
For general display settings, three Scaling Levels can be selected to adjust the size of texts and interface elements to personal preferences or screen dimensions. The forms can be displayed either in a linear layout or divided into a main area and a sidebar.
Furthermore, a central Accent Color can be defined, which is used throughout the entire interface. This gives the Backend a consistent appearance that can be visually adapted to the respective project.
Additionally, Awyiss uses the styles defined in the Frontend Design for displaying text within Rich Text Editors and the Audit History, allowing content to appear during editing exactly as it will later appear in the Frontend. This makes editing significantly more intuitive and ensures that the visual context remains clear at all times.
Frontend-Editor
The Frontend Editor in Awyiss allows Content to be edited directly on the website without opening the Backend. Existing texts, images, or other fields can be modified right in their position while the page structure and layout remain unchanged. This enables editorial adjustments to be made quickly and within the actual page context.
The Editor accesses the existing data in the system and applies changes directly to the stored Content. All Permissions and Roles are taken into account, ensuring that only authorized areas can be edited. This creates an efficient and clear workflow for editors that requires no technical knowledge.
Menus
In Awyiss, Menus can be centrally managed and freely structured. They are used to represent the navigational structures of a website – such as main navigations, footer menus, or links to social media channels. A Menu consists of individual, language-specific entries that reference Pages, external links, or other content, and can be arranged in any desired hierarchy.
This allows navigational structures to be precisely controlled and adapted to different requirements. Changes to Menus immediately affect the linked areas of the website without the need to modify Templates.
Menus are integrated into the Frontend via the Template System and can be styled there in any way. This keeps navigation centrally manageable while the appearance is fully determined by the website’s design.
Forms
In Awyiss, Forms can be created and managed directly within the Backend. They are used to collect input from website visitors and store it in the system – for example, for contact requests, newsletter sign-ups, or other interactions. After submission, the data is saved and can be accessed in the Backend. Optionally, an email can be sent to the site owner and/or the customer.
The structure of a Form is built from freely combinable Form Elements that can include different input types such as text, email, select fields, or checkboxes. Validations and protection mechanisms against spam or multiple submissions ensure that collected data is processed reliably and securely.
Forms can be integrated into any area of the website – for example, within Content, Global Contents, directly in Page Templates, or within Widgets. This allows interactive functionality to be implemented directly within the system – without external services or additional programming.
Recipient Rules
Awyiss allows the definition of conditional recipients within a Form. Depending on specific inputs – for example, a selection made in the form – it can be defined which internal recipients should receive an email. This makes it possible to automatically forward inquiries to the appropriate department or person without the need for multiple separate forms.
Customizable Data Tables
Custom Data Tables are a core tool in Awyiss for creating individual data structures directly within the system. They allow you to create, maintain, and manage your own tables with freely definable fields through the Backend – all without additional programming or external modules. This makes it possible to implement specific requirements that go beyond standard content, such as product data, event calendars, or internal data lists.
The tables are fully integrated into the existing User Interface and use the same mechanisms as other areas of the system: access via the Backend, consistent form inputs, filter and search function, as well as sorting options. Each Data Table can be individually configured to provide only the fields and input types that are actually needed.
Through integration with the Permissions Management, Data Tables can be precisely controlled – defining in detail who is allowed to create, edit, or delete entries.
This ensures that working with custom data remains secure and transparent. Custom Data Tables extend Awyiss in a flexible way without affecting the system’s updatability. They provide developers and editors with a stable foundation for managing tailored data models directly within the CMS and dynamically integrating them into Templates or Widgets.
Surveys
With the Survey System, Awyiss provides an integrated way to collect visitor feedback directly within the CMS. It enables the creation and management of surveys, polls, or short questionnaires without the need for external tools or extensions. All forms and responses are stored within the system and can be managed via the Backend.
A Survey consists of freely definable Questions that support different answer types – such as single choice, multiple choice, information text, or free text input. For single and multiple choice types, the option to allow a custom answer can also be activated in the Backend.
The sequence and logic of a Survey can be freely defined: both Questions and, in the case of single-choice questions, individual Answers can determine which step follows next. The system can then proceed to another Question, a Form, or save and/or end the survey (prematurely). This makes it possible to implement flexible and branching flows that can be precisely adapted to individual usage scenarios.
Surveys can be embedded directly into Content or assigned to specific Pages. This makes them part of the editorial workflow and allows them to be integrated into thematic focuses or campaigns. This creates a direct connection between Content and user feedback without interrupting the editorial process.
With this approach, Awyiss provides a lightweight yet powerful tool for integrating visitor interaction – fully system-integrated, compliant with data protection standards, and freely customizable.
The Survey System can be used not only for classic surveys but also as a Configurator. In addition to typical use cases such as feedback or satisfaction surveys, it also supports step-by-step selection processes where Answers determine the subsequent flow. This makes it possible to implement product configurations, guided consultations, or thematic decision trees that dynamically display different content, Forms, or results to users. As a result, the system becomes a versatile tool for interactive content and dynamic workflows within Awyiss.
Visual Representation of the Flow
For better clarity, the Backend displays an automatically generated diagram that visualizes the entire flow of the Survey. It shows which Questions and Answers lead to subsequent steps, making even complex branches easy to understand. The visualization serves primarily for review and coordination during the editorial or conceptual process.
Design Management in the Backend
The Design System is one of Awyiss’s core strengths and forms the foundation for a consistent and extensible visual identity of a website. It enables the centralized definition and management of design parameters such as colors, fonts, spacing, and components — without directly modifying templates or stylesheets.
The available settings in the Design Editor are based on developer-defined SCSS files. These files determine which parameters can be adjusted in the Backend — such as color variables, typography options, or layout values — and how they affect the overall appearance. This keeps the Design System fully extensible while maintaining a clear separation between design and content.
A Design combines these parameters into a complete configuration. It can be activated globally for the entire website or serve as an alternative version to compare and align different settings internally. This allows design adjustments to be prepared, tested, and visually communicated before going live.
The Design System also directly impacts editorial work: Rich Text Editors and the Audit History use the styles defined within the Design to display content during editing exactly as it will appear in the frontend. This makes editing significantly more intuitive and ensures the visual context is always visible.
Multi-language Support
Multi-language support is a core part of Awyiss and allows managing Content, Pages, and other data in multiple Languages. Each language version is maintained independently, so translations can be edited and published separately. This enables websites to be built specifically for different regions or target audiences.
For elements shared across all Languages — such as Forms — translations can be added directly within the respective section. This way, they don’t need to be duplicated. At the same time, it remains possible to create and manage language-specific variants individually when structure or content differ between Languages.
The Backend itself is also multi-language. The user interface, system texts, and help texts can be displayed in various Languages, allowing editors and administrators to work in their preferred language. This makes Awyiss ideal not only for multilingual websites but also for internationally distributed teams.
Multi-language support is fully integrated into all areas of the system. It covers both editorial content and technical components, while remaining fully updateable and easy to maintain despite its flexibility.
Widgets
Widgets in Awyiss extend the system with custom functionality without altering its core structure. They act as flexible building blocks for integrating dynamic content, external data, or specific logic into Pages and Contents. This allows projects to be enhanced with new features without modifying existing Templates directly.
Widgets are treated as standalone components and can be used in various contexts — for example within Contents, Global Contents, or Templates. In the Backend, editors can select Widgets through the editor interface and adjust their settings directly. In the Frontend, they are automatically rendered and integrated into the page layout.
Awyiss already includes several Widgets that cover common use cases. In addition, custom Widgets can be developed and integrated to provide project-specific functionality. This makes the system flexibly extensible and adaptable to any client requirement.
Backend Menu
The Backend Menu can be extended with custom menu entries to integrate individual functions or extensions. These entries can link to custom targets, external tools, or specific Backend areas and are seamlessly integrated into the existing menu structure. By assigning Access Rights, users only see the menu items relevant to their respective roles in the Backend. This allows the working environment to be precisely tailored to responsibilities and areas of focus.
The management of additional menu entries can be handled either directly in the Backend by users with the appropriate access rights, or by providing a JSON configuration file within the client folder.
Users & Usergroups
In Awyiss, Users are organized into Usergroups to manage permissions centrally. Each User can belong to multiple Usergroups, allowing a flexible combination of access rights. Changes to groups or memberships take effect immediately and apply system-wide, without the need to manually assign permissions for each individual User.
This structure makes access control efficient and consistent: Usergroups define roles and areas of responsibility, while Users automatically inherit the corresponding rights through their membership.
Attributes
In Awyiss, Attributes are used to add additional information to any element within the system. They can be created for Pages, Contents, or Users, allowing custom fields to be added without modifying the system’s core structure.
Attributes are defined centrally and managed within their own data structure. This makes the system flexibly extensible while remaining fully updateable. Their values can take on different data types — such as text, numbers, or selection lists — and are available both in input forms and in the code.
In this way, Attributes offer a controlled and future-proof way to extend Awyiss functionally and represent project-specific information in a structured manner.
Global Contents
Global Contents in Awyiss allow creating reusable content elements that can be embedded anywhere in the Frontend. Global Contents can range from simple text blocks to complex elements such as Forms, image galleries, or combinations of multiple components. They are based on Awyiss’s Column System and use separate Templates for rendering.
Unlike regular Contents, Global Contents are not tied to specific Pages or Content Areas. They can be freely placed within Templates — for example, in the header, footer, or a sidebar. This allows recurring information such as contact details, opening hours, or call-to-action sections to be managed centrally and used consistently across the entire website. This flexible structure make Global Contents an essential tool for dynamic and modular layouts.
Audit
The Audit Log in Awyiss records all changes made to data within the Backend. For each entry, it tracks which action was performed (creation, modification, or deletion), by which user, and at what time.
Additionally, a Version History of each element can be viewed at any time to restore previous versions or review changes. Differences — what was added, changed, or removed — are clearly highlighted.
The Audit System therefore plays a key role in maintaining transparency and traceability. It is ideally used in live projects to track down errors, clarify responsibilities, and ensure content is managed securely and in a controlled manner.
Locks
In Awyiss, Locks ensure that multiple Users cannot edit the same content simultaneously. As soon as an element — such as a Page or a Content — is opened for editing, it becomes locked so that other Users can only view it in read-only mode.
The Lock remains active only for a defined period of time and is automatically released afterward, even if the editing session was not properly closed. This ensures that locked elements are never permanently blocked and that access is restored once the lock duration expires.
This locking system guarantees content consistency and allows editors to see at any time whether an element is currently being edited. It reliably coordinates collaboration within the Backend and prevents unintentional overwriting of changes.
SEO Analysis
The SEO Analysis in Awyiss helps editors evaluate the search engine friendliness of individual Pages. It reviews key elements such as page titles, meta descriptions, and heading hierarchy, highlighting missing or incomplete information. This makes it easy to identify and fix common SEO issues — such as missing or overly long meta descriptions.
Because the SEO Analysis is fully integrated into the Backend, any identified issues can be corrected directly on the spot. This makes search engine optimization an integral part of the editorial workflow.
URL History / 404 Tracking
Awyiss stores previous addresses of Pages — and optionally of Media Elements — in the URL History. When pages or media are renamed or moved, their old URLs are preserved and automatically redirect to the current addresses, ensuring that existing links do not lead to dead ends.
In parallel, the system logs all requests to non-existent URLs in a dedicated 404 Tracking view. This list shows which unknown URLs were accessed by visitors or external sources and helps identify broken links and set up appropriate redirects if needed.
Together, these two features ensure that modified or removed Pages do not result in dead links, and that both users and search engines are reliably redirected to valid content.
Awyiss is designed from the ground up to be extended and customized without modifying the system core. All central components — such as Widgets, Templates, Classes, and Backend Views — follow a clearly defined structure based on inheritance and overrides. This allows existing functionality to be expanded or replaced without altering any core Awyiss files.
Extensions are stored within the dedicated client folder. If a class with an identical path exists there, Awyiss automatically uses that implementation, enabling targeted adjustments to specific areas. In this way, standard functionality can be adapted to project-specific requirements without compromising the integrity of the base system.
Additionally, new Widgets or entire Backend sections can be added as standalone extensions. These are dynamically loaded during system startup and become fully integrated into the Backend. Because the core remains untouched, future Awyiss updates can be applied without losing individual customizations.
This clear separation between the system core and the extension layer ensures that Awyiss remains maintainable and update-safe in the long term — regardless of how deeply projects are customized or extended.