wiki:TechnicalDescription

Version 4 (modified by dagmon, 11 years ago) (diff)

—

Technical description

  1. Technical description
  2. 1. Technical requirements
    1. 1.1. Google tag manager
    2. 1.2. All site pages on https
    3. 1.3. Hidden form field to be injected by Javascript
    4. 1.4. Embedding of youtube
    5. 1.5. Use the open graph protocol
    6. 1.6. Don’t forget the favicon: ​http://css-tricks.com/favicon-quiz/
    7. 1.7. RSS feed for new courses
    8. 1.8. Direct URL to filtered view
  3. 2. SEO
    1. 2.1. Index/no index, follow/no follow drop down menu
    2. 2.2. Meta title
    3. 2.3. Meta description
    4. 2.4. Canonical field
    5. 2.5. Friendly URLs
    6. 2.6. HTTP Code 301 redirection Management
    7. 2.7. HTTP Code 404 page sending a valid 404 response error, customizable in CMS.
    8. 2.8. No frames, no iframes for content, no table for layout.
    9. 2.9. Semantics (correct headings)
    10. 2.10. No flash
    11. 2.11. Img alt
    12. 2.12. Robots.txt upload via ftp
    13. 2.13. Search engine friendly Breadcrumbs markup
    14. 2.14. No-www  with www redirection (if not on subdomain)
    15. 2.15. XML Sitemap
    16. 2.16. “Semantic” IDs and Classes for in tags for better event management via GoogleTagManager.
    17. 2.17. Ability to inject third party code at the bottom of the <head>

1. Technical requirements

1.1. Google tag manager

Test test

1.2. All site pages on https

1.3. Hidden form field to be injected by Javascript

1.4. Embedding of youtube

1.5. Use the open graph protocol

(​http://ogp.me/) for good presentation on social media

1.6. Don’t forget the favicon: ​http://css-tricks.com/favicon-quiz/

1.7. RSS feed for new courses

(once we have a blog, the blog will have its own RSS feed, here we need one for the courses)

1.8. Direct URL to filtered view

To design the course catalogue so we can provide a URL to a user that will direct him to a filtered view. (when the filtered view is reached, the relevant filter button should be “turned on”.) o Use case example: I would like to link to the course catalogue when only the water management courses are displayed, or, for example, to display only free courses, sorted by the start date.

2. SEO

2.1. Index/no index, follow/no follow drop down menu

2.2. Meta title

2.3. Meta description

2.4. Canonical field

2.5. Friendly URLs

2.6. HTTP Code 301 redirection Management

2.7. HTTP Code 404 page sending a valid 404 response error, customizable in CMS.

2.8. No frames, no iframes for content, no table for layout.

2.9. Semantics (correct headings)

2.10. No flash

2.11. Img alt

2.12. Robots.txt upload via ftp

2.13. Search engine friendly Breadcrumbs markup

See ​https://schema.org/breadcrumb

2.14. No-www  with www redirection (if not on subdomain)

2.15. XML Sitemap

2.16. “Semantic” IDs and Classes for in tags for better event management via GoogleTagManager.

2.17. Ability to inject third party code at the bottom of the <head>

(this cannot be done using google tag manager). This is needed for A/B testing software.