Skip to content
Best practices for modern web development
Branch: master
Clone or download
Latest commit 26b905d May 20, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add guide on JS modules (#6272) Jun 18, 2018
gae Framebox tweak Feb 26, 2019
gulp-tasks Fixes build break May 1, 2019
src add missing "the" May 20, 2019
tools Remove outdated & orphaned translations (#7632) May 16, 2019
.csslintrc Just file moves: Jan 5, 2015
.eslintrc Add Puppeteer to /web/tools/ (#5644) Jan 16, 2018
.gitignore ignore index.yaml (#7147) Jan 29, 2019
.gitmodules Fixing the build Sep 9, 2015
.jscsrc Moves next-version into master Oct 12, 2016
.jshintrc Removing existing files, will add under old/ Jun 30, 2015
.nvmrc Update to Node.js v10 (#6769) Oct 30, 2018
.travis.yml Update to Node.js v10 (#6769) Oct 30, 2018 Update link to new styleguide in CONTRIBUTING (#4756) Jun 26, 2017
LICENSE Moves next-version into master Oct 12, 2016 fix typo (#6791) Nov 1, 2018 Point to new translation guide Jul 6, 2016
app.yaml Minor tweaks to the updates templates Oct 23, 2018 Moves next-version into master Oct 12, 2016 Desktop PWA refactor (#6731) Oct 16, 2018 Propose fix typo for occurred (#5757) Feb 8, 2018 Improved template support (#5656) Jan 17, 2018 Migrates Hacked guides into WebFu (#5233) Dec 22, 2017 Font update & Code Highlighting (#6420) Jul 24, 2018 Font update & Code Highlighting (#6420) Jul 24, 2018 Fixes variable check Sep 19, 2018
gcloud-client-secret.json.enc Migrate to Travis CI from Drone (#4143) Feb 6, 2017
gulpfile.js Makes building RSS/ATOM feeds optional (#6225) Jun 5, 2018
package.json Generate latest workbox docs (#7565) May 1, 2019 Move update-resources to start-appengine Feb 6, 2018

Web Fundamentals on DevSite

Build Status

Welcome to the new WebFundamentals! An effort to showcase best practices and tools for modern Web Development.

What's changed?

  • We're now using the DevSite infrastructure
    • New style guide
    • New widgets allow inline JavaScript, common links, related guide and more
  • Jekyll has been eliminated. Instead, pages are rendered at request time
  • Front-matter has been eliminated from the markdown, but files now require a simple set of tags

What stays the same?

Cloning the repo

If you have a high-bandwidth connection, I recommend starting with a fresh clone of the repo.

git clone

Getting set up

The new DevSite infrastructure simplifies the dependencies a lot. Ensure you have Node 10 or greater, and the AppEngine SDK for Python already installed.

  1. Run npm install (needed for the build process)

Build the auto-generated files

Some files (contributors includes, some pages for updates, showcases, etc.) are automatically generated. The first time you clone the repo and run npm install, this is done for you. However, when you add a case study, update, etc., you'll need to re-build those files using:

npm run build

Start Local Server

To view the site locally, just run:

npm start

Note: The first time you start the server, you may need to run and answer any prompts provided by

Update the code labs

To update the Code Labs, you'll need the claat tool and access to the original Doc files. This will likely only work for Googlers.

  1. Download the claat tool and place it in your tools directory.
  2. Run tools/
  3. Check the latest changes into GitHub

Start the development server

  1. Run npm start

Test your changes before submitting a PR

Please run your changes through npm test before submitting a PR. The test looks for things that may cause issues with DevSite and tries to keep our content consistent. It's part of the deployment process, so PRs will fail if there are any errors! To run:

npm test
You can’t perform that action at this time.