Computing Hubs: East of England & East Midlands Website Requirements

Computing Hubs: East of England & East Midlands Website Requirements

Technology

• The website MUST include the use of HTML, CSS, and JavaScript.
• All media content MUST be sourced from the client or have appropriate licensing (royalty free, copyright free, and suitable for commercial use).
• All media content requiring accreditation MUST be properly credited.
• Images MUST be stored in a separate folder from the code files within the web project.
• The website SHOULD include custom written CSS.
• Custom CSS SHOULD be stored in its own file separate from HTML / JavaScript.
• The website SHOULD include CSS from a library / framework.
• The website SHOULD include custom written JavaScript.
• Custom JavaScript SHOULD be stored in its own file separate from HTML / CSS.
• The website SHOULD include JavaScript from a library / framework.
• The website MAY call external API services to provide extra functionality or data.
• The website MAY make use of videos or audio content.
• The website MAY use advanced HTML functionality such as drag-and-drop.

General

• The website MUST have a home page.
• The website MUST have a remote courses page.
• The website MUST have a face-to-face courses page.
• The website MUST have an events page.
• The website MUST have a contact us page.
• All pages MUST display the logo and organisation name.
• All main pages MUST be accessible from all other pages (navigation).
• All pages MUST have a footer at the bottom of the page with legal information.
• All sections and pages MUST meet the brand guidelines 1.3 for colour scheme.
• All sections and pages MUST meet the brand guidelines 1.4 for fonts.
• All pages with regularly changing content SHOULD be updatable from an external file or source (e.g. courses, events, news and updates pages).
• All pages SHOULD have an appropriate title shown in the browser tab.
• All pages SHOULD have at minimum span the entire height and width of the screen regardless of content size.
• The website MAY support dynamic sizing for a mobile sized screen.
• The website MAY support searching functionality.
• You MAY propose additional functionality for the website, which can be implemented upon approval. 

Footer

• The footer MUST contain the contact details of Teach Computing.
• The footer SHOULD contain the social media links of Teach Computing.
• The footer SHOULD contain details of the parent organisation (NCCE).
• The footer MAY contain links to a Terms and Conditions page or message.

Home Page

• The home page MUST include a welcome message.
• The home page MUST include images to showcase computing study.
• The home page MUST include an “Who We Are” section (handbook page 2).
• The home page MAY include advanced UI features e.g. clickable cards, animation.
• The home page MAY include a news and updates or what’s on section (handbook page 6).

Remote Courses Page

• The remote courses page MUST include a single table displaying all remote courses.
• The remote courses table MUST include all details available (handbook page 3).
• The remote courses table SHOULD be populated by loading content from a JSON formatted external file.
• The “Book Now” links for the remote courses SHOULD be valid booking links as provided in the handbook page 3.
• The QR code from handbook page 3 SHOULD NOT be displayed on the page.
• The remote courses table MAY include searching, ordering, and/or filtering options.
• The remote courses page MAY support a custom print view of the page, showing only the title and table.
• The custom print view MAY include the QR code as provided on handbook page 3.

Face-To-Face Courses Page

• The F2F courses page MUST include a single table displaying all face-to-face course locations.
• The F2F courses table MUST include all details available (handbook page 4).
• The F2F courses table SHOULD be populated by loading content from a JSON formatted external file.
• The “Book” links for the F2F courses SHOULD be valid booking links as provided in the handbook page 4.
• The QR codes from handbook page 4 SHOULD NOT be displayed on the page.
• The remote courses page MAY support a custom print view of the page, showing only the title and table.
• The custom print view MAY include the QR codes as provided on handbook page 4.

Events Page

• The events page MUST include a single table displaying all events.
• The events page MUST include a link to the Eventbrite website for ICTs, ECTs and I Belong as shown on handbook page 5.
• The events page MUST include a link to the ISAAC student events website as shown on the handbook page 5.
• The events table MUST include all details available (handbook page 5 & 6).
• The events table SHOULD be populated by loading content from a JSON formatted external file.
• The “Book” links for the events SHOULD be valid booking links as provided in the handbook page 5.
• The QR codes from handbook page 5 SHOULD NOT be displayed on the page.
• The events page MAY support a custom print view of the page, showing only the title and table.
• QR Codes MAY be generated for each of the booking links and included on the custom print view.

Contact Us Page

• The contact page MUST display the Teach Computing contact details as provided on handbook page 7.
• The contact page MUST include a contact form.
• The contact form MUST ask for name, email address, subject, and message.
• The contact form MUST show a message on submission.
• The contact form MUST NOT send an actual communication to the client.
• The contact page SHOULD include any further contact details which can be found through the Teach Computing website.
• The contact page SHOULD include contact details for each of the East of England and East Midlands hubs.
• The contact form MAY include validation checks for empty fields.
• The contact form MAY save or display the input content when submitted to evidence its functionality.
• The contact page MAY display an interactive map with pins showing the location of the different hubs.

Accessibility and Performance

• The website MUST meet WCAG guidelines on colour contrast for accessibility.
• The website MUST achieve a green score for accessibility using Google Lighthouse.
• The website SHOULD achieve green scores in all areas using Google Lighthouse.
• The website MAY achieve green scores in all areas using Google Lighthouse in mobile device mode.

Note 1: Where logos cannot be provided by the client, cropped versions from brand guideline documentation can be used instead.

Note 2: Layout of the main content, such as the order of content being presented is left to developer discretion unless otherwise specified.