Content architecture (and other animals)

Taxonomies

Content on Mosaic

  • generally speaking, 'a piece of content' = a page on the site
  • content in Drupal (i.e. under Mosaic's bonnet) is non-hierarchical - i.e. each page is weighted equally
  • the structure of a site is determined by the page relationships defined by the user

Navigation

Main menu

  • define the navigation structure
  • move navigation links: up/down; indent to define page hierarchy (up to 9 levels deep)
  • add/edit/remove navigation links (nav links can also be created in each page's edit mode)

Navigation display options

  • single level (landing page nav links only)/two-level/three levels (wide drop down)
  • standard/underline style

Sidemenu

  • displays sibling pages and sub-pages - documentation; example
  • can be switched on/off site-wide or on a per-page basis
  • can be positioned on the left or right of the content area (is not within the content area)

Breadcrumbs

  • displays the page hierarchy (defined in the main menu screen) as a set of links at the top of the content area
  • useful for navigating up the nav structure, from deeper-level content, example

Header links

  • up to 3 links (with optional Font Awesome icons) can be placed in the header
  • [worth mentioning] social media links can also be added to the header

Content types

  • 4 base content types on Mosaic: Page; Article; Event; Person. Differentiated by the metadata associated with each - more information about this in the documentation
  • a set of content sub-types are created for each site when provisioned
  • users can create new sub-types/delete default sub-types
  • consuming shared content requires the consuming site to include the content sub-type that the piece of shared content belongs to
  • a piece of content can be moved between different sub-types (e.g. Blog --> News); it cannot be moved betwen different content types (e.g. Person --> Article)
  • Primary uses:
    • sub-types provide a more granular level of content structuring
    • creating listings (Grid/List/Carousel/Slideshow adv) which display certain content types/sub-types

Taxonomies

  • 'taxonomy' = a grouping of taxonomy terms
  • 'taxonomy term' = tag - can be attached to a piece of content (more than one term can be added to each piece of content)
  • taxonomies can be applied to 1, 2, 3, or all 4 content types
  • taxonomies can be 'controlled' or not:
    • Controlled taxonomies: terms can only be added/edited/removed by site admins
    • Uncontrolled taxonomies: terms can be created by any content editor, at the point where terms are applied to the content (in the details tab, in page edit mode)
  • there is 1 default taxonomy present on each site - Authors. This is an uncontrolled taxonomy; terms are added to it when author names are added to the 'author' field in Article content.
  • maximum of 15 custom taxonomies per site
  • Primary uses:
    • If a taxonomy is applied to 1 content type only, it can be a secondary way to filter content within that type (e.g. Person content type > Researcher sub-type > 'Specialism' taxonomy: 'Hop-scotch game theory' term)
    • If a taxonomy is applied to multiple content types, if provides way to filter across different types of content for related themes
    • End users can filter for the content they want: a listing can be set up to filter for content in a particular type/sub-type and taxonomy filters can be set to appear above the listing, example
    • A listing can be 'pre-filtered' by taxonomy terms (only one term can be used from each taxonomy)
    • Taxonomy terms can be displayed using a 'Taxonomy terms display' widget

Content sharing

  • a two-sided process:
    • the originator site chooses to provide content with a particular site, then specifies which piece of content it wants to share;
    • the consuming site can see which content is available for it to use in Manage Content > Shared content, it can then choose to use the content or not
    • the consuming site must include the same content sub-type that the piece of shared content belongs to -- this must be on the consuming site before the shared content is used
    • if the shared content has a taxonomy term and the consuming site wants to use it, the consuming site must include the taxonomy the term belongs to -- this must be on the consuming site before the shared content is used
    • to stop using shared content, manage this in the tab in Manage Content

Shared search

  • Must set up a 'search collection'
  • To set up search collection: send a change request and the site(s) you want to search across to the support team
  • Example: search 'content' and select 'All staff sites' on demo5.web.ox.ac.uk

Aliases

  • page aliases are generated automatically using the page title but custom aliases can be defined
  • pages can have multiple aliases
  • Possible use of a secondary alias:
    • when a site is migrated from an external system into Mosaic and the previous custom domain has been transferred to the platform, old page aliases can be added to new versions of the pages to automatically send pre-existing links and bookmarks to the new version of the page
    • Example: https://www.bbc.co.uk/news

Redirects

  • To be used when a site has been migrated from an external system into Mosaic
  • Useful where a site migration has resulted in content being broken up between multiple new sites
  • Individual redirect:
    • Example usage: capture a particular URL path of an old link/bookmark and send people using this URL to a specific page (on the site or external)
  • Batch redirect:
    • Example usage: capture a particular URL schema and send all old links/bookmarks containing this URL structure to:
      • a specific page (on the new site or external)
      • new versions of the old pages (using the wildcard in the destination path)
    • Example: https://www.admin.ox.ac.uk/personnel/recruit/

Missing pages report

  • see where people are using a URL to access content on the site where: the site URL part is correct (i.e. they land on the site) but the alias they're using doesn't exist
  • Purpose of the report:
    • Identify any opportunities to add secondary aliases or redirects to send old links/bookmarks to new content

Search engine visibility/indexing

  • restrict viewing to content editors (i.e. people with user roles on the site) -- can be used to hide a site during development but not strictly necessary
  • hide site from search engines checkbox -- ticked by default. When flagged, a robots.txt is aplied to the site to prevent search engines from indexing (it is up to search engines to obey this instruction). Unchecking this option is the final platform setting that needs to be edited before launching a site.

Other info

Site details

  • Main site information

Domains

  • Up to 2 custom domains can be added to a Mosaic site

Templates

  • Can only be created/edited by site admininistrators
  • Templates are not dynamic: changes to the template do not result in corresponding changes to the content created from the templates
  • Behind the scenes, a template is a normal piece of content which is always in Draft state; when creating content from a template, the process uses the same functionality as 'Copy as' on any page

Workflow

  • three publishing states exist for pages: Draft / Needs Review / Published
  • up to 1 Draft / Needs review version and 1 Published version can exist at the same time