Table of Contents
Previous | Next

Site Structure and Site Nodes

An EndApps-based web application is structured to accommodate both the primary functions of the application as well as the configuration, administrative and data management tasks that make for an easy-to-use and responsive User Interface.

EndApps site nodes and structures

1) End-user area

2) Site Admin area

3) Data Admin area

4) User and Role Management area

5) Document Publication area

6) Landing pages repository area

7) User Profiles

End-User Area

The End-User Area represents the primary function of the web application.

It is the site’s Raison d'être.

The End-User area is the primary business area of the site. In the sample website, the End-User Area contains two illustrative domains

1) Job Board

2) Admin

The illustrative domains are further discussed in the chapter: Sample Illustrative Domains.

Site Admin Area

The Site Admin Area is the primary administrative, configuration and maintenance area of the website.

It is made up of the following sub-areas.

1) Metadata admin

2) Site properties management

3) Rules management (Rules and flows)

Data Admin Area

The Data Admin Area allows administrative personnel to interact with and change domain specific data that is displayed and used in the End-User Area.

User and Role Management Area

The User and Role Management area is primarily responsible for the creation and management of user accounts and user roles.

In this area of the web application, users can be added to roles and roles empowered with permissions.

Document Publication Area

To upload and publish a document, or to delete a document publication, you must be in the Data Manager Admin mode. Currently only Microsoft Word 2007 and later versions maybe uploaded.

An EndApps-based web application includes the ability to publish Microsoft Word documents as site content.

To upload and publish a Word Document, navigate to:

“/WebDocs”

Picture 134

Figure : WebDocs showing two published documents

By default, a newly published document will be added as a sub-folder of the WebDocs area. For example, if you publish a document titled “Q1-Sales”, the path to the index page of the document will be:

“/WebDocs/Q1-Sales”

Alternatively, you may choose to publish to a different folder like “Sales/2014”. If we publish a document titled “Q1-Sales” to the sales folder, the path to the index page of the document becomes:

“/Sales/2014/Q1-Sales”

Picture 136

Figure : WebDocs - Document Upload

Landing pages repository area

In an EndApps-based website, shortcuts may be overridden by custom html landing pages.

The Landing Pages Repository displays the uploaded custom html landing pages.

The naming convention for a custom landing page is:

“LandingPagesRepository_

So a custom landing page that overwrites the site’s home page will be:

“LandingPagesRepository_home”

Picture 137

Figure : Landing Pages Repository

User Profiles

An EndApps-based website can support multiple User Profile types.

Having a variety of Profile Types can be useful in the following ways:

1) Grouping similar site users

2) Segregating search – makes it easier to find users

3) Tailoring user information segments

Here are a few examples on how Profiles and Profile Types may be used

1) An investment fund may group users by continent or risk tolerance. Examples

a. Conservative, Moderate, Aggressive

b. North America, Europe, Asia, Africa

2) An agricultural community may group users by occupations. Examples

a. Farmers, Researchers, Vendors

3) An IT firm may group users by job role. Examples

a. Architects, Managers, Analysts

For each profile type, an administrative user is able to configure the different data segments that the user is asked to fill out after registering on the site.

Picture 138

Figure : User Profile segments in Edit Mode

Picture 139

Figure : User Profile public view

Table of Contents
Previous | Next