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 below.

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 
• 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

• 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 content section - image"

• Events page = "Header content section - image"

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”
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 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.