Modules

#module_achievements

Activated by tag module_achievements on a basic subpage - this will load in the animated achievements - specifically created for the homepage.

NOTE: Please reach out to For Purpose if you want to make any tweaks or modifications to this module as all data and content are hard-coded due to the custom animations used here.

module_action_panels

Activated by tag module_action_panels on a basic subpage - this module expects 2 nested subnav sorted basic pages. Each of these child pages will have a page tag action_panel:XXX tag where XXX is a data tag on the landing page we want to link to.

Example Usage:

The "Our People" landing page (/people) has a page tag ap_our_people. This is the data tag used by one or more action panel modules across the site.
The "Our Story" landing page (/story) has an action panel subpage - which has two subpages - one of them has the page tag action_panel:ap_our_people.
So when the "Our Story" page is rendered - at the bottom of the page the user will see one of the panels linking to the "Our People" page.

Data Mappings:

For a tile with tag action_panel:XXX:

• Tile headline = Headline of recruiting page with datatag XXX.
• Tile descripton = Content of recruiting page with datatag XXX.
• Tile URL = "Page to promote" URL of recruiting page with datatag XXX.
  • If instead the panel is sending users to an external link (Ex: The ReoMaori site) - There needs to be an additional nested redirect page underneath the recruiting page to be able to enter the URL. Additionally the action panel page should be tagged external_link so the URL opens in a new tab.

module_board_directory

Activated by tag module_board_directory on a directory subpage - we render all matching profiles in a 6 column grid. Clicking on each individual person will launch a modal displaying their biography.

The profiles are ordered by occupation in the following order:

1. Toihau | Chair
2. Toihau Tuarua | Deputy Chair
3. Hautū
4. Kaiwhiri | Board Member
5. Tumu Whakahaere | Chief Executive
6. ....Any other occupations

Data Mappings:

• Module Header = Directory headline
• For each profile with tags (set in Directory Settings):
  • Signup Profile Image URL
  • Signup Published Name
  • Signup Iwi (if custom field iwi has a value and custom field Hide Iwi is unchecked)
  • Signup Occupation
  • Signup Profile Content (loaded inside pop-up modal)

module_card_carousel

Activated by tags module_card_carousel and module_card_carousel:XXX on a basic subpage. XXX is the datatag added to a different page on the site. This module will load a carousel of cards for all nested published pages underneath the page with the XXX datatag.

Data Mappings:

• Module header = page headline
• Module text = page content
• A card for each page nested under the datatagged page

module_card_grid

Activated by tag module_card_grid on a blog subpage - this module will render a three column card grid - where each published blog post in the blog is rendered as a card. This module is currently used on three different blogs: news, he-muka, and reports.

For any filter_XXX tags on any of the published blog posts - a toggle filter willb e added to the top of the card grid module.

module_concertinas

Activated by tag module_concertinas on a basic subpage - this module will render each nested child basic subpage as a concertina. The concertinas willappear stacked in order. Upon clicking on one of the concertina buttons - it will expand to show the content beneath.

Data Mappings

• Module header - Headline
• Module description - Content
• Then a concertina will be rendered for each published basic subpage:
  • Concertina "tab" button text - Headline
  • Concertina content - Content

module_concertina_tabs

Activated by tag module_concertina_tabs on a basic subpage - this module will render each nested child basic subpage as a concertina. On desktop the concertina "tabs" (button/toggles) will appear staced on the left column and the concertina content will appear in the right column. Only one concertina can be open at a time (with the open one closing automatically). On mobile this module behaves like the normal concertinas module - where the content will appear underneath the corresponding "tab".

Data Mappings

• Module header - Headline
• Module description - Content
• Then a concertina will be rendered for each published basic subpage:
  • Concertina "tab" button text - Headline
  • Concertina content - Content

module_faq_topics

Activated by tag module_faq_topics on a basic subpage - this module will render a tile for each published nested "FAQ" page and will render a concertina for each published "Question" underneath it.

Once a user clicks on one of the FAQ Topic "tiles" - the topics will fade away and the individual questions within the selected topic will be shown as expandable concertinas. At the bottom of each topic question list there is a "Back to topics" button which will hide the current questions and show the topic tiles again. Additionally there is a "Share" which will copy the selected Topic FAQ URL to the users clickboard for easy sharing.

Data Mappings:

• Module header = basic page headline
• A Tile will be rendered for each published nested FAQ page:
  • Topic Title = FAQ page headline
  • For each nested published "Question" page a concertina will be rendered:
    • Concertina Button = Question page headline
    • Concertina Content = Question Q&A "Answer"

module_featured_page

Activated by tags module_featured_page and module_featured_page:XXX on a basic subpage. The XXX is a datatag which determines where the featured page is pulled from.
On this site it is most often wired into the News blog and highlights the most recent blog post. Alternatively - there is a layout:featured-page if you want to keep the layout but be able to customize the page data.

Data Mappings:

• module headline = blog post headline
• module text = blog post before the flip
• module image = blog post image
• module button label text = "Read more"
• module button URL = blog post URL

module_feedback

Activated by tag module_feedback on a feedback subpage - this module will render a banner that reveals a feedback form.

The banner will display with hardcoded headline "Can't find what you are looking for?" and a "Send a message" button. Upon clicking this button - a form will be revealed with the following fields:

• First name
• Last name
• Email
• Topic (dropdown)
• Type your message here

This module was specifically created for the /faq page - but can easily be adapted if desired to be used elsewhere on the site.
To help ensure that user feeback is seen - it is recommended that a TTW admin follows the feedback pages in NationBuilder to be notified of form submissions.

module_feedback_form

Activated by tag module_feedback_form on a feedback subpage - this module will render a feedback form with the following form fields:

• First name
• Last name
• Email Address
• Organisation
• Your message

This module was specifically created for the /language-planning-contact page - but can easily be adapted if desired to be used elsewhere on the site.
To help ensure that user feeback is seen - it is recommended that a TTW admin follows the feedback pages in NationBuilder to be notified of form submissions.

module_history_timeline

Activated by module_history_timeline on a basic subpage - this module renders a two column timeline with each nested basic subpage representing an event on the timeline.

Data Mappings:

• Module header = page headline
• Module description = page content
• For each nested basic page an event on the timeline will be created:
  • Event headline = subpage headline
  • Event Date = subpage publish date
  • Event description = subpage content
  • Event image = subpage meta image

module_our_partners

Activated by tag module_our_partners on a basic subpage - this module will render the "partners" (nested child pages) in a two column grid.

Data Mappings:

• Module header = page headline
• A "partner" item will be rendered for each nested basic page:
  • Partner name - subpage headline
  • Partner description - subpage content
  • Partner logo - subpage meta image
  • Partner website - nested redirect subpage "URL to redirect to"

module_quick_links

Activated by tag module_quick_links on a basic subpage - this module expects 3 nested subnav sorted basic pages. Each of these child pages will have a page tag quick_link:XXX tag where XXX is a data tag on the landing page we want to link to.

Example Usage:

The "News" landing page (/news) has a page tag ql_news. This is the data tag used by one or more quick link modules across the site.
The "FAQs" landing page (/faq) has quick link subpage - which has three subpages - one of them has the page tag quick_link:ql_news.
So when the "FAQs" page is rendered - at the bottom of the page the user will see one of the buttons linking to the "News" page.

Data Mappings:

For a button with tag quick_link:XXX:

• Tile headline = Headline of a basic or recruiting page with datatag XXX.
• Tile URL = URL of the basic page or the "Page to promote" URL of recruiting page with datatag XXX.
  • If instead the panel is sending users to an external link (Ex: The ReoMaori site) - There needs to be an additional nested redirect page underneath the recruiting page to be able to enter the URL. Additionally the action panel page should be tagged external_link so the URL opens in a new tab.

module_recruiting_banner

Activated by page tag module_recruiting_banner on a recruiting subpage - this module will render a full-width banner link.

Data Mappings:

• Banner header = recruiting page headline
• Banner text = recruiting page content
• Banner button text = "Haere"
  • Banner button text can be overridden by adding a page tag button_text:XXX to the recruiting page - where XXX is the button label text you want to display
• Banner button URL = recruiting "Page to promote" URL
  • If you want to link to an external page - add a nested redirect subpage and add page tag external_link to the recruiting subpage

module_signup_form_lfe

Activated by tag module_signup_form_lfe on a basic subpage. This module was specifically created for the /lfe page. It is a full width banner with a button and when clicked it opens a modal. The modal contains a form that will sign the user up on the ReoMaori site.

The form will have the following fields:

• First Name
• Last Name
• Email
• Region (dropdown)
• I am signing up as: (dropdown)

Data mappings:

• Module header = page content
• Buttton text = "Haere"
  • Button text can be overridden by adding page tag button_text:XXX where XXX is the custom button label text.

module_signup_form_toi_reo

Activated by tag module_signup_form_toi_reo on a basic subpage - this module adds a full width banner - that links out to the Toi Reo signup form.

Data Mappings:

• Banner header = page headline
• Banner text = page content
• Banner button label = "Haere"
  • This button label can be overridden with page tag button_text:XXX where XXX is the button label
• Banner button URL is pulled from page tag button_url:XXX

NOTE: This module could end up being replaced with a different banner module or basic layout. Originally it had a more unique pop-up modal and nested form but has since been replaced with an external link to a TypeForm.

module_translator_grid

Activated by tag module_translator_grid on a basic subpage - this module will render the translator grid. On this page users can find translators and interpreters who are open to work. Users can view translator profiles and contact them.

The grid has the following filters:

• Translator name (keyword search)
• Region (dropdown)
• Service (dropdown)
• Expertise (dropdown)

The cards in the grid are populated by NationBuilder profiles with tag translator.

module_upcoming_events_current_month

Activated by page tag module_upcoming_events_current_month - this module will render event cards for any remaining calendar events in the language planning calendar (tagged mahere-reo-events) - if any exist. It will also always render a button link to take users to see all events (/language-planning-events).
If the user is on the Maori site - they will see a banner message telling them to switch to the English site to see Lanauge Planning events.