Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

The frontend, backend, and content source code for developer.chrome.com

License

NotificationsYou must be signed in to change notification settings

Hawthorne001/developer.chrome.com

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

This site has been migrated to a new platform. As of 7 November, 2023, we stopped merging new pullrequests for updates to existing content. You can raise content issues in the newissue tracker,and they will be addressed on the migrated site.


[Archived README]

developer.chrome.com is the ultimate resource for developers of all backgroundsto learn about what's new in Chrome!

Found a bug? 👷‍♀️

Thanks for letting us know!File an issue and a team member should reply shortly.

If you're submitting a pull request to fix a bug, read theContributing guidelines.

Authoring content ✍️

Before you start writing take a moment to look over thedeveloper.chrome.com handbook andfamiliarize yourself with the process.

Building the site 🏗

You'll need a recent version ofNode: v14 (LTS) or higher.To check your node version runnode -v in your terminal.

If you don't have node, or if you need to upgrade, we recommend using theNodeVersion Manager (nvm).

Clone the repo

⚠️ If you'd like to contribute (and you're not a member of the core team), be sure to fork the repo first, and clone the fork.

git clone https://github.com/GoogleChrome/developer.chrome.com.git

Install dependencies

npm ci

Set up build flags

Building the entire site can take a while because it's over a thousand pages.If you want tomassively speed up your build times, we suggest setting somebuild flags to ignore certain sections.

WARNING: By default, in dev we ignore all translated docs (all docs outside of /en/ directory).To include them back, useELEVENTY_INCLUDE_TRANSLATED=true env variable.

  • Create a.env file at the root of your project
  • Optionally add the following:
# Ignore ALL /docs/ELEVENTY_IGNORE_DOCS=true# Only ignore /docs/android/ELEVENTY_IGNORE_ANDROID=true# Only ignore /docs/apps/ELEVENTY_IGNORE_APPS=true# Only ignore /docs/devtools/ELEVENTY_IGNORE_DEVTOOLS=true# Only ignore /docs/extensions/ELEVENTY_IGNORE_EXTENSIONS=true# Only ignore /docs/handbook/ELEVENTY_IGNORE_HANDBOOK=true# Only ignore /docs/lighthouse/ELEVENTY_IGNORE_LIGHTHOUSE=true# Only ignore /docs/multidevice/ELEVENTY_IGNORE_MULTIDEVICE=true# Only ignore /docs/native-client/ELEVENTY_IGNORE_NACL=true# Only ignore /docs/privacy-sandbox/ELEVENTY_IGNORE_PRIVACY_SANDBOX=true# Only ignore /docs/versionhistory/ELEVENTY_IGNORE_VERSIONHISTORY=true# Only ignore /docs/webstore/ELEVENTY_IGNORE_WEBSTORE=true# Only ignore /docs/workbox/ELEVENTY_IGNORE_WORKBOX=true# Ignore BLOG /blog/ELEVENTY_IGNORE_BLOG=true

To build only a specific component, start with the above.env file and change the value for thecomponent you wish to build. You can comment it out, or set it to0 orfalse.

Start a local server to preview the site

npm run dev

Openhttp://localhost:8080/ to see the site locally. Changes to assets willrebuild the site. Refresh to see your changes.

Run linters to address bugs

Before you push your branch, find and address any errors.

npm run lint

Environments 🌳

To do a production build of the site and start the local serverrunnpm run production && npm start.

Staging 🕺

When you send in a pull request it will be automatically staged for you. Keep aneye out for the netlify bot to comment on the pull request with your unique URL.

(Googlers only) If you would like to stage yourlocal changes to a unique URL,run the commandnpm run stage:personal. This can be useful if you're not readyto create a pull request yet, or if you need to stage something private.

☝️ You will need to be a member of our GCP project for this command to work.

Deploying the site 🚀

Automatic deploys

The site will build and deploy themain branch automatically every hour,Mon–Fri. If you've just merged an article then it should go live at the topof the next hour.

About

The frontend, backend, and content source code for developer.chrome.com

Resources

License

Code of conduct

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • HTML47.2%
  • SCSS26.9%
  • JavaScript13.3%
  • Nunjucks12.5%
  • Shell0.1%

[8]ページ先頭

©2009-2025 Movatter.jp