You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+32-11
Original file line number
Diff line number
Diff line change
@@ -29,21 +29,42 @@ $ bundle exec jekyll build
29
29
$ bundle exec jekyll serve
30
30
```
31
31
32
-
> You must run `bundle exec jekyll build` after every change and include the `docs` directory in your commit!
32
+
> You must run `bundle exec jekyll build` after every change and include the
33
+
> `docs` directory in your commit!
33
34
34
35
## Publishing
35
36
36
-
This site uses Jekyll plugins, so GitHub Pages will not build it automatically. To publish, check in manually built static site files to the `docs` directory.
37
+
This site uses Jekyll plugins, so GitHub Pages will not build it automatically.
38
+
To publish, check in manually built static site files to the `docs` directory.
37
39
38
-
The static site should be configured to build to the `docs` directory. The `docs` directory is a special directory from which GitHub pages can publish directly. The naming convention is unfortunate given the confusing overlap with the site's own `docs` pages (output to `docs/docs`) which are themselves generated from the design docs submodule located at `design`.
40
+
The static site should be configured to build to the `docs` directory. The
41
+
`docs` directory is a special directory from which GitHub pages can publish
42
+
directly. The naming convention is unfortunate given the confusing overlap with
43
+
the site's own `docs` pages (output to `docs/docs`) which are themselves
44
+
generated from the design docs submodule located at `design`.
39
45
40
46
## What is the role of `_config.yml` and the custom Jekyll plugins?
41
47
42
-
> Note: the following plugins are all hacks to make the workflow of generating website docs from the `design` repo work without updating the sources in the design repo.
43
-
44
-
-`gem 'jekyll-optional-front-matter'` loaded directly in the `Gemfile` allows markdown files without YAML frontmatter to be consumed directly. This is included to allow `design` repo `.md` files to be used as pages without modifying their source to add frontmatter.
45
-
-`gem 'jemoji'` loaded directly in the `Gemfile` replaces GitHub-style emoji markdown (e.g. `:+1:`) with images for compat.
46
-
- The `defaults` section of `_config.yml` adds default values to the YAML frontmatter of documents from the `design` repo. In particular, it specifies that all `.md` files in the design submodule should be labelled as type `doc` and given layout `doc.html`. It also manually moves a few docs into the `community` tree where they fit the site organization better.
47
-
-`auto_titles.rb` adds a `title` value to YAML frontmatter by looking for the first header tag in the source files. It also orders the design docs based on a hardcoded list.
48
-
-`link_converter.rb` turns the `design` repo's links (e.g. `[threads](FutureFeatures.md#threads)`) into their respective locations on this website (e.g. `[threads](/docs/future-features/#threads)`).
49
-
-`underscore_paths.rb` rewrites Jekyll page permalinks to convert `/design/FutureFeatures/` to `/docs/future-features/`.
48
+
> Note: the following plugins are all hacks to make the workflow of generating
49
+
> website docs from the `design` repo work without updating the sources in the
50
+
> design repo.
51
+
52
+
-`gem 'jekyll-optional-front-matter'` loaded directly in the `Gemfile` allows
53
+
markdown files without YAML frontmatter to be consumed directly. This is
54
+
included to allow `design` repo `.md` files to be used as pages without
55
+
modifying their source to add frontmatter.
56
+
-`gem 'jemoji'` loaded directly in the `Gemfile` replaces GitHub-style emoji
57
+
markdown (e.g. `:+1:`) with images for compat.
58
+
- The `defaults` section of `_config.yml` adds default values to the YAML
59
+
frontmatter of documents from the `design` repo. In particular, it specifies
60
+
that all `.md` files in the design submodule should be labelled as type `doc`
61
+
and given layout `doc.html`. It also manually moves a few docs into the
62
+
`community` tree where they fit the site organization better.
63
+
-`auto_titles.rb` adds a `title` value to YAML frontmatter by looking for the
64
+
first header tag in the source files. It also orders the design docs based on
65
+
a hardcoded list.
66
+
-`link_converter.rb` turns the `design` repo's links (e.g.
67
+
`[threads](FutureFeatures.md#threads)`) into their respective locations on
68
+
this website (e.g. `[threads](/docs/future-features/#threads)`).
69
+
-`underscore_paths.rb` rewrites Jekyll page permalinks to convert
70
+
`/design/FutureFeatures/` to `/docs/future-features/`.
0 commit comments