Moderation

Moderation just means whether the page or widget is live/in draft/archived.

The draft moderation does not function at all, once the page goes live. Don't use it.

There's only once scenario where you use draft, and it's if the page or widget has never been published before. As soon as you hit publish, or archive, keep it either as published or archived.

Cheat sheet:

• Live content > updated live content:

If page is live/published already = never never use save as draft - just save & publish

• Live content > new changes not yet approved:

If page/widget is live already, but new changes can't be live yet = use the archive option for the specific widget. i.e. Save & archive or Save & keep archived

• Brand new content

If page/widget is brand new (never been live before) = only then can you save as draft. As soon as that goes live, you would either keep it live, or revert to archive. Draft is no longer an option.

Scenario note: you've accidentally published something that can't go live yet: 

Don't use draft mode. It will not unpublish the page. You must use archive, and keep archived, until ready to go live.

Hello hello

Naming conventions 

If I can offer one main piece of advice to help in managing our enormous CMS, it would be to follow the current naming conventions that are in place. Frequently this role is required to get things up quickly, or source previous content to make new content, and by following the naming convention things remain organised and you can use the search function to find anything pretty easily. There's also many campaigns that have been of the same subject, but throughout different time periods, so also to avoid any confusion there these names keep it correct and reliable.

The specific naming convention details are listed in the Naming Conventions section (it has its own block) below on this page.

Editing images in a tile that sits in a widget (not relevant for images in body text)

Then just secondly, but really importantly, when you're editing images that are existing in a tile, make sure you remove the whole media file, rather than just the image itself. It is quite often that images are used in multiple places, so if you replaced just the image, but not swap the whole file, you would be editing images across the entire website accidentally. You can find more notes about that in the uploading images section :)

• Content > Add content > Page

• Pages are not the same as Articles. If you want an article (includes the itinerary style), Content > Add content > Article

Notes: 

• Title* = even if hidden from page, it will be displayed in Breadcrumb link on page. To hide the page title, you will need to add the widget type: Custom HTML with the title "CSS hide page title". This will be under "Widget Bottom".
• Widgets should all be under "Widget Bottom" for full width (pink section)
• Slug = the very last part of url after the final / - E.g. https://www.sydney.com/travel-information/public-holidays/christmas - the slug of this page will only be "christmas" - the rest of the page is mapped out - see menu settings point below
• Analytics Page Type* = how we report on pages
• Geo Location = for Favourites Page map
• Menu Settings = for page mapping > parent page is where you are attaching the page to in the url. E.g. https://www.sydney.com/travel-information/public-holidays/christmas - the parent page of "christmas" is "public holidays". The parent page of "public holidays" is "travel information" etc.
• Meta tags = SEO
• Pages are not the same as "articles". If you are creating an article (including itinerary style articles), you will go Content > Add content > Article. You can copy the existing formatting of an article as a reference.

Wherever there is a link in the copy that's to an ATDW listing, use the little Baby Yoda icon in the editor bar to do so: 

You can type in the business name into the bar, however sometimes multiple listings have the exact same name (this will happen say for example if one listing is a tour vs one is an attraction, or there is an old archived listing with the same name that still shows up):
 

If this happens, you can find the correct ATDW ID number from the ATDW platform in the listing's url (different from profile number #):
 

To build any type of product list, you can have a look at all the different display types from the link below, and then copy the same settings from the example:

https://www.sydney.com/widget-index/product-list

• Content > Media > Add Media > Image

If adding the image into copy

• Go to the spot you need to add in the image and create the new line break
• Select the camera icon: 

• Type the specific media name, select the media when it pops up
• You will then need to select "article" as the "view mode*" so the image displays in the correct specs (always article mode for any content block with text):
  
  
  
  
  
   
• Never select the icon "image" directly in the copy - it doesn't have any of the necessary content fields so we would never be able to track the image in the system:
  
  
  
   

If adding an image to a tile

• You can add the image directly in here as all the fields will populate - "add new media item", or if one exists already just select "add existing media item" and type in the specific media name:
  
  

