Create a Wordpress Template for a website

John Scottus Educational Trust (JSET) is the patron of John Scottus National & Secondary Schools (JSS) JSS has a shared website, [login to view URL], and has recently agreed to redevelop the website as its primary marketing / communications channel with current and prospective parents, students and relevant other external stakeholders. The website has been developed in Wordpress and the new redeveloped website should also be developed in Wordpress. It is envisaged that the new website would be highly visual in appearance with a simple site architecture and accessible / meaningful text Platform & Plugins The existing website uses free open-source applications centred around “Wordpress”, and our preference is to continue using open source SW. The new website must retain all existing functionality such as on-line payment and integration of video [login to view URL] intent is to extend the JSS online presence to social networking and so Social media feeds (e.g Twitter, Facebook), must be encorporated. Stylistic “branding” The graphic style of the new website must portray JSS in a unique way and should incorporate our school colours and logo. Navigation A common navigation bar should be included on all pages. The navigation bar will include links to the home page, Senior School, Primary school, Ethos, Locations, Past Pupils, Payments, about us, and contact details. Content, device independence, and user accessibility The new website must be constructed in compliance with “Responsive Web Design”, “One Web”, “Mobile First” objectives in conformance with World Wide Web Consortium ([login to view URL]) specifications, including HTML5 for structural and semantic markup, CSS3 for styling with Media Queries for progressive enhancement, and best-practices guides (mobile web authoring, device-independent authoring, default delivery context, etc). 1. Output of the CMS must pass W3C validation ([login to view URL]) for HTML5, CSS3, and MobileOK with no “critical” or “severe” failures. However, moderate violations of MobileOK filesize limitations and diagnostics resulting from the non-essential use of vendor-prefix CSS3 specifications are acceptable. 2. Output of the CMS must transparently support a wide diversity of end-user hardware and software that will range from no-longer-supported to state-of-the-art desktop computers and laptops running a variety of operating systems (Windows, MacOS, Linux, etc) to an ever-growing array of tablets, smartphones, and other mobile devices. All of the content must display with the common user-device browsers (Chrome, Firefox, Internet Explorer, Opera, Safari) even though some versions of some browsers may not support certain aspects of HTML5 and/or CSS3. All of the content must also be available to special-purpose browsers (plain-text browsers such as Lynx, readers for the visually impaired, etc). 3. The content must dynamically adjust to whatever screen-size area the user has chosen for the browser window (the “viewport”), and to the small-screen display of a smartphone, without resorting to having separate versions of content for different categories of devices. (For examples, see the “Media Queries” website, [login to view URL]). 4. The content for which JSS is responsible must not use “cookies”, Java, FLASH , “frames”, or “pop-up” windows, and Javascript must not be a requirement for navigating and/or displaying content. (It is understood, however, that we may wish to incorporate some of these features in future.) Content architecture and layout The following website of a sister school in London has been identified as a best practice prototype: [login to view URL]