Some websites that were linked from the previous WOUDC site have been moved and those links now point to dead ends or unintended redirects. These links should be replaced in the new UI so that they point to an existing site with the same or similar information as they would have had before (judging by the link text and previous URL).

List of links needing replacement (link text followed by previous, disconnected URL):

• First three links under Data Summaries and Reports on the products home page:
  • Antarctic and Arctic ozone bulletins - WMO: https://www.wmo.int/pages/prog/arep/gaw/ozone/index.html
  • GAW Research and Monitoring Reports - WMO: https://www.wmo.int/pages/prog/arep/gaw/gaw-reports.html
  • Global Ozone Research and Monitoring Project Reports - WMO : https://www.wmo.int/pages/prog/arep/gaw/ozone_reports.html
• Second item on contributor registration page:
  • more about GAW: https://www.wmo.int/pages/prog/arep/gaw/gaw_home_en.html
• First link on data quality page:
  • GAW quality assurance system: https://www.wmo.int/pages/prog/arep/gaw/qassurance.html
• Second link on the standards page:
  • WMO Information System: https://www.wmo.int/pages/prog/www/WIS/
• Link under Erythemal on glossary page points to somewhere that seems to have little to do with the link text:
  • carcinogenesis effectiveness: https://www.wmo.int/pages/prog/dra/etrp/documents/926E.pdf

As mentioned in #6 (comment)

Lots of HTML elements are in the format of void elements. Best practice is to reserve those for official HTML void elements.

Lines like these:

<nuxt-link :to="localePath('about-faq')" v-text="$t('contact.blurb.faq')" />

to be replaced with:

<nuxt-link :to="localePath('about-faq')">{{ $t('contact.blurb.faq')" }}</nuxt-link>

As mentioned in #6 (comment):

• Be sure to replace the /n/n so they're split up as individual paragraphs <p> (and thus removing the "newlines" class).
• Don't be afraid to use more descriptive keys; template sounds too generic. Something like how_to_use would be better.

The table of contents on the data access page contains a link to each section. Clicking on these links is meant to scroll the user to where the section they clicked on is at the top of the page. Because the header at the top of the page has fixed position, it overlaps content at the top of the page when the page is scrolled and hides the title of the section the user clicked on, plus some content.

Example: On the data access page, click "Definitions Service" on the table of contents and see that the section title and first line of its content are hidden.

Goal: Make the page content fall completely between the header and footer at all times so that no content on the page is hidden.