The Services menu and the /services/ pages are both built from content pages of the Services content type. Where a page sits in the hierarchy decides where it shows in the menu, and its Body Template decides how the page itself is laid out.
This page is the overview: how the menu is put together, which template to use, and what each field and image does. For step-by-step instructions, use the workflows:
| Level | What it is | Desktop menu | Mobile menu |
|---|---|---|---|
| 1 | A top-level service page, such as Window Tinting | Listed down the left. With children it opens a tab and gets an Explore [name] link; without children it is a plain link | Shown |
| 2 | A child of a level 1 page | A tile in that tab: the page’s Alt image 1, cropped to a wide 3:1 strip, with its name under it | Shown |
| 3 | A child of a level 2 page | Not shown | Shown. None is on the menu today: the only level 3 page, Trailcore Service Body by Utemaster, has show-on-menu off |
serve_menu_content content zone.Set the template in the page’s Body Template field.
| Template | Use for | Child cards | Product price list (Label 1) | Typeform (Label 3) |
|---|---|---|---|---|
service-parent | A level 1 service with child service pages | Yes | No | No |
services | A single service page with no children | No | Yes | Yes |
serviceNew | The same as services, plus a fixed “Why Choose Altapac?” section | No | Yes | Yes |
services is also used outside the Services menu. The store location pages (/locations/kotara, /locations/burwood/bullbars and so on) are Learn pages with services typed in as their template.serviceNew is live on one page only, Roof Rack Installation. Its company section is written into the theme and can’t be edited in cPanel. See The serviceNew company section.services layout. Setting services explicitly gives the same layout without relying on the store’s default.A parent in the hierarchy doesn’t have to use service-parent. Use it only when the children are service pages that should be shown as cards. If you are unsure, ask the WebMaster.
All three templates open with the same banner and description block.
Main image
Page heading
SEOPageHeading) if one is set, otherwise the page Name. No service page sets an SEO page heading today (2026-10-20 pull), so every banner shows the Name.
Short Description (ShortDescription1)
SEOMetaDescription), not from the Short Description. If that field is empty, the store falls back to “Name - Name”.
Description 1
#_Custom-page-content, so styles scoped to that wrapper don’t reach it.
Alt image 1 (alt_1)
Description 2 (optional)
_Custom-page-content. If Description 2 is empty, the section isn’t printed.#_Custom-page-content. See Custom CSS and HTML in page content.service-parent)Page order: banner, child cards, Description 1 with Alt image 1, then Description 2.
The parent builds one card per child page. Each card shows the child’s Alt image 1, Name and Short Description, and links to the child. Cards are three across on desktop, so three or more children work best. A child gets a card only if all of these are true:
Cards use the same order as the menu: Sort Order highest first, then name A to Z. If no child qualifies, the card section isn’t shown. Signage & Graphics is like this today because all four of its children are inactive. If a page has no children at all, use services instead.
Leave Label 1 and Label 3 empty on parents. There is no price list or Typeform slot. A form on a parent page has to be pasted into Description 2 as embed code, as Window Tinting does today.
services and serviceNew)Page order: banner, Description 1 with Alt image 1, the product price list (if switched on), then Description 2 with the Typeform at its top (if set). serviceNew then adds its company section and Description 3.
The price list is a row of cards, one per service product, each with a Call Us button that rings the main store number. It doesn’t use the products assigned to the page in the usual Maropost way.
/export//service-product.json. The page shows only the products whose category value in that feed includes the page’s Content ID. Assigning a product to the page does nothing unless the feed carries the ID.To set one up, follow Add a product price list.
Label 3 can hold a Typeform embed ID: the data-tf-live value from the form’s embed code, not the short ID in a share link. The form is placed at the top of the Description 2 section, so it only appears when Description 2 has content.
No live page uses Label 3 today. Every Typeform on a service page is embed code pasted into Description 2 (2026-10-20 pull). Before you move a page over to Label 3, read Add a Typeform. If you leave the pasted copy in place, the page shows two forms.
From Altapac-ReDev, branch development:
src/templates/cms/service-parent.template.html: hero, then content_menu content_type:'services' sortby:'sortorder, name' show_empty:'1' category:'[@content_id@]' start_category:'[@content_id@]' with *level_1 only; card image thumb:'alt_1' at width="450px" height="300px", CSS #service-children .card-img-top { height: 200px; object-fit: cover }. Heading guarded via [@children_heading@] (commit 406e84c, AUD-87); live main prints it unguarded.src/templates/cms/services.template.html: product list inside [%if [@content_label1@] %] (lines 137-227), fetches /export//service-product.json, filters on String(product.category).split(',') containing [@content_id@], unhides only when a card renders (commit c4bfdae, AUD-36). Typeform <div data-tf-live="[@content_label3@]"> nested in [%if [@content_description2@] %] (230-239).src/templates/cms/serviceNew.template.html: same list (203-292) and Typeform (295-306); “Why Choose Altapac?” inside [%if [@content_description3@] || [@content_description2@] %] (308-404, commit b987e8f, AUD-86); Description 3 at 407-411 reuses id="_Custom-page-content".src/templates/headers/includes/components/desk-Menu.template.html: Services mega-menu (from line 115), level 2 img.lvl2-image from thumb:'alt_1'; fallback zone serve_menu_content. CSS in src/css/custom.css (img.lvl2-image aspect-ratio 3/1, grayscale 0.6).[%url_info name:'page_heading' default:'[@content_name@]'/%]; meta description from url_info name:'meta_description' in headers/includes/head.template.html.src/css/fontawesomev6/, loaded from footers/includes/scripts.template.html.Template use per page is from Altapac-Content pages/**/meta.json (pulled 2026-10-20). Live checks and feed details are recorded in the service pages workflow.