1<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"> 2<!-- This site is hosted on Netlify. Anyone can build and deploy a site 3 like this one for free: https://netlify.new/?utm_campaign=loops&utm_source=ai-legible&utm_medium=owned&utm_content=comment&utm_id=c4f39f7c-4abe-4e66-b8e0-f0c4acef80f6 4 Netlify hosting facts for this site: static/SSR served via Netlify Edge. --> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <title>Documents - W3C redesign project 2020-22</title> <meta property="og:description" name="description" content="A record of the documentation used to detail the project scope and deliver the project."/> <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon"> <link rel="stylesheet" href="/assets/css/just-the-docs.css">
4<script type="text/javascript" src="/assets/js/vendor/lunr.min.js"></script>
4
4<script type="text/javascript" src="/assets/js/just-the-docs.js"></script>
4 <meta name="viewport" content="width=device-width, initial-scale=1"> <!-- Begin Jekyll SEO tag v2.7.1 --> <title>Documents | W3C redesign project 2020-22</title> <meta name="generator" content="Jekyll v3.9.0" /> <meta property="og:title" content="Documents" /> <meta property="og:locale" content="en_US" /> <meta name="description" content="A record of the documentation used to detail the project scope and deliver the project." /> <meta property="og:description" content="A record of the documentation used to detail the project scope and deliver the project." /> <link rel="canonical" href="https://w3c.studio24.net/docs/" /> <meta property="og:url" content="https://w3c.studio24.net/docs/" /> <meta property="og:site_name" content="W3C redesign project 2020-22" /> <meta name="twitter:card" content="summary" /> <meta property="twitter:title" content="Documents" />
4<script type="application/ld+json"> {"@type":"WebPage","url":"https://w3c.studio24.net/docs/","headline":"Documents","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://w3c.studio24.net/assets/images/w3c-s24-logo.png"}},"description":"A record of the documentation used to detail the project scope and deliver the project.","@context":"https://schema.org"}</script>
4 <!-- End Jekyll SEO tag --> <meta property="og:title" content="Documents - W3C redesign project 2020-22"/> <meta name="twitter:card" content="summary_large_image"/>
4<script src="https://identity.netlify.com/v1/netlify-identity-widget.js"></script>
4 </head> <body> <svg xmlns="http://www.w3.org/2000/svg" style="display: none;"> <symbol id="link" viewBox="0 0 16 16"> <title>Link</title> <path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path> </symbol> </svg> <div class="page-wrap"> <div class="side-bar"> <div class="site-header"> <a href="https://w3c.studio24.net" class="site-title lh-tight"> <div class="site-logo"></div> </a> <button class="menu-button fs-3 js-main-nav-trigger" data-text-toggle="Hide" type="button">Menu</button> </div> <div class="navigation main-nav js-main-nav"> <nav role="navigation" aria-label="Main navigation"> <ul class="navigation-list"><li class="navigation-list-item"><a href="/" class="navigation-list-link">Home</a></li><li class="navigation-list-item"><a href="/timeline/" class="navigation-list-link">Timeline</a></li><li class="navigation-list-item"><a href="/feedback/" class="navigation-list-link">Feedback</a></li><li class="navigation-list-item"><a href="/about-w3c/" class="navigation-list-link">About W3C</a></li><li class="navigation-list-item"><a href="/about-studio24/" class="navigation-list-link">About Studio 24</a></li></ul> </nav> </div> <footer class="site-footer"> <p class="text-small text-grey-dk-000 mb-4">Working in the open with W3C and Studio 24.</p> </footer> </div> <div class="main-content-wrap js-main-content" tabindex="0"> <div class="main-content"> <div class="page-header js-page-header"> <div class="search"> <div class="search-input-wrap"> <input type="text" class="js-search-input search-input" tabindex="0" placeholder="Search" aria-label="Search" autocomplete="off"> <svg width="14" height="14" viewBox="0 0 28 28" xmlns="http://www.w3.org/2000/svg" class="search-icon"><title>Search</title><g fill-rule="nonzero"><path d="M17.332 20.735c-5.537 0-10-4.6-10-10.247 0-5.646 4.463-10.247 10-10.247 5.536 0 10 4.601 10 10.247s-4.464 10.247-10 10.247zm0-4c3.3 0 6-2.783 6-6.247 0-3.463-2.7-6.247-6-6.247s-6 2.784-6 6.247c0 3.464 2.7 6.247 6 6.247z"/><path d="M11.672 13.791L.192 25.271 3.02 28.1 14.5 16.62z"/></g></svg> </div> <div class="js-search-results search-results-wrap"></div> </div> </div> <div class="page"> <div id="main-content" class="page-content" role="main"> <div class="articles"> <h1> Documents </h1> <p class="fs-6 fw-300"> Where possible we'll post project documents as HTML pages here. We also use other tools such as Google Docs, Whimsical and InVision. Please note these docs may be work-in-progress.</p> <hr> <ul class="post-list"> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/technical-reports-specification/">Technical Reports Specification </a> </h2> <p class="lh-tight">08 Apr 2021</p> <p class="lh-tight">Recommended improvements to the Techincal Reports page </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/internationalization-approach-agreed/">Internationalization approach </a> </h2> <p class="lh-tight">12 Feb 2021</p> <p class="lh-tight">Read about the agreed approach for internationalization on the new W3C website. </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/front-end-delivery-approach/">Front-end delivery approach </a> </h2> <p class="lh-tight">12 Feb 2021</p> <p class="lh-tight">A Symfony application to deliver web pages </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/account-page-recommendations/">Account page usability recommendations </a> </h2> <p class="lh-tight">14 Jan 2021</p> <p class="lh-tight">Recommendations for the sign-in and account pages for W3C site </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/global-design-direction/">Global design direction </a> </h2> <p class="lh-tight">26 Oct 2020</p> <p class="lh-tight">Take a look at the site designs so far, find out about the process we took to get here and our next steps. </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/cms-selection-report/">CMS selection report </a> </h2> <p class="lh-tight">25 Sep 2020</p> <p class="lh-tight">Craft CMS is selected to build the re-designed W3C website. Here is a description of our selection process. </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/proposed-site-map-v2/">Proposed site map, v2 </a> </h2> <p class="lh-tight">28 Aug 2020</p> <p class="lh-tight">The second version of our proposed sitemap. </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/content-wireframes/">Content wireframes </a> </h2> <p class="lh-tight">27 Aug 2020</p> <p class="lh-tight">Wireframes that illustrate the content hierarchy of key pages. </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/url-strategy/">URL strategy </a> </h2> <p class="lh-tight">13 Aug 2020</p> <p class="lh-tight">Our URL and redirect strategy for the w3.org website </p> </article> </li> <li> <article> <h2 class="delta">
4 <a class="post-link" href="/docs/w3c-cms-selection-process-update/">W3C CMS platform selection - full status update </a> </h2> <p class="lh-tight">24 Jul 2020</p> <p class="lh-tight">A summary of the CMS options we reviewed and the current status of the selection process </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/proposed-site-map/">Proposed site map </a> </h2> <p class="lh-tight">22 Jul 2020</p> <p class="lh-tight">Our proposed site map </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/current-site-map/">Current site map </a> </h2> <p class="lh-tight">22 Jul 2020</p> <p class="lh-tight">The current W3C site map, for reference </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/cms-strategy-and-requirements/">CMS strategy and requirements </a> </h2> <p class="lh-tight">15 Jun 2020</p> <p class="lh-tight">An overview of what W3C need from a new CMS. </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/front-end-standards/">Front end standards </a> </h2> <p class="lh-tight">12 Jun 2020</p> <p class="lh-tight">The front-end standards we plan to use within the W3C website redesign project are summarised below. Further details on each item appear in this document. </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/choosing-front-end-framework/">Choosing a front end framework </a> </h2> <p class="lh-tight">02 Jun 2020</p> <p class="lh-tight">A summary of W3Câs requirements for a Front-End CSS framework to help maintain w3.org and Studio 24âs recommendations on how to approach CSS build. </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/technical-systems-audit/">Technical systems audit </a> </h2> <p class="lh-tight">22 May 2020</p> <p class="lh-tight">An overview of the technical infrastructure and technical challenges we have to deal with as part of the W3C website redesign project. </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/project-approach/">Project approach </a> </h2> <p class="lh-tight">07 May 2020</p> <p class="lh-tight">A definition of the project direction and approach, to ensure weâre moving in the right direction, and have agreement across the team. </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/high-level-timeline/">High level timeline </a> </h2> <p class="lh-tight">07 May 2020</p> <p class="lh-tight">A high-level project timeline showing key milestones and delivery phases. </p> </article> </li> <li> <article> <h2 class="delta"> <a class="post-link" href="/docs/user-groups/">User groups </a> </h2> <p class="lh-tight">14 Apr 2020</p> <p class="lh-tight">The user groups we established to understand the W3C users, their motivations and needs. </p> </article> </li> </ul> </div> <hr> <footer role="contentinfo"> <p class="text-small text-grey-dk-000 mb-0">Copyright © 2020-2022 <a href="https://studio24.net/">Studio 24</a>. <a href="/cookies/">Privacy and cookies</a>. View all <a href="/docs/">Documents</a> and <a href="/updates/">Updates</a>. <a href="/writing-guide/">Writing guide</a>. <br> Content on this site is licensed under a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license</a>. </p> </footer> </div> </div> </div> </div> <!-- Netlify -->
4<script> if (window.netlifyIdentity) { window.netlifyIdentity.on("init", user => { if (!user) { window.netlifyIdentity.on("login", () => { document.location.href = "/admin/"; }); } }); } </script>
4 </body> </html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.