Themes

The very FIRST thing you need to do is to sign into the "Dashboard". To do that you will scroll to the bottom of the page and select the link there that says “Sign in to edit this site”.  You will be logged in and will have a screen that looks sort of like this (Figure 2).  It will also have the default Plain Yogurt Template installed.  That information is in the figure below.

Figure 2 - Top Dashboard Menu

This is where your adventures with 7thWeb CMS begin.  Just like the “Edit Page” says, you click that
button and edit your pages.  I will get to those left hand buttons below.  Your third button from the right is important.  Click it and you will come to the main “Dashboard” (Figure 3) as referred to in the
following graphic,

 

 

Figure 3 - The Main Dashboard

Get familiar with this area. Some areas will be used by the site administrator but most of the time, you will be using the "TOP" Dashboard menu (Figure 2). This allows you to create new pages and to edit existing data "IN-LINE". That is the one thing that really makes 7thWeb CMS stand out from other cms's. It is implemented so wonderfully.

This is also the time where you should become familiar with 7thWeb CMS terminology (see the Glossary
at the end of this document). It is a little different and some people will sound somewhat exasperated
when you are asking a question that has been asked over and over again. This is OK, don't get riled up.
Also, as a side note, not everyone has English as their first language, so keep that in the front of your
mind when reading some of the forums. On the " Help " portion of the official site, you will find How-
Too's, FAQ's and assorted other documents (including Screen Casts (the C5 team loves those)).

 

 

Chapter One

Learning to edit your content.

Introduction

Disclaimer on site design: This section is for new people to 7thWeb CMS.  It is intended
to describe introductory web site design and editing.  The descriptions are based on
my own experience dealing with people when approaching a first time web design
meeting.  It is “Basic”.  The comments here do not in any form relate to how the
7thWeb CMS developers approach design.  These are my own observations.

In this chapter you will learn the basics of editing your content.  Your web site is loaded the first time with example data and this is very easily changed.
If you point your browser to your site (either localhost or your domain name), it will come up like any normal appearing Concrete based web site.  Look around it.  See if the basic menu system is right for you.  Look to see how the color and text look.
This, my friends, is “Site Designing” at its base level.  If you have ever been in business and had the
oppurtunity to sit in with the first meeting of a web site design team, you will recognize some of the
things I am about to say.  Here are some questions that are asked for every web site that is designed
(These are only a few.  There are many many questions asked and answered before most sites are even
demonstrated):
•  What is your color schema going to be?
•  Do you have a company or organization logo that will be used?
•  Will there be a new branding of your company/organization done?
•  Will the web site design determine your new branding?
•  Will you want typical Web 2.0 formatting?
•  Will you want a gallery?
•  Will you want a forum?
•  How many contributers will be adding or modifying information on this web site?
•  How many people will be allowed in the administrative portion of this site? The list can go on and on.
Colors and Logo's
One of the worst things you can do is have lots and lots of color on your web site.  This detracts more than it helps.  Even for a funky forum or wiki, that has no formal reason to be on-line except for a way to communicate with like minded people.  A lot of colors will be detracting.  Decide on no more than 3 colors for your pages.

 

 

For your logo, unless its on a introductory page, make sure it is clear and easy to read, but small
enough not to be a detractor.  Make it pop by all means, but the logo is not the thing you want people to
have blaring in their face.  Reference the 7thWeb CMS logo.  Clean, sharp, not a lot of colors but it
“POPS”.
Determine what your background's will be.  Will it be a picture of some sort or just color?  Limit your contrasts of color but remember to ensure that it is appealing to the eye.  I know what your thinking, “But I am a funky, hip graphic artist that is hot with all the cool trends”.  Still, it is recommended  that you follow some type of design guidelines.  You can make it appealing too all your visitors.
Images
Do not crowd your pages with images.  Normally on a professionally designed site you only have 3 maybe 4 images per page.  And that is stretching it.  Of course if this is a personal site, have all the images you want.
“But I want jammy stuff!”  You want wiz bang rollover's and Flash movies and movies from You Tube or Vemio.  You can have all that.  But remember, if you just throw those things on your page, it  may be confusing for your visitors.
7thWeb CMS has the tools pre-built to handle most of these needs. (Remember those terminologies I
referenced earlier?  Hopefully you took a look.)  How will this be handled?  You will use “Blocks” to
make this happen.  And you just need to supply the images.  I will go into this in detail further in the
Guide.

