Page structure

The way we organised front office management aims at the following objectives :

Galaxy CMS renders HTML pages, with some parts coming from the theme, some other parts created by the system.

<!DOCTYPE html>
<html lang="en">
<head>

  <!-- contains code generated by the system -->

  <!-- START [HEAD] THEME CONTENT 
    
    see file theme/head.html
    you can include here your CSS for examples
    
    END [HEAD] THEME CONTENT-->
</head>


  <!-- START [HEADER] THEME CONTENT
    the body is inside the header of the theme
    header/header1.html (based on the selected header)
  -->
<body> 
  <!--  END [HEADER] THEME CONTENT-->
  

  <!-- START [PAGE] THEME CONTENT
    the content of your page template will go here
    END [PAGE] THEME CONTENT-->



  <!-- START [BOTTOM] THEME CONTENT 
    
    see file theme/bottom.html
    you can include here your JS for examples
    
    END [BOTTOM] THEME CONTENT-->

</body>
</html>

Before the page and after the page we can have a header and a footer. It often contains navigation, footer, cookie messages, etc…

They are in the header / footer folders. The user can choose here the different headers and footers. Each block inside is a syndicated block.

+-- theme
|   +-- footer
|       |-- footer.html
|   +-- header
|       |-- header.html

Pages are a set of « predefined » templates, so it’s easier for the hotel/producer to build pages. Pages appear when you click on “new page” in the backoffice.

These templates are our html files in the page folder. There are 2 types of pages : simple page or collection (collection = detail page)

A detail page will create automatically one page for each item of a module. ( Unit Data )

Templates can be:

Completely fixed
Have a controlled level of freedom (On/off Blocks)
Free through composer

Page templates can be configured as « Single usage » or can be used as many times as desired.

PreviousTheme NextTemplate engine for logic

Last updated 5 years ago