Notes:

• There are thousands of images uploaded in the system - to save time do a quick search of the image before uploading (Content > Media > Media Name)
• Every image media name must be different from the others, otherwise you will cause a bug in the system and the wrong image can get pulled through.
  > It doesn't matter if it's as small as saying "blue sky" or "bright sun" or just literally any differentiating point
  E.g. Man crossing bridge at Treetop Adventure Park - Tuggerah - Central Coast
• Please refer to "Naming Conventions" on this publisher guide page for information on how to name images, however in summary:
   

If possible - whatever content piece you're working on, whether it's copy | a tiles container | an image | any widget | a tile;

Media Name = Back-end of CMS - producer use only

Image Caption/Article Image Caption = displayed to website user

Whenever you're thinking about headers + widgets/media types, think of it as first needing a picture frame, and then you put the picture/art inside the frame.

The widget is the frame, the image itself is the picture/art.

In the very extreme simplest form explanation of backend setup:

#1 Standard Headers

• Video Headers (homepage/deals page/campaign pages)
• Standard default headers (child pages - standard content; town pages/theme pages/non navigational)
   

#2 Specialty Headers

• Articles & Road trips
• Media Header (high level navigational pages e.g. region level/events landing page)
  Image example
  Video example
  Gallery example
• Text only (product list pages/difficult to find images for pages)

This is a further short breakdown of header type:

If building a new header image on a page that exists already

• Go into "New draft" then the header container > "Add new media item" > make sure it is the correct media type e.g. "Header article and road trip - image" vs "Header image with text block"
• Events page = "Events Header"

How to name images as an ATDW

1. Source the image.
2. Import the image from the ATDW listing, first checking it does not exist already in the media library.
3. Choose the ATDW and click import.
   
    
4. Choose the image you want to import.
   Choose image > click import
   
5. Name the image correctly.

Media name:

ATDW - Product name - Location - Description of image

Eg. ATDW - Iron Gate Estate - Pokolbin - Two men sitting with dog on bench

Alternative text:

Description of the image, Name of product, Location - Credit: Name of image credit

Eg. Two men sitting with dog on bench, Iron Gate Estate, Pokolbin - Credit: Hunter Valley Visitor Centre

Title:

Product name, Location - Credit: Name of image credit

Eg: Iron Gate Estate, Pokolbin - Credit: Hunter Valley Visitor Centre

Image id:

ATDW - Name of product

Eg. ATDW - Iron Gate Estate

Article Image caption:

Product name, Location - Credit: Name of image credit

Eg: Iron Gate Estate, Pokolbin - Credit: Hunter Valley Visitor Centre

• Note the product name has a baby yoda link
• Choose this by highlighting the product and clicking the baby yoda, searching for the product and saving it
  

Credit: Put in the credit of the image

Copyright: Put in the image copyright if needed.

*Note: You will need to cross reference with the ATDW to ensure it is correct.

Final image in the media library for reference:

The reason we do it this way is because if you don't take the original file from the code using the below instructions, the image will save at a much much smaller size and be poor quality on the website.

1. In the ATDW listing, go into “Photo’s”, which sits in the vertical orange bar on the left hand side
2. Click on one of the images you want so it appears in a larger size above the rest of the gallery
3. With your mouse over the image, right click, and click on “inspect” (use Google Chrome browser)
4. A bar will appear on the right hand side of the screen. At the top of this bar, you’ll see “sources”. It should be the third option along. If you click that, there’s a drop down of heaps of options
5. Click on the one that has an icon of a cloud and then says: “assets.atdw-online.com.au” – this is just you accessing the code of the database, and then you’ve now navigated to where the files are saved.
6. Click on the “images” folder – all the images will appear in a long list. If you click through each one, you’ll see what image it is.
7. Find the one you’re after and right click and open in a new window.
8. In the url at the top, just backspace out the characters that appear after the “.jpeg” or “.jpg” – the characters are just making your image appear smaller than it really is. By backspacing that out you can see the quality of the image at its full size and then save it to your own files
9. You don’t have to start from scratch per image, you can just go back to that list of images in the sources bar
10. Naming the image - when you upload it into the CMS, the Name* field should always start with "ATDW - name of the listing" and the credit should always have both the photographer and the owning organisation.

