- Official Post
Creating and managing custom pages is among the major additions shipped with WoltLab Suite Core 3.0. We would like to provide a brief overview of the system's capabilities and what you can easily achieve in the most user-friendly way.
List, Search and Filter
Maintaining a large set of pages, both static and dynamic, tends to be a real issue and cannot be easily solved by adding a simple pagination. We've added quite a few search controls that enable you to quickly find the page you want to edit, even if you don't know the exact name you'll find it eventually.
Adding Custom Pages
Most of the time users will use the built-in WYSIWYG editor to create their pages, offering an easy solution for structured and formatted content without requiring any knowledge of HTML. For those of you who would like to go beyond that, you can also chose to provide raw HTML instead without limitations, and optionally utilize full template scripting with HTML.
Editing a page: Settings and URLs
You can edit every existing page to alter its name and URL. Especially custom URLs used to be quite a pain as it was just a simple textbox using an equitation-like syntax to provide different values. Not only has this been lacking behind in terms of user experience, but it also created issues with pages that belong to different apps but used the same name. This is no longer an issue as you can provide a custom URL for each page separately and on top of that varying URLs for multilingual pages.
Editing a page: Content
The screenshot above shows the user interface for text pages utilizing the Redactor II WYSIWYG editor, lightning fast with semantic markup. Title, content and meta data is set for each language separately.
Editing a page: Boxes
Boxes can now be freely assigned to any page of your choice, enabling you to pair your content with additional data at your discretion. The actual configuration options will be show-cased during the upcoming spotlight on the all-new box system.
Editing a page: Restrict Access
Custom pages are accessible for everyone by default and in case this doesn't match your expectations, you're free to restrict the access to users and user groups of your choice. These permissions also control the visibility of menu items, limiting access will also hide these items if the user doesn't have the permission to view them.
