Repository for the gRPC website and documentation
Go to file
Muxi Yan b45663b5c8 Update quickstart to v2 API 2019-10-17 11:32:12 -07:00
.github/ISSUE_TEMPLATE Create issue template 2019-05-14 10:09:54 -07:00
archetypes Add contents of new site repo 2019-04-22 18:07:24 -07:00
content Update quickstart to v2 API 2019-10-17 11:32:12 -07:00
data Remove public folder from Git 2019-04-22 18:27:11 -07:00
layouts Update RSS feed image 2019-06-15 09:47:42 -07:00
static Merge pull request #52 from shirhatti/shirhatti/dotnetcore-blog-post 2019-09-23 20:08:34 +02:00
.gitignore Remove public folder from Git 2019-04-22 18:27:11 -07:00
CODE-OF-CONDUCT.md Add GOVERNANCE.md, CODE-OF-CONDUCT.md and CONTRIBUTING.md 2019-09-26 15:56:15 -07:00
CONTRIBUTING.md Add GOVERNANCE.md, CODE-OF-CONDUCT.md and CONTRIBUTING.md 2019-09-26 15:56:15 -07:00
GOVERNANCE.md Add GOVERNANCE.md, CODE-OF-CONDUCT.md and CONTRIBUTING.md 2019-09-26 15:56:15 -07:00
LICENSE Add contents of new site repo 2019-04-22 18:07:24 -07:00
Makefile Synchronize Hugo version between Netlify config and Makefile 2019-04-26 13:50:39 -07:00
README.md Revamp README and add Docker serving option 2019-04-23 11:03:52 -07:00
config.toml Merge branch 'master' into release/bump_version_1_24_0 2019-10-02 11:01:12 -07:00
deploy.sh Add contents of new site repo 2019-04-22 18:07:24 -07:00
netlify.toml Add contents of new site repo 2019-04-22 18:07:24 -07:00

README.md

The gRPC website and documentation

This repository houses the assets used to build and deploy the gRPC website, available at https://grpc.io. The site is built using the Hugo static site generator. Check out the Hugo Quick Start for a quick intro.

Running the site locally

To run the site locally, you need to install Hugo. Once Hugo is installed:

make serve

Alternatively, you can run the site using a Docker container:

make docker-serve

Publishing the site

The gRPC website is automatically published by Netlify. Any time changes are pushed to the master branch, the site is re-built and re-deployed. This process does not require manual management.

Site content

All of the Markdown content used to build the site's documentation, blog, etc. is in the content directory.