Note: if you get sick of having to scroll through that super long list of images to choose from, refresh the webpage, and it’ll return the image results list from just the profile of the page you’re on

Here is a visual chart of the instruction steps 1-7:

How to save and naming conventions for a DNSW image

1. Search for the image in the media library either by the name or ID number. If it is not in the library then follow the below to add it into the library.
2. 
3. Source the image in the content library if it doesn't already exist in the media library on VisitNSW or Sydney https://content.destinationnsw.com.au/
4. Download an image under 10MB
5. Add an image into the media library in Drupal.

Media name:

Product name - Location - Description of image - DNSW

Eg. Mitchies Jetty and Cafe - Merimbula - Couple enjoying a morning coffee - DNSW

Alternative text:

Description of the image, Name of product, Location - Credit: Name of image credit

Eg. Couple enjoying a morning coffee, Mitchies Jetty and Cafe, Merimbula

Note: There is no credit as it is an image owned by DNSW

Title:

Product name, Location - Credit: Name of image credit

Eg: Mitchies Jetty and Cafe, Merimbula

Image id:

Number in the content library

Eg. 1005585

Article Image caption:

Product name, Location - Credit: Name of image credit

Eg: Mitchies Jetty and Cafe, Merimbula

• Note the product name has a baby yoda link
• Choose this by highlighting the product and clicking the baby yoda, searching for the product and saving it

Credit: Put in the credit of the image 
Eg: Destination NSW

Copyright: Put in the image copyright if needed.

Final image in the media library for reference:

How to build a Campaign Anchor Widget

• Content > Add content > Widget: Campaign Anchor

Title* = backend name. Always follow: Campaign Anchor - purpose of widget or title or topic. E.g. Campaign Anchor - EV Road Trips

Generally if it's for the homepage I would include that as the first thing in the title (e.g. Homepage - Campaign Anchor - EV Road Trips), because our two homepages are the face of the website and usually require really fast searching for content or previous content, so that always helps navigate and keeping organised. Using the "homepage" inclusion doesn't always make sense though if the widget is seeded throughout the whole website, so use judgement on whether it's relevant for the backend name. 

Fields: "Heading" will be for the entire widget, not just on the image itself. 

Then "Add new media item" - this is the part where you're building the actual campaign anchor widget

Name* = this is the same as the Title, but with the addition of something specific about the image. E.g. Campaign Anchor - EV Road Trips - couple charging EV car

Then add in the landscape and mobile image. Crop them to the correct specs that are written for you under each space to upload

Fill out the fields as briefed.

Note: in the CTA section, if it's an external URL (so not in either Sydney or Visitnsw) then click for the "Attributes" dropdown, and select from the "Target" options "New Window"

All external URLs should open in a new tab. This is a sitewide business rule.

Visitnsw.com (different to Sydney)

If you need to add an emergency warning, open the widget: "Christmas Holiday Period Emergency Widget - traffic congestion" and copy the settings and text style into building a new widget. This is where you put the content of the warning/update. 

Then when this is built, on its own it'll look weird, so when you add it onto the page, you need to also add on the page existing node "Fire Widget CSS" which is the formatting. You dont need to build a new Fire Widget CSS, just use the existing one.  

Instructions: 

Build a "Widget: Text with Image" widget, and make the display setting "Emergency Module LEFT Image" in this widget - you then add that to the page, but you also must add on "Fire Widget CSS" as an existing widget/node to the page too. 

If you do not do this, it wont be formatted correctly.

Note: when you build the widget on it's own, without the Fire Widget CSS added into the same browser, it'll look incorrect. This is okay, just follow the instructions above when adding it onto the actual page.

With the correct Fire Widget CSS formatting widget: 

Without the correct formatting widget this is what it looks like: 

Sydney.com

Sydney.com operates almost the same as Visitnsw.com - the difference is the title of the extra formatting widget you'll add in. 

