This project is discontinued on GitHub.
You can find it on Gitea at https://git.elbe5cloud.de/miro/BandikaSwiftBase
This library contains common classes of SwiftyBandika and SwiftyBandikaCL.
SwiftyBandika is a CMS server app on the Apple App Store (thus including a frontend).
SwiftyBandikaCL is the headless (Command Line based) server.
This library is based on Apple's
and the author's libraries
all on GitHub.
Projects which use this library are: SwiftyBandika (server with GUI in the app store) and SwiftyBandikaCL (command line)
The web view shows content or page is governed by the current content's page type and its master page.
The system menu is a list of small icons on the top right.
This icon links to the home page (as the logo does).
The icons appear when the user is not logged in.
Leads to the login dialog.
These icons appear when the user is logged in, but depending on the users rights and the current page edit mode.
Links to the Adminstration. This icon appears only if the user has any administration rights.
Opens the current page in edit mode. This icon appears only if the user has edit rights for this page.
Toggles between the draft and the published view. This icon appears only if the user has edit rights for this page and the page has been changed.
Publishes the current draft of the page. This icon appears only if the user has approve rights for this page.
Link to the current usres profile page, where he/she can edit certain attributes and change the password. The password minimum length is 8 characters.
Logs the current user out, changes to anonymous view.
The logo is an image, which can be changed in the app. It links to the home page.
The top menu items are links to direct child pages of the home page (which have been selected for the main menu). If a top item has child content, it opens a dropdown with a link to itself and its child contents.
These are links to the contents.
Depending on the browser width, the main menu changes to a mobile view with a 'burger icon'.
This shows the path from the Home page to the current content. Path elements are links to the respective content.
The content area shows what is the "content" part of the master page. It can be viewed in normal or edit mode (if the user has these rights).
The defaut view shows the content as it has been created and edited. If the content has been changed compared to the published version and the user has edit rights, he7she is shown the draft version. This can be changed by the 'eye' icon in the system menu.
The edit view allows direct editing of all editable parts of the page.
At the top of this view there are Save and Cancel buttons to save or cancel the current changes.
Important: If changes are not saved and the page is closed, all changes are lost!
Depending on the page types and templates, the edit areas may differ. So a full page layout has just one dit area, whereas a template based page may have several sections which can be filled by parts and their editable fields.
Beside the master templates, which govern the area around the content, there are page templates for the content layout and part templates for single parts in sections of the content.
Sections are areas for parts (maybe with own templates), which are defined in a page template. Typical sections are columns for main and aside content.
Part are small items which can be added to a section. Parts can be program defined like a list of subcontent or a list of usres, or it can be template based with editable fields like text field, html field or image field.
Footer links point to content, which in the administration has been set a footer content. Typically these are imprints or legal pages.
The web administration is split into user/group administration and contentadministration.
Groups are groups of users, mostly for assigning rights.
A dialog lets you set name, global rights and members.
A dialog lets you change name, global rights and members.
Deletes the group permanently.
Users have the usual attributes and may be member of one or more groups.
A dialog lets you set the attributes and group memberships. Last name, login name, password and email are mandatory.
A dialog lets you change the attributes and group memberships. Last name, login name, email are mandatory. If no new password is entered, the old one remains in place.
Deletes the user permanently. You cannot delete the Superadmin user (root).
The content administration lets you create content, or edit content settings and their tree structure. Visual content is edited in wysiwyg mode, that is on the actual page itself.
A dropdown lets you choose the content type before editing its settings (see below).
Lets you paste content from the internal clipboard if present.
Jumps to the default view of the content.
A dialog lets you edit the content's settings, including name, description, anonymous viewing, master template, page template (if any), appearance in menus, active state.
A dialog lets you set specific right for any group.
A dialog lets you change the sequential appearance of child contents in any list (e.g. the menu).
Cut content to the internal clipboard. Only after pasting the content is actually moved.
Copy content to the clipboard. During this operation the new content gets a new ID, but all other attributes are exactly copied.
Deletes the content permanantly. The root content (Home page) cannot be deleted - it can only be changed.
For each content the content administration lets you create files, or edit file settings.
Create new file data and opens a dialog to edit it (see below).
Lets you paste a file from the internal clipboard if present.
Open the file in a new window.
Lets you save this file locally.
A dialog lets you edit the file's settings, including name, description and the file itself (replace).
Cut the file to the internal clipboard. Only after pasting the file is actually moved.
Copy the file to the clipboard. During this operation the new file gets a new ID and a new physical file, but all other attributes are exactly copied.
Deletes the file permanantly.