Basic Terms
Some important, often used terms are explained here to avoid misunderstandings.
- access files: the small php files in the /pages directory. They contain the→ Page ID, some → code and nothing else.
- access right: definition of the rights of a →user, e.g., is he/she allowed to edit/create/delete pages, see certain contents, create user accounts, install modules etc.
- account, user account: All the personal data of a user (login name, display name, password etc.)
- addon: usually a →module or a →template.
- administrator: →user with extended rights, e.g., able to create new → accounts, install or delete → modules.
- backend: in this case the user interface of WBCE CMS, where you create →pages and →contents, manage →addons and →accounts, modify options and settings and so on.
- block: a defined area in the →template where one or more →sections are situated.
- code: commands for the server and/or browser which are written in a markup or programming language, e.g., PHP or JavaScript.
- content: the information provided on a →website, e.g., text, images, downloads... everything that does not come from the template.
- core: all the necessary files, containing uncountable masses of code lines, which are needed for WBCE CMS. All that stuff which can be found in the installer.
- editor: →user with restricted editing access, e.g., able to change the content of the website, but is not allowed to create new user accounts.
- footer: something that appears at the very end of a →page. Can be defined in the →options or →template.
- frontend: the public →website which is displayed to the →visitors.
- header: something that appears at the very beginning of a →page. See →footer.
- installation: a) the process of copying the →core files onto the webserver and running the installer script; b) the result of a)
- instance: exactly one running WBCE CMS installation (consisting of one or more →pages).
- layout: the design of a website (how and where each element shows up), e.g., the colors, images, fonts.
- menu: navigation area of a →website. Often found in the →header, →footer and/or the →sidebar of a →page.
- module: mandatory or optional →addon which generates a certain →output or provides some special functionalities in the →backend, e.g., the module "MiniForm" generates contact forms.
- navigation: the part of a →page which represents the structure of the →website and enables the →vistor to access the other →pages. See →menu.
- options: mostly input fields, but sometimes plain text files too, where the global configuration of a WBCE CMS installation or module specific configuration is defined.
- output: → code which is generated by a →module or →template which makes the →content of a →page.
- page-ID: each →page of a WBCE CMS →installation can be identified by its ID, which is just an automatically increased number. It can be used for linking pages (< a href="[ wblink42 ]">Don't panic< /a > and so on) or conditional outputs (if (PAGE_ID==42) and so on).
- page: a single page of your →website, e.g., yourdomain.tld/pages/about-us.php. Can contain one or more →sections which are positioned on one or more →blocks defined in the →template.
- placeholder: reserved word using a certain syntax, which is replaced by the →core or a →module function by a value, e.g., the placeholder [BACK] will be replaced with "<< back".
- session: the period of time during which a user is logged in to the backend. Is terminated either by the user themselves, or if a period of time passes with no (perceived) activity (e.g., saving, changing to another page...) by the core.
- section: a part of a → page generated by a → module and displayed in a defined → block.
- sidebar: area which is placed on the left or right side of the main →content of a →page, often used for →navigation elements.
- tag: HTML command, e.g., < h1 >
- template: defines the →layout of a →page or the →output of a →module. The counterpart of the →content.
- theme: see →template. As a WBCE CMS term: the template for the →backend.
- user: someone with access to the →backend.
- visitor: someone who looks at the →frontend of the →website.
- website: all →pages of an →installation.
- webspace: the server or directory where the files of a WBCE CMS →installation are stored.