QwikZite Users Manual

QwikZite.Net: knowledge and support network for QZ users
| Home | Manual | Tips & Tricks | Canteen | Helpdesk |EnglishDutch/NederlandsPapiamentu

Search in this site with Google:



Introduction
QwikZite at a glance
Access procedures
General functions
Menu Sitestyle
Menu Page
Menu Button
Menu News
Menu Link
Menu Foto
Menu File
Menu Topic
Menu Defaults
Structure of the site
Working with sitestyles
Working with buttons
Limitations of the web
Working with fonts
Working with colors
Working with images
Working with backgrounds
Working with sizes
Working with HTML
Working with webtext
The first steps
Contents of this page: Working with buttons | Simple site with 1 level | Simple site with 2 levels | Complex site with 2 levels



Working with buttons



While making a simple site is a piece of cake, making a more sophisticated site navigation system may be rather complicated.
  • Navigation in QwikZite involves 2 options in the 'Button' menu:
    - Button visible on all pages or belongs to page ...
    - Button refers to page ...

  • Besides, it involves an option in the 'Page' menu:
    - Page inherits buttons from page ...

How it works is explained below with the help of 3 examples.
  • Example 1: Simple site with 1 level
    Site with an identical series of buttons on all pages.

  • Example 2: Simple site with 2 levels
    Site with standard series of buttons and extra buttons on the 2nd level.

  • Example 3: Complex site with 2 levels
    Site with differentiated button series, where the homepage series of buttons is no longer displayed on all pages.




Example 1: Simple site with 1 level

Site with an identical series of buttons on all pages:

Page
100 HOME:
Page
200 PRODUCT:
Page
300 MANUAL:
Page
400 CONTACT:
HOMEHOMEHOMEHOME
PRODUCTPRODUCTPRODUCTPRODUCT
MANUALMANUALMANUALMANUAL
CONTACTCONTACTCONTACTCONTACT


The texts are the button 'Titles' which are displayed at the frontend of the site.


Requirements in the 'Button' menu:

Beside the above button 'Titles', the following input is made:
100 HOMEvisible on all pagesrefers to page: 100
200 PRODUCTvisible on all pagesrefers to page: 200
300 MANUALvisible on all pagesrefers to page: 300
400 CONTACTvisible on all pagesrefers to page: 400


The left column texts are the 'Working titles' of the buttons. Though invisible, their alphabetic order determines the order of the 'Titles' at the frontend.


Requirements in the 'Page' menu:

None.
The pages do not need to inherit button series, as all buttons are already made visible on all pages in the 'Button' menu.





Example 2: Simple site with 2 levels

Site with the following series of buttons on the pages:

Page
100 HOME:
Page
200 PRODUCT:
Page
300 MANUAL:
Page
400 CONTACT:
HOMEHOMEHOMEHOME
PRODUCTPRODUCTPRODUCTPRODUCT
MANUALNew productsMANUALMANUAL
CONTACTOld productsIntroductionCONTACT
MANUALRequirements
CONTACTFunctions
Problems
CONTACT


Page
210 New products:
Page
220 Old products:
etc.

HOMEHOME
PRODUCTPRODUCT
New productsNew products
Old productsOld products
MANUALMANUAL
CONTACTCONTACT



Requirements in the 'Button' menu:

This is the input of the buttons which are visible on all pages:
100 HOMEvisible on all pagesrefers to page: 100
200 PRODUCTvisible on all pagesrefers to page: 200
300 MANUALvisible on all pagesrefers to page: 300
400 CONTACTvisible on all pagesrefers to page: 400


The following buttons are only visible on page 200 PRODUCT:
210 New productsbelongs to page: 200refers to page: 210
220 Old productsbelongs to page: 200refers to page: 220


The following buttons are only visible on page 300 MANUAL:
310 Introductionbelongs to page: 300refers to page: 310
320 Requirementsbelongs to page: 300refers to page: 320
330 Functionsbelongs to page: 300refers to page: 330
340 Problemsbelongs to page: 300refers to page: 340