You still need to build a new widget "Widget: Text with Image", and make the image position setting "Emergency Module LEFT Image" (even though there's no image, this is crucial) 

Then you add the existing widget "Emergency Warning Widget CSS" as an existing node/widget to the page as well for formatting.

If you get stuck, ask Millie/Marcelo

COVID ALERT

This is titled "Covid Alert" but this is for the Yellow Emergency warning strip that goes at the bottom of all headers across the whole website in times of a crisis. If you need to edit this, you can ask Millie, or Marcelo, or if you have a access you can edit this page: 

https://www.sydney.com/admin/content/sitewide_alert/1

If you ever have a url, that is producing a "-0" on the end of it, you have actually created a duplicated page.

To find the original page, just backspace off the -0, and hit enter, and you'll be able to see what page currently exists holding that url.

You'll then need to migrate over the new content back onto the original page with the correct url, and then you need to:

• remove all content off the duplicated page
• remove the mapping from this duplicated page > un-tick the "menu" item
• remove the duplicated url slug and make that field something along the lines of "archived-1" or just any random number

If you do not do this, you'll create confusion and a mess in the cms. These steps are really important.

1. Create Widget: Article List

2. Title* = always the name of the page you're creating the widget for, followed by '- Travel Inspiration' (or if it's titled something else, call it that)

3. "Heading" = whatever is written in the brief - e.g. "Travel Inspiration"

4. Link = leave this blank

5. In the "Article List" drop-down, choose "Articles List (Short)"

6. in "Article View Mode" drop-down, select "Promoted Articles"

7. Type the names of the articles you want pinned in the "Promoted Articles" field with a comma in between each one.

Note: The name of the article will be the page title of the article - so not the displayed heading, and not the url. This one:

8. If you haven't been given any names of the articles, and it's for a region/area/town, just enter the relevant info into the destination fields

9. In the "count" field, please make the number 3.

• This is when you need to create a document that is not a downloaded attachment, but rather an online document with a URL, which is accessible by anyone/the public (not just DNSW staff). 

  By using this method, as a word document, you are able to continue editing content, without needing to produce a new URL for every update/change. 

  Only the owner of the document will have editing access.

An example I have created, are these instructions as their own document: https://docs.google.com/document/d/e/2PACX-1vS1-ALvDNEE-EANLWDXruW-Is7ro5ThVHJUMwCKIbpJLSus9J0kGRp3ZBhIvduY-w/pub

I can also make the URL look prettier, without the ID showing and just hyperlink text. For example, click here. 

Steps:

1. Go to google drive - you can use your DNSW email. If you go to www.google.com, you'll see this view.

2. Have the document saved to your desktop, then drag and drop into your Google Drive account. As mentioned, these instructions are for a word document only:   

3. From your google drive list view, and click on the “Share” icon: 

4. Set the access to: “Anyone with the link”. This means it’s public (for viewing, not editing).

5. Open the document, and make any changes that you need to. You can do this as many times as you would like to. It does not matter how many changes you make, or when you make them, including after this document has been published. 

We are now ready to publish to web (nothing will happen, it just means you can provide the URL to Millie, who can then publish it onto the Sydney.com page. So until the URL is on the Sydney.com page, the document still isn’t out in the world).

6. Open the document from within Google Drive, and click File > Share > Publish to web.

7. Copy the URL in the Link field:

Send this to Millie.

You can test this URL too if you would like, by sending it to anyone directly to view it. 

The public will not have access to edit the document, only the owner of the document has access for editing.

A reminder: you can still open the document, and make any changes that you need to. You can do this as many times as you would like to. It does not matter how many changes you make, or when you make them, including after this document has been published. 

The updated content will appear for the users viewing the information.

If you want to add in buttons into the copy, so that it looks like this: 

Steps to do this: 

Steps from above:

1. Type in your text (so whatever you would like your button to say)
2. Add in the hyperlink (remember external URLs should open in new window, you can choose this in advanced settings in this step)
3. Highlight the linked copy, and select the "styles" dropdown
4. Choose "Blue Button" - this will automatically display as green on Visitnsw & blue on Sydney. Always choose the blue button option here. 
   If you choose the green one, it will bug, and you'll have to delete the whole thing & start again, or you'd need to edit the source code.

At the top of this guide, there are all of the international homepage URLs listed; section one under "International Websites". If you need quick access to an international homepage, you can find them all listed there.

Translation Logic & Default Behaviour

You can now have a customised translated version of any page that exists in Sydney.com or VisitNSW and have it live in any of our international sites.

1. The default behaviour is that if you update the page in Sydney.com or VisitNSW, the translated versions will sync this content.
2. Currently, the international websites mostly only have a unique homepage, and a unique deals page. The rest of the website is mirrored/duplicated content that is synced with every update we do. This new functionality allows tailored content per market.
3. If you want it to be customised, and therefore not override the unique market content if the original page has content edited on it, you can block the default sync that occurs (already set to this on the homepages). The instructions for new customised pages are below, under the heading in this section "Customised Translations per International Market".

Searching for current translated/international versions of pages in our CMS

As mentioned in the very first sentence of this section, all of the international homepage URLs are listed at the top of this guide under "International Websites" in section 1. This is just a short list of the homepages, deals pages + country prefixes.

If you wanted to have a look to see what pages exist as a customised translation page, you can go into the content section of the Drupal CMS, and select under the language option which country you're looking for, and select under the "content type" a "page", to quickly filter out the other languages. 

In the example below, I have created a unique page for Walks & Hikes for India, so you can see that it exists now in the India section of the site:

Note: for every country's homepage, the name of the homepage is actually just the country it belongs to. For example, the India homepage is titled "India". This obviously does not display to the consumers and is for a quick reference for us internally.

Creating a translation version of an existing page in Sydney.com or Visitnsw.com

Scenario: you have a page that lives in either Sydney.com or Visitnsw.com. You need to create a translated version of this page to live in the India International version of the website.

1. Head to the page you want to create a translated version of; e.g. Hikes & Walks. Click on the "Translate" tab, which is located next to the "Edit" tab
2. Choose which language/site you wish to create the version of, and click "add". The website will clone the page, and bring the screen to the new view of this page. You are now sitting in the backend of this new version.
3. Scroll to the bottom of the page & select "Publish". If there's content you need to modify on the translated version, you can do that on this new duplication you have now created.

Customised Translations per International Market

As stated in the Logic section of this dropdown, the translated pages are synced with every update on their matching source page, unless someone checks the box telling the cms not to do this.

Note: "entity references" as a term just means the widget/block of content (in this circumstance, it's the content on the original page). The dev team will use this term so I have included it below so we're matching.

To block the default sync, there is a new button, that says "Do not sync entity references". It's a checkbox, and it's located on the page level of the translated version, not on a widget level. It lives towards the bottom of the page, in a dropdown under the meta data  section. 

So just to reiterate, when you want to block the translated version from syncing to the original; you will do this on the translated page, in the international sites' language prefix, NOT in the Sydney/Visit original version.

E.g. /in/things-to-do/nature-and-parks/walks - note the prefix of IN in the url, so it lives in the India version of the website.

Taking down a customised translations page

Scenario: You no longer want to have a customised version of a page in a translated site and want the content to sync with the original version in Sydney.com or Visitnsw

1. Go to the translated version of the page (if you dont have the url, go to the CMS content section and choose the filter option by the language dropdown and add "page" as the content type)
2. Go down to the "Translations" section at the bottom of the page - sitting underneath the meta data
3. Uncheck the tickbox "Do not sync entity references" - note: this just means you're choosing for it to sync the content in the widgets on the page again
4. Publish the page
5. Go to the original page in Sydney.com/Visitnsw.com & republish this page - you'll do this to cause a resync of the content, otherwise the system won't have reason to refresh the content on the translated version.

Note: as this is a new feature, I am currently unsure if the best practice is to also then delete the translated version as there's no longer a need for it if you're removing the customised feature. I'm unsure of any other implications that might cause, and we can ask the dev team about it/make the decision in due time.

Location to create one in the menu of the CMS: Configuration > Search & Metadata > URL redirects > Add redirect

1. Screenshot the page that is to be redirected.
   Before you actually create the redirect, take a screenshot of the page that will be archived. I recommend using the Google Plugin called "Awesome Screenshot", which our Senior Executive team also recommended, and it can take a full length page screenshot without you even needing to scroll down. Add this onto the ticket once the redirect is complete so there's a record of the old page

Add redirect

1. Be sure you are in the right cms > either Sydney or VisitNSW.
2. Go to configuration > Search and Meta data > URL Directs > Add redirect.

3. Add in the "Node" of the page you want to redirect the path to. 

• The cms won't recognise it if you just paste the URL rather than the node number and the page exists. 

• The node is the number in the url of the specific page after the word "node".

   

  4. To*: add in the node number eg: node/13661

If you are creating a vanity url, entering in the URL is okay, because the page doesn't exist.

NOTE:  Be careful when filling in the fields. Note each field for the 'path' and 'to' is different - one has a '/' and one doesn't. Make sure you don't duplicate the '/' in the first field, and add one in for the second.
 

• Path* = node/'page id number' found in url. E.g. the Events page: https://www.sydney.com/events, has the node id of 8126 so e.g. https://www.sydney.com/node/8126
  You would then enter into the Path field: node/13256 
   
• To* = website url /node/ new page's id. So e.g. https://www.sydney.com/node/1234
  You would enter in /node/1234

Note: it is essential you copy the exact node number. If you use the wrong one, you will redirect something else, and you won't be notified of the incorrect number.

If you need to delete a redirect, click to "add" a new one, and enter in the existing node number. You'll then get a dropdown of options once you click out of the field, to "edit the existing redirect". If you click that link, you can then choose to delete it.

Removing the original page:

Once the redirect is saved, go to the original page you're removing, and click to Save & Archive after you have hidden the page from search engines

Making the archived page hidden from search:

Once the redirect has been saved first, you then go onto the page that needs to be archived, and scroll down to the "meta" section. Untick the first two options, and select the rest of the entire list. 

Again, don't forget to save & archive - you don't want to keep the page you're taking down as live/published.

Location to create one in the menu of the CMS: Configuration > Search & Metadata > URL redirects > Add redirect

• + Add redirect
• Be sure you are in the right cms > either Sydney or VisitNSW. 
• This is the only time you'll ever put in letters/a slug into the redirect field. So in the "from" field, you make up the vanity URL that you want. E.g /feelnew
• In the "to" field, you then use the node number for where the page actually lives. So think of it as linking the content to the fake url.
• The node is the number in the url of the specific page after the word "node". To locate this, go to the page of content, click to new draft/edit, and look at the url.
  E.g. the Events page: https://www.sydney.com/events, has the node id of 8126 so e.g. https://www.sydney.com/node/8126
  You would then enter into the Path field: node/13256 
• Be careful when filling in the fields. Note each field for the 'path' and 'to' is different - one has a '/' and one doesn't. Make sure you don't duplicate the '/' in the first field, and add one in for the second.
   
• Click to save it - leave the auto populated fields underneath. You can add multiple vanity urls to the same piece of content.

• Articles are automatically mapped. You won't need to do this 

New page creation: 

• Menu settings > tick "provide a menu link" 
• In "parent link" > "+" > select the parent page for where the new page should be mapped to

URLs:

• Page meta* > "slug" field - no spaces, only hyphens, be as specific as possible to the page

For example, the Spas & Wellbeing page. The "parent page" is "Fashion and Shopping", the slug is simply "spas-and-wellbeing", creating this url: 

https://www.sydney.com/things-to-do/fashion-and-shopping/spas-and-wellbeing

1. In the red bar at the top, click on "ATDW Online" 

2. Select "Product Sync" from the new menu that appears directly below it

3. Paste in the product ID number into the field - note, it's the URL number in the ATDW profile (the same one you use for the Hodor copy linking):