Theme Layout

Learn about the files implementing the built-in functions of your portal.

What are common files?

Common files implement the built-in pages and functions of the portal, such as registering a new member, making a booking or paying an invoice. You cannot delete these pages as they are required for the portal to function correctly, but you can change the way they look and where each component is placed within them

image__86_.png
Common files
 

You access the code in this pages from the "Common Files" section in the template editor. 

Master Page

Provides common mark-up for other pages to use.
 

What's a master page?

There are some sections on the portal which are repeated in every section. For example, the navigation menu and the content of the footer is very similar in every section. Also, there are files which need to be included in every page, such as the CSS and JavaScript files required for the site to look and function correctly. To avoid having to include all this HTML markup in every single page, Nexudus uses master pages. This page contains all the common elements to all the pages in the site.

image__87_.png
master.master file
 

By default, there are two master pages in your account, named "master.master" and "signup.master". This pages contains all the common elements and gives the general structure to the space website for the general and sign-up pages respectively.

How does it work?

A master is a normal HTML page, it can use any of the DotLiquid code as any other page, but it can also define sections or placeholders (known as blocks in DotLiquid) where other pages using this master page can insert content

image__88_.png
Light blue sections pulling data from master.master
 

The light blue sections represent the content defined in the master page. This content is rendered in every page. The master page also defined a placeholder (block) where child pages can inject content.

The light orange sections represent a child page using the placeholders defined in a master page. The child page injects content into the placeholder defined in the master page.

When defining a block in a master page, you can provide some content inside that block. This content will be only rendered if the child page using the master page does not provide content for that block. Effectively, by doing this you are providing a default content for the place holder, but any child page using the master page can override this content with its own. 

Custom Pages

Learn how to add your own pages.
 

What are custom pages?

Custom pages are any other pages you want to display in the space website. These pages are typically content pages, like a description of the space, a presentation for the team, a FAQs page or a place where members can download your printer drivers.

Content pages are written in the exact same way as built-in pages, but they usually have access to a limited set of data. For example, a custom page does not have access to the list of members in the space

image__89_.png
Adding a custom page
 

To create a custom page, use the "Custom pages" node in the template editor tree. When creating a custom page, you will need to give it a name (ending with .htm, .js or .css) and specify the language in which it is written. When browsing the space website, only those custom pages in the visitor's language will be displayed.

You can make custom pages private so they are not displayed in the navigation bar and only visitors with the exact URL can visit them. You can also password protect custom pages.

By default, custom pages are displayed in the navigation menu, under the menu item with the name of the space.

image__90_.png
Custom page 
 
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Please sign in to leave a comment.