With the above input, all buttons on the pages 100, 200, 300 and 400 are now defined.

And, in fact, at the same time specific button series have been defined belonging to page 200 (button series 210/220) and page 300 (button series 310/320/330/340). These pages are hereafter referred to as 'parent pages'.


Requirements in the 'Page' menu:

If, at present, the button 210 New products would be pushed to open the page 210 New products, you would only see there the buttons visible on all pages (buttons 100/200/300/400) since no other buttons have been defined to belong to that page.

To make the buttons 210 and 220 also visible on the page, you utilize the 'inherit' function included in the 'Page' menu: indicate the 'parent page' from which the button series shall be taken over. In this case:
page 210 New productsinherits buttons from page: 200 PRODUCT


Now, from parent page 200 the button series 210/220 is taken over on page 210.

This shall be applied to all pages of the 2nd level, so also:
page 220 Old productsinherits buttons from page: 200 PRODUCT
page 310 Introductioninherits buttons from page: 300 MANUAL
page 320 Requirementsinherits buttons from page: 300 MANUAL
page 330 Functionsinherits buttons from page: 300 MANUAL
page 340 Problemsinherits buttons from page: 300 MANUAL






Example 3: Complex site with 2 levels

Site with differentiated button series, where the homepage series of buttons is no longer displayed on all pages:

Page
100 HOME:
Page
200 PRODUCT:
Page
300 MANUAL:
Page
400 CONTACT:
HOMEHOMEHOMEHOME
PRODUCTPRODUCTMANUALPRODUCT
MANUALNew productsIntroductionMANUAL
CONTACTOld productsRequirementsCONTACT
Functions
Problems


Page
210 New products:
Page
220 Old products:
etc.

HOMEHOME
PRODUCTPRODUCT
New productsNew products
Old productsOld products



Requirements in the 'Button' menu:

These are the buttons visible on page 100 HOME:
100 HOMEvisible on all pagesrefers to page: 100
200 PRODUCTbelongs to page: 100refers to page: 200
300 MANUALbelongs to page: 100refers to page: 300
400 CONTACTbelongs to page: 100refers to page: 400


Major difference with example 2 is that the home page buttons are no longer visible on all pages and that page 100 HOME has become the parent page for the button series 200/300/400.

It is common usage to make the 'Home' button visible on all pages, to avoid that visitors land at a dead end.

The following buttons are only visible on page 200 PRODUCT:
200a PRODUCTbelongs to page: 200refers to page: 200
210 New productsbelongs to page: 200refers to page: 210
220 Old productsbelongs to page: 200refers to page: 220


For reference to page 200 an extra button with the working title '200a PRODUCT' is made, belonging to page 200. This is not the same button as '200 PRODUCT' since that button belongs to page 100 and is only visible there.
Both buttons refer to the same page and have the same title, 'PRODUCT', but belong to and are displayed on different pages.

In the same manner, the following buttons are only visible on page 300 MANUAL:
300a MANUALbelongs to page: 300refers to page: 300
310 Introductionbelongs to page: 300refers to page: 310
320 Requirementsbelongs to page: 300refers to page: 320
330 Functionsbelongs to page: 300refers to page: 330
340 Problemsbelongs to page: 300refers to page: 340



Requirements in the 'Page' menu:

First of all, the pages of the 2nd level:
page 210 New productsinherits buttons from page: 200 PRODUCT
page 220 Old productsinherits buttons from page: 200 PRODUCT
page 310 Introductioninherits buttons from page: 300 MANUAL
page 320 Requirementsinherits buttons from page: 300 MANUAL
page 330 Functionsinherits buttons from page: 300 MANUAL
page 340 Problemsinherits buttons from page: 300 MANUAL


As on page 400 CONTACT the same buttons shall be displayed as on page 100 HOME, also here you can utilize the inherit feature:
page 400 CONTACTinherits buttons from page: 100 HOME






Go to top | Simple site with 1 level | Simple site with 2 levels | Complex site with 2 levels


     



Latest changes in this page
Developed with QwikZite (version 1.12)