• Landing page: https://www.sydney.com/articles

Three different templates:

• Listicle: 9 secret Sydney spots
• Itinerary: A 72-hour nature staycation on the Northern Beaches
• Standard: What to do in Sydney in winter

Located in the CMS to build: Content > Add content > Article

Briefs

Each brief provided for an article is exceptionally detailed, so follow the brief provided to you and enter in the information to the corresponding and labelled data fields.

You will be given the categories, locations (need to match the location hierarchy, meaning you can't list a town that doesn't exist in our CMS. Type in the name and if it exists it will appear in the dropdown), content, image options, titles, meta data, analytics information etc.

The only info you most likely won't be given is the reading time, which you can copy and paste the body copy from the brief into this website and then look at the 'Reading Time' that's listed on the right hand side panel: https://wordcounter.net/

You also will by default always just make the author "Destination NSW", which comes up if you click to 'add existing author'. The date & time of publishing should be the date and time that it is when you're building the article. You can change this if needed in the future.

Navigation for the user

The link that lives within the header, so field titled "Category or overlay image link", should always be *Link Text: Article | URL: https://www.sydney.com/articles or https://www.visitnsw.com/articles:

It appears like this on the front end, so is consistent as a navigational tool for the user on every single article: 

This is how it appears in the backend: 

Article Titles

You should be provided a title that is for the backend and for the small tile preview to be displayed, and then also a title that lives in the header itself, which is longer and more descriptive.

If you are not provided these, follow up with the person that briefed you, and ask for it.

If there's any confusion for building any of the above templates in the articles section, you can open up any of these existing articles, and follow along the same fields and settings.

Sydney.com & Visitnsw.com pulls through the following ATDW categories as Product List/Product Profile pages: 

• Accommodation
• Attraction
• Event
• Food & Drink
• Hire
• Journey
• Tour

These can all be identified by both the template and url. The url will always contain the category type. The page template has an image gallery and information text field, with contact details on the side:

https://www.sydney.com/destinations/sydney/sydney-north/mosman/attractions/taronga-zoo-sydney

• This is a page list of ATDW products.
• It will be for one specific category, e.g. Accommodation, and will be specific to a destination, e.g. Mudgee.
• They were created automatically by the CMS, and then over time some have been rebuilt to include some introduction copy and a header image at the top as the generated version didnt include those elements.
• They're mostly accessed from the default links on a page, however can be linked in a tile directly anywhere if requested and also rank incredibly well in search from google: 

Product list URLs:

• The url should ONLY ever end in the specific category, e.g. /accommodation or /activities or /events - if you add in more than this you will break it.
   
• The title of the page does not need to be the url. A url is the abbreviated form of any title, and doesnt need repeated info (e.g. the destination).
• If you are briefed for the url to be different than just the category, explain why this can't happen to whoever has briefed you in, remembering the title displayed can be whatever they like.

When to edit an existing page rather than building one:

• If the page already has been rebuilt at some stage and you just need to edit it and optimise it, then just click 'New draft' and don't create a duplicate page:

When to build a new page vs editing one: 

• If the page has not yet been rebuilt by us, it will be missing the editors tabs at the top of the page, and also won't have a header image, so it will look like this: 

• So if the url takes you to a page that looks like this, you will need to build a page.

Building a product list page

• Content > Add content > Page
• Title* = The most basic relevant information, e.g. Mudgee Accommodation. Do not put the consumer facing title here.
• Widget Bottom: Widget: Product Lists "Add new node":

• Title* = Page name, e.g. Mudgee Accommodation - Product List
• Select the correct criteria - e.g. the location you're building it for. Select to lock region

• Display options tab
  > Product List View Mode: "Product List Domestic". Note: It used to be paged, however on paged you cannot display the filter, so have changed to domestic.
  > Tick yes for: "Show product search form" + "Map Display Switch" + any other relevant filters you need to display
  > Enabled categories: this should be the category you're building the page for, and drag it to the top of the product list: 

• Create node

Page Meta - Header Image Container

• Build a header container like you would for any other page: Header - Mudgee Accommodation
• If one exists already, remove it and build a new one
• This is where you will put in the display name for the page, so it will be longer and most likely more descriptive, e.g. "Accommodation in Mudgee & surrounds"

Menu Settings

• Tick "Provide a menu link"

• Click on the '+' button that appears in Parent link:

• Type in the destination for where this page is being mapped to in the hierarchy and click which one you want it to sit under

• Enter the meta data
• Save and publish
• Don't forget to publish the header container separately

Used for high level pages, the page is mostly tiles containers, with minimal content

Purpose is to help users find their specific content quicker

• Mega menu pages
• Things to do pillar theme e.g Food & Drink
• Region level pages
• Area level pages

E.g. https://www.sydney.com/things-to-do/nature-and-parks

Editorial content pages are pages that aren't articles, but still have the purpose of being informative text, and generally have minimal tiles containers but rather product lists on them: 

• Destination town pages
• Theme pages requiring content

E.g. Mosman: https://www.sydney.com/destinations/sydney/sydney-north/mosman

E.g. Outdoor dining in Sydney: https://www.sydney.com/things-to-do/food-and-drink/food/sydney-restaurants/outdoor-dining

• Landing page: https://www.visitnsw.com/things-to-do/drives-and-road-trips

Road trips are their own section of the website, and in terms of page creation, they are shell pages, which we pull through code from the ATDW platform. The road trip content itself is accessed via the Alpaca platform.

Road trip example: Cool Coast to Intrepid Inland

All instructions on how to build this page and the widgets required can be found here:

"Building a Road Trip from Alpaca into Drupal"

• Really only ever for pages like this Digital Publisher Guide. It's in the backend as a page type classification so reporting isn't affected by staff having pages like this.

• Where to find the best cocktails in Sydney's CBD

• 8 ways to see Sydney like you've never seen it before

• A 72-hour nature staycation on the Northern Beaches

Teaser tiles are what are pulled through onto editorial pages:

• Teaser image = vertical/portrait image
• Teaser image horizontal = of course horizontal/landscape (what is shown above in the screenshot)