ReadMe Documentation

This is the general documentation for all pages and page types for this site. 

General UI Elements

- The social nav on the header and the footer is hardcoded - but the links for each social media in the nav are pulled from an unlisted page called "social_media_info". In this section you copy and paste the 4 social media source links, split by a horizontal line under each. The order, in order to correspond to the correct social media platform - must always be 1. Facebook, 2. Instagram, 3. Twitter, 4. LinkedIn.

- Items can be added to the footer nav by adding the tag "footer_nav" to any page.

There are 4 page types that must remain with the "show sidebar" option clicked. These are petition, volunteer, feedback (contact), and event pages. If this does not happen the layout will not be correct.

- The footer form that appears on all pages except events, signups, volunteer signups, and donations - pulls from a signup page called footer form. The editable title at the top of it pulls from the content section of this page.


- The video for the homepage header is hardcoded. It must be loaded into the theme files in order to be played - and we should decide on a name for the files ASAP. If there is no video for the homepage header - remove the tag "has_video" from the home_header subpage of the homepage - and a photo will be loaded instead. The photo that will appear is the photo in the home_header attachments that has either the suffix "-header" or the prefix "header-".

- The header text is written in the home_header headline.

- The little "about the minister" home section is pulled from the homepage content section. The headline is pulled from the homepage headline. The button on desktop is pulled from the homepage content section. However on mobile this button is below both the about section and the data section, so it is hardcoded. Approved text is required that will be used across all themes to send users to the "about" page

- The "latest data"  section on the homepage is pulled from the "data_home" subpage of the homepage. The headline and content are pulled from here, and each of the 3 data points are a featured content slide. In these - the number is the "label", the data label is the "headline/action", and the image is the attached image. Don't worry about putting in the correct page slug for "page to feature" (you are required to) - but the link does not exist in the code so it's entirely irrelevant.

- The three blog posts featured on the homepage are pulled with the tag "highlight" on each of the posts. They are limited to 3 - so if there is more than this they will not show will pull the 3 most recent with this tag.

- The social media section slider and text is pulled from the home subpage called "social_media_home". The slider can support up to 7 embeds from FB, Twitter, and probably soundcloud and/or spotify as well. The subpage headline is the section header, and then the content section is split by horizontal lines. The first item must always be the text to display in the section, and all the following are where links for embeds can be copied and pasted. As long is an embed is not the first, you can erase and add as many lines, followed by links, as you wish.

- The event pulled to the homepage is pulled with the tag "home_event". The headline for this section is hardcoded.

Basic pages

- If you want a header on a basic page - you need to place one photo in the featured content slider. Do not put a headline or else it will not render properly. Just a label, a photo, and a page to feature (again this is irrelevant because the link has been taken out). The headline of the page is the title text that will show in the bottom left of the header image.

- Basic pages can also not have a header - and photos can be added to both basic page types in the content section easily.

- Blockquotes will render as they do in blog pages.

The About the Minister page and the Homepage are also basic pages that have their own unique styles.

- About the Minister must have the tag "bio" in order to have these unique styles applied (the same styles as the longform blog post)

- About the Minister can also have a header added the same way that other basic pages with headers can - with a photo without a headline in the featured content slider. About the Minister follows the same styles for embeds etc as the longform blog post. This is the only page in the site that depends on a keyword in the slug to call the correct template and styles. At the moment it is coded so that any page with "about" in the slug will use this template - but we can obviously find a more suitable word.

Blog pages (updates - "longform" and others)

Longform blog posts will render with the longform styles if they have the tag "longform" added. The header for these can be added with the featured content slider - again with no headline text and following the same method as the other page headers.

- The text that will appear on the bottom left of the header image will again be the headline of the blog post.

- Style for longform posts include support for twitter embeds, photos, blockquotes, and the different background color (white) for the post content.

Non-longform blog posts can also have header images - but these will not render full-width as the longform posts do. This header is again pulled from the featured content slider - which must be added in the same way as all the others.

- All blog posts will have their tags listed out on or above the header image.

Blog cards - i.e. blog post excerpts shown on the updates page, homepage, and under "ook interssant" - include the blog post headline, 1 tag pulled from the blog post, and if desired, a photo which can be added in the social media tab of the blog post's settings page. Keep in mind this means that the header image on the blog post's respective page, and the image shown on the blog card can be different. Of course to make them the same - simply add the same photo to both the featured content slider and the social media section.

Thema's basic page

- This page shows all published subpages under "themas". The image for each is pulled from the individual page's files with any photo that has "-header" in the file name. This includes the Themas main page header itself which unlike almost every other header on the site - is pulled this way as well. 

- The intro text / "themas" text on this page is pulled from the themas page headline, which overlays the header image, and the text below is pulled from the themas page content section.

- The text on top of each of the other images is the page headline and also the text content from the page's content that is above the horizontal line.

- The text below each image is the page's content below the horizontal line and a link that is hardcoded and leads to the topics main page.

Individual "thema" pages can have a header by adding a photo - in the same way as other pages - to the featured content slider. 

Signup page

- The signup page header is pulled as almost all the rest are - with the featured content slider that does not have a headline/action text. The arch overlay will remain despite the photo chosen.

- The image for mobile is separate ( as there is a great degree difference in size and orientation) - and lives in the page's attachments. It must have "mobile-" in the file name to appear.

- All images (besides the header image) included in the content section of the page will have rounded corners and be centered.

- The bottom button that scrolls the user to the form is hardcoded.

Event cards / event pages 

- Event cards - i.e. the ones shown on the Agenda page and on the homepage, pull the event headline, date and time, and the event description (truncated to 15 words). If the event has a featured content slider image (formatted as oh so previously mentioned) - then this will appear above the event info in the card.

- The photo in the featured content slider also is shown on the header of each event page above the RSVP form.

- If the event has "Online" in the "Venue Name" field - the event details will show a little computer icon and the word "Online". You can also alternatively, put a link in the Venue Name section - and the computer icon will also show up there, along with the link to the Zoom, webinar, etc.

- If the event is in a physical location - then simply fill in the address, venue name etc, and this will show in the event details section with a geo-location pin and the address and venue name, along with a link to google maps with the information.