Editing Content
So how will you edit your content?  Start by logging onto the page of your site that you want to begin with.  Remember Figure 2.  Those buttons on the left I referenced.  Click on the “Edit Page” button. You will see something like what is in Figure 4.

 

 

 

Figure 4 - A page in 7thWeb CMS that is in “EDIT” mode

 

 

The red boxes around the items on the pages are areas that you can edit.  When you role over those
blocks of text or a graphic, they will turn gray.  When you see that, that will indicate an “Editable Area” and if you have the permissions to edit that content, you will be able too.  Go ahead, click one.  When you click your left mouse button, a small pop-up window will appear (See Figure 5).

 

 

Figure 5 - Edit Content Menu

When the menu pops up, select the “Edit” option.  An installed program for editing content known as
TinyMce will open on your page.  It is a “What You See Is What You Get (WYSIWYG)” editor for
changing information.  It is free so don't worry about having to pay for it.  The content of that gray area
will be displayed.  You can edit the data or add data just like your were in your favorite document
editor.  Go ahead, edit stuff.  When you are done, look at the top menu of the  Dashboard and tell it to
Exit Edit Mode.  A window will appear with some options.  7thWeb CMS has a versioning system built in.
You can revert to any number of edits.  So just look around this window and get familiar with it, you
will see it every time you edit a page area.  You can preview your changes, discard your changes or
save it.  This is where your save option buttons are and then select Publish My Edits (See Figure 6).

 

 

 

Figure 6 - Saving your data

If the content your editing or replacing happens to be a “Block”, the menu will be different and your options will be different.  Play around with your pages to start learning the system.
As you can see in Figure 5, several options are there for the user to set certain items or do certain things for each page.

Learning about permissions

If you are in a group of content contributers, you may only want certain contributers to edit certain
pages.  This is where the permissions option on your menu comes into play.  With the help of your
administrator or senior editor, create user groups from your dashboard.  Then when you have your site

 

 

set up the way you want it, you can assign certain people to certain groups.  Only a handful of people will have complete access to all content.  This is a normal thing and if you are wondering, here is a typical breakdown of example group lists and users:

 

1.  Administrative Users
2.  Group Content Users
3.  Content Users

An administrative user is typically one of the server administrators.  Though in some cases, this may be
split into a few sub-areas in which all technical things (special web page development or server
maintenance) are done and then those administrators that handle the day to day administrative things.
This could include management of groups, setting permissions for users, or moving data around the
web site.

Groups are exactly that, groups of people that have access to select areas of content or administrative
capabilities.  Normally, with a site that only has between 5 to about 100 pages, you would only have
maybe 3 or 4 groups.  If you have multiple sub-domains, this is exponentially bigger.  You may have
topical areas of 100 topics or more.  So you could potentially have upwards to 20+ groups just to edit
content.

Content users then would be those contributers that are assigned to certain groups.  The have certain
permissions that allow them only to do certain things.  You can assign people so that they cannot delete a page, they could be able to create new pages but not publish.  So just like a newspaper, your authors may have to wait for the editors who then have to wait on the publisher to approve the content before it is available to the general public.

As you become more exposed to 7thWeb CMS and the way it handles data and the flexibility it gives a site owner, you will want to add/edit more and more.
Customizing Pages

Figure 5 displays a menu item that is called “Move”.  This allow a contributer to move data around the page in a “Drag and Drop” way.  This gives considerable flexibility to contributers.  So you may say to yourself, “I don't want my contributers to mess with areas such as side menu's and pictures.” That is easily restricted using the “Permissions” option of your menu.  There you can select permissions for each editable area on your page.  Even adding select groups.
When you are in edit mode and you have the reason to change a picture, Figure 7 displays your current
options.

 

 

Figure 7 - Changing an image

 

 

Here you can replace your image by selecting the reset option.  You select reset and then select Choose Image.  It will take you to the File Manager area and you then select which image you would like to change.  You select which image you want and then select update.  Your page will have the updated image.  You can also add a url to the image or create an image rollover here.  Follow the options from the menu's it gives and when you are done select the update button.

Selecting a Custom Template

In the menu while in edit mode, you have an option of “Custom Template”.  If there is additional things that are specific to a page or set of pages on an area of a site, you can select a “Custom Template” to accomplish this.  There are no custom templates on a clean install for 7thWeb CMS but if functionality is needed, contact your administrator or web designer/developer to create these.  You may even like to get the Developer/Designer Guide from 7thWeb CMS and design one yourself.  It will take some time to learn how to do this but the effort is well worth it.

Adding information to editable pages

As Figure 4 shows the areas outlined in red are editable areas, there is an option to add new data to a
page.  Move your mouse to the words “Add to Header/Main/Sidebar”, it will also highlight in gray.
When you select this, a menu pops up asking you what type of information you would like to add to
this area.    The menu is a list of “Blocks” that are installed in your Dashboard.  These are very flexible
and gives the contributer many types of data to insert.  Figure 8 shows you a partial list of items.

 

 

Figure 8 - Type of blocks to insert to pages

Normally, the Content Block or one of the image blocks are used by contributers.  In our example I will
select the Content Block.  Select the Content block and TinyMce will launch just like when I edited
content above.  Here, you will add your text and your in-line graphics to add to your page.  When your
finished adding the content, click the save button. 

 

 

 

Chapter two

Themes

Introduction

Themes are pre-built pages that give your site a custom look.  Themes are the layout and graphics of your site.  There are three themes that are available with a default install of 7thWeb CMS.  They are Plain Yogurt, Green Salad and Spatially Adjusted.  Spatially Adjusted is not available for immediate use out of the box.  You must install it under the Dashboard/Pages and Themes. Installing Spatially Adjusted will give you a simple example of installing an add-on Theme.

There are a lot of themes that you can get from the 7thWeb Themes .  Also, you can go to your favorite
search engine and type in “7thWeb CMS themes” and find a lot of themes there.  Just remember that these are often provided “As Is” and if there is a problem with it, you can email the creator or post on their forum to get more answers.

 

This is the definition of a theme per 7thWeb CMS
“Themes are collections of Templates. Themes each get their own sub-directory in the /themes/ directory ….. and think of the Theme as a package of Templates.

 

That is not the complete definition but it should suffice for now.

Installing a Theme

There are a few steps you have to do when installing a new theme.  You must have FTP privileges to upload the files.

•  Download the theme you would like it have.
•  Uncompress the files using your compressions software like WinZip or ZipGenius and save to
your local machine where you will find it easily.
•  Log in to your server via FTP and upload your themes to site root/themes.
•  Log in to your Dashboard and go to Pages and Themes.
•  If the themes were uploaded correctly, you scroll down to see the thumbnails of the theme(s)
you placed in the Themes directory.  There will be a set of buttons and you select the one that
says install.
•  The page will refresh and you will be given an option beside the new locations of your theme to
“Activate”.  Press this button and your site will then have that Theme as its default.

You should be aware that if there are any customized settings that have been done, they may be lost when activating a new theme.  Go to the forums before you activate new themes.

 

Creating a new theme

Go to the “ Help ” section to learn how you can create your own themes.  An alternative to the forums,
just take a look at a theme you like.  Review of the code will reveal that much of the code does not
have to be modified.  I have learned the easiest way (for me anyway) was to take a look at how the

page looks (looking at the code).  For background images, you may only have to replace them and all
the additional changes will be done in the CSS file for that theme.  This makes creating your own
theme fast and easy.  The only time consuming thing for me when I created my first theme, was getting my background image(s) the right size and opacity.  Otherwise, the second longest thing I had to do
was to modify the CSS file to the color and font attributes that I wanted to use.  It was that easy.  You
definitely can not create a custom theme in Droopal or Joomla this easily.  It took me about 30 minutes the first time.  Admittedly, I then spent several hours getting it just right (it was image sizes for multiple browsers and screen resolutions that had me stumped).  The CSS files will take a little time, but if they are documented well, you shouldn't have an issue changing them.  The cool thing about creating your
own theme is that you can customize it anyway you want.

 

 

Glossary of Terminologies

Dashboard Options

 

Dashboard: The admin panel. This is where you control everything behind the scenes. You are the puppet master.

Sitemap: The entire site at a glance. This is arranged in a Windows Explorer-like hierarchy - parent
pages appear as folders, with children pages listed inside them. Click any page to open the sitemap
options.

File Manager: Any file or image you’ve uploaded to the site will appear here. You can search for files based on the filename or the date you uploaded it. You can also upload files here.
Form Results: Any form you put on your site using the “Form” block type will output here. You can
click on the form name and see the results below the list. You can also output these results to an Excel
doc.

Users: All of the users registered on your site are listed here for your perusal and management. You can
view and edit their user details, deactivate users so they are no longer able to log in, or add new users.
Groups: List of all user groups you have created. Groups are useful in situations where you want to
limit permissions for an entire group of users - for example, if you wanted everyone in your human
resources department to be able to edit your Careers page, but you don’t want them mucking around
anywhere else, you could add them to a “Human Resources” group and give that entire group adequate permissions to edit that page.

Page Types: Lists the page types (templates), page attributes (fields you can set in the Page Properties pane), and single pages (one-of-a-kind page types you won't reuse elsewhere on the site) you have
installed on your site.

Themes: These are the “flavors” available for use on each page of your site. Here you can activate, inspect, or remove the theme.

Add Functionality: A list of installed block types and packages, as well as block types and packages currently available for installation.

Site wide Settings: Gives you access to options that will affect the entire site. Here you can adjust site permissions, editing preferences, debug level, and maintenance mode.

Jobs: A list of automated jobs installed on your site.

Return to Website: This exits the dashboard and takes you back to your homepage. You remain logged in, so you’ll still see the 7thWeb CMS menu and can still make edits.

Sign Out / Logout: You’re all done. This will sign you out of 7thWeb CMS and take you back to your homepage.

 

 

7thWeb CMS Menu Options

Edit Page: Reloads the current page with new menu options and editable blocks outlined in red. You can mouse over these blocks and click them to access their edit menus.

Exit Edit Mode: Saves your changes as a new version.  You can choose to add version comments to
make notes of what changed in this version. From here, you can choose to publish your edits and make
your changes public, or you can preview your edits and have the option to publish them at a later time.

Properties: All of the details of your page.

Page Name: This is the name of the page as it will be displayed in the auto-navigation blocks and the top of the browser window.

Page Alias: This is the vanity URL for the page you’re adding. It is automatically generated based on the page name, but you can change it if you like.

Date: The date the page was added. This defaults to the original date and time the page was added, but if you want to change the date yourself (to affect where it falls in chronologically-sorted auto
navigation blocks, for instance), you can change it here.

Page Description (optional): A brief description of the page you are adding.  This is also used as the short description search engines will display as your page summary.

Custom Fields: ?????

Meta Fields:

Theme/Design: Choose the look and feel of your page. This is where you select from page types and designs that have been installed on your site.

Choose a Page Type: A page type is a basic “skeleton” of a page, with a set arrangement of blocks. Choose a pre-made page type for your page here. How to add new ones??

Choose a Design: The design of your page is the particular flavor for whatever page type you have selected. Choose one of the designs available for your site here.  How to add new ones???

Versions: This is a list of all of the past and present versions of the page you’re viewing. Add Page: Adds a sub-page directly under the page you are currently viewing.

Type of Page: Select the page type you are adding. These are managed in the Dashboard. Standard Information:

Page Name: This is the name of the page as it will be displayed in the auto-navigation blocks and the top of the browser window.

Page Alias: This is the vanity URL for the page you’re adding. It is automatically generated based on the page name, but you can change it if you like.

Date: The date the page was added. This defaults to the current date and time, but if you want to
change the date yourself (to affect where it falls in chronologically-sorted auto navigation blocks, for instance), you can change it here.

 

Page Description (optional): A brief description of the page you are adding.  This is also used as the short description search engines will display as your page summary.
Help: Hi, you’re here! Clicking Help anywhere on the site will take you to these friendly help docs. If you’re still stumped or just craving some personal attention, send us an email at
support@7thweb.com.

Logout: This will log you out of 7thWeb CMS and take you back to your home page.

 

 

The following is from the “Site Builders” section of the “Help” area of 7thWeb CMS

 

7thWeb CMS's documentation and comments refer to a number of internal conventions that, when learned, should make 7thWeb CMS more accessible to developers and end users alike.
At a summary level: Every Page has editable Areas, defined by its Page Type. Areas contain instances of Blocks (defined by Block Types) which may be anything from editable HTML to a highly
customized survey. Each Page has its own Permissions and a Theme associated with it. Themes
contain Template files that determine presentation for a given Page Type.
Common Terms

Pages
A page in 7thWeb CMS is just like a page on any website: it typically fills the full browser, and be found at a unique URL. Pages in 7thWeb CMS can have pretty URLs or standard CMS-y URLs.

Every page has a unique cID ("c" stands for Collection -see below:) and a bunch of metadata about it in the Pages table.
There are some exceptions to this Page=Collection rule, some standard pages like login and register are called "Single Pages" and exist in their own directory in a 7thWeb CMS install. They are still skinned
through the CMS, see the bottom of this page for more explanation of the exceptions.

 

Areas
Areas in 7thWeb CMS are parts of a particular page that can be edited using the content management
system. Without any areas, a page would be completely static. Areas can have permissions applied to them, making it so that only certain kinds of blocks may be added to them, or they can only be viewed by certain people.

 

Blocks
Blocks are bits of content added to particular areas on pages. A block is an instance of a certain type of
content, as displayed on a page. When in edit mode, blocks may be hovered over with a mouse, clicked
on, and edited within the page itself. All blocks have certain bits of data in common, like the ID of the user who added them, or the date the block was created and modified.

 

Block Types
A block is the instance of content or functionality after it's been added to a page. The type of block determines how those blocks differ.

Types of blocks include:
•  Some HTML content
•  An in-page image gallery
•  A navigation list
•  A list of popular pages on a site
•  A survey or poll

All of these are types of blocks. When a block type is installed, an administrator is able to add that type
to an area on a page. When adding a survey to a page, for example, the survey is a block type, and the
actual survey added to the page, with its customized questions, answers and results page is the actual
block itself.

Blocks are typically self-contained, and blissfully ignorant of other items on a particular page. Every type of block has its own presentation layer, a form that gets called when it's being added, and a form that's called when it's edited. These forms are typically displayed in in-page popups dispatched by Concrete's interface layer. Developers interested in writing their own block types should check out the [[.:developers:developing blocks|blocks section of the developers manual.]]

 

 

Page Types

Like block types, 7thWeb CMS also has the concept of "page types." A page type is a template and
convention allowing different types of pages to be added in different areas of a website. Page Types are typically named and considered around functional requirements, rather than layout requirements. For example, here is a list of page types that might be found in a corporate website:

•  Home - A page type corresponding to the main home page of the site
•  Landing - A page type corresponding to one of the main sections of the site
•  Detail - A detail article page type
•  Press Release
•  News Article
•  Product

Page Types are typically made only for reusable pages (home is the one notable exception to this rule.) Single, one-off pages are described in "single pages" below.

 

Themes
Themes are the outer graphical skin of a 7thWeb CMS website. Separate from page types and single pages,
themes allow the same types of pages to appear differently in different areas of a website. For example,
an article within the sports section of a newspaper's website could have a completely different theme
than an article page in the finance section. For more information about themes, see [[theme intro| Introduction: Understanding Pages, Page Types and Themes]]. ==== Permissions ==== Disscuss what we have now.

 

Page & User Attributes
While all pages and users have data that's associated with them, Concrete allows site administrators to create their own bits of data and associate these with pages and user accounts. These are known
throughout Concrete as "attributes." Example of page attributes might be:

•  "Exclude From Nav?" (check box)
•  "Meta Keywords" (text field)
•  "Additional Description" (text box)

Examples of user attributes:
•  "Gender" (radio button w/Male and Female available)
•  "State/Province" (select menu)

 

Users
Users are accounts used to edit a 7thWeb CMS-enabled site. At its core, a user record in 7thWeb CMS consists solely of an ID, a unique username, and an email address. Extended user attributes can be added in the dashboard.

Groups
Groups are simply a way of combining users into a particularly semantic...well...//groups!// Groups are used primarily in 7thWeb CMS permissions: a given group of users can be allowed read, edit, delete, and administrative access to pages, areas and even individual blocks.

 

Developer Terminology
Interesting in developing for 7thWeb CMS? You probably ought to understand the following concepts, in addition to those above:

Collections
In versions of Concrete before 7thWeb CMS, Collections mapped entirely to Pages (see above.)
Collections were so-named because they were "collections" of blocks. However, in 7thWeb CMS, a
collection can exist without a record in the Pages table, and thereby group blocks together without
having any presentational aspect to it, or appearing in the sitemap. Furthermore, these collections can
be called programatically, which can be helpful for programmers who want to use the power and
flexibility of built-in blocks programmatically, without having to worry about where a page lives, its
permissions, etc...

 

 

Single Pages
Single pages are Page records that don't have a page type. Instead, they're one-off pages that map directly to a file in the file system. These are nice because they can be added directly to the file system,
and, once installed in the dashboard, exist at http://www.yoursite.com/pagename/. Generally it's a nicer
practice to use single pages where you know a particular page will only be needed once. Examples of single pages automatically created by the system include:

•  Login
•  Register
•  Various dashboard pages.

Single pages use Concrete's Model-View-Controller, which makes them useful when using 7thWeb CMS as an application platform.

 

The default installation of Concrete in setup in the following manner. (The root directory in these examples corresponds to the root of your 7thWeb CMS website. These examples also assume you are running one website, and not sharing the 7thWeb CMS core amongst several sites.)

 

 

Client Application Contents
These are directories directly within your web root.

/blocks

This directory contains block types used throughout your 7thWeb CMS site. This will typically be empty on an initial installation - core block types are installed inside the concrete directory.

/concrete

This is the Concrete Application directory. 7thWeb CMS owns these files - they should typically be off
limits in most projects. For more information about what's inside this directory, skip down to 7thWeb CMS Internal Contents

/config

This directory contains “site.php,” the configuration file added by the 7thWeb CMS installation program.
This stores your database connection settings and some server-specific information. Additionally, this
directory contains “site_theme_paths.php,” which allows a developer to manually specify certain
themes for certain areas of a site.

 

/controllers
The controllers directory contains controllers for any single pages, views or dashboard modules used
by your website. Click here for more information about controllers and 7thWeb CMS's MVC syntax.

 

/elements
The elements directory is a place for you to keep snippets of PHP code reused throughout your site.

Examples of this might include a header menu or a reused sidebar. Elements are presentational in
nature; if you have special functions or libraries you want to reuse for your website, these should go in ”/libraries” or ”/helpers.”

 

/files
The files directory holds all files added by your user's through the CMS. Additionally, the files directory may hold cache information or logs.

 

/helpers
The helpers directory store reusable functions based on the type of assistance they provide. You can
include your own helpers in your helpers/ directory, as well as use helpers that come with 7thWeb CMS. A complete list of 7thWeb CMS helpers is available here.

/libraries

The difference between helpers and libraries is largely a semantic one. Helpers are typically smaller in scope, and assist in one specific purpose, while libraries serve an underlying purpose. For example, 7thWeb CMS ships with a “feed” helper. This feed helper exposes a couple of methods for the parsing of RSS and ATOM feeds; it is the public accessors to this functionality. However, the feed helper itself is really just a simple gateway to the very nice SimplePie library, which itself is contained in
“7thWeb CMS/libraries/3rdparty/simplepie.php.”

 

/mail
The mail directory contains mail templates that your site uses, in conjunction with the Mail Helper.

 

/models
Items in the models directory correspond to database-backed items in your custom 7thWeb CMS
application. For example, if you added a “properties” table to your database, you'd need a PHP class for querying this information. In 7thWeb CMS, you'd add “property.php” to your models directory. Models are mostly optional, but if your model extends the Model class (loaded by the 7thWeb CMS core), you'll be able to use ADODB Active Record syntax to query it.

/single_pages

Single pages - one-off pages like /login, /register, etc… - live in here. They inherit the active theme,
and can have their view templates overridden by templates in a given theme directory. Single pages are most useful when paired with Concrete's MVC syntax.

 

/themes

Directories corresponding to your site's theme live here. 7thWeb CMS ships with a default theme, but you can add your own theme to this directory and activate it in the dashboard.

 

/tools

Tools is a catch-all directory for other PHP scripts that you might need to integrate with 7thWeb CMS.
These scripts are wrapped in 7thWeb CMS, and have access to the database and everything else, but aren't wrapped in 7thWeb CMS permissions, have no MVC support, etc…
7thWeb CMS Internal Contents

These are the items inside the ”/concrete” directory, typically off limits to all but the most wizened or foolish developers.

/config

Concrete's internal configuration directory, and it contains the main installation database file, as well as some constants that rarely change.

/css

This contains presentational style sheets used by the content management system, including its menus, dialog boxes, the dashboard and rich text editor.

/dispatcher.php

The main runtime of the program, dispatcher.php is responsible for parsing every request to 7thWeb CMS.

 

/flash
This contains flash assets used by the CMS, including a flash uploader, image thumbnailer, etc…

 

/helpers
This directory contains 7thWeb CMS's core helpers. Application helpers should go into their webroot.

 

/images

This directory contains images used by 7thWeb CMS's interface components.

/js

This directory contains JavaScript used by 7thWeb CMS's core components. 7thWeb CMS makes extensive use of the Jquery library, as well as a number of custom JavaScript components.

/libraries

The core libraries directory contains libraries used 7thWeb CMS. These include some relating to
7thWeb CMS's MVC syntax, as well as some third party libraries used by various components of the
system.

 

/models

Most of 7thWeb CMS's internal CMS components keep their data access classes within the models directory.

/packages

The packages directory contains directories corresponding to various “packages” available to the
system. These are so named because they can be deployed to all 7thWeb CMS websites on a given server
(if those websites all share the same core libraries.) Individual sites can also make use of packages as
well, by copying them into the packages directory and installing them. Packages can include single
pages, blocks, elements, dashboard modules, controllers, mail templates and themes. At this time, the
only package available is the core package, which is responsible for setting up the default 7thWeb CMS
theme, its login/registration process, the dashboard, and the block types which ship with the system.

/startup

Items within the startup directory are subroutines included during a page load by dispatcher.php

 

/tools
The items within the tools directory are interface components used by the content management system. These include popup windows, etc…