@@ -52,131 +52,34 @@ changes locally.
52
52
53
53
### Instant Development environment
54
54
55
- If you open this repository in VSCode, and you have Docker, and you have the VSCode extension for remote containers,
56
- then VSCode will offer to open the folder in a container. Accept that, and you'll have a development environment
57
- with the right tools installed.
55
+ ### Docker
58
56
59
- In the terminal inside VSCode, you can type
60
-
61
- ` serve ` and then access your local, hot-reloading version of these docs on localhost:8000.
62
-
63
- ` build ` will build the site and test the links.
64
-
65
- You may now skip the rest of this section. Continue with [ including code snippets from other repos] [ code-snippets ]
66
-
67
- ### Working outside Docker
68
-
69
- You may need or prefer to install the tools on your computer instead.
70
-
71
- #### Install dependencies
72
-
73
- The project uses [ MkDocs] [ mkdocs ] to generate the static site
74
- and [ htmltest] [ htmltest ] to validate the generated HTML. Below
75
- are instructions to install them in a non-obtrusive way.
76
-
77
- [ htmltest ] : https://github.com/wjdp/htmltest
78
-
79
- #### MkDocs
80
-
81
- First [ install Python 3] [ py-install ] using [ Homebrew] [ brew ] on Mac OS X.
82
-
83
- [ py-install ] : https://github.com/Homebrew/brew/blob/master/share/doc/homebrew/Homebrew-and-Python.md
84
- [ brew ] : https://brew.sh/
57
+ You can build the docs with the following command.
85
58
86
59
```
87
- $ brew install python3 htmltest
60
+ $ docker run -it --rm -v "$PWD:/docs" squidfunk/mkdocs-material:5.3.3 build --strict
88
61
```
89
62
90
- or on Debian-based GNU/Linux distributions
63
+ You can also run ` htmltest ` .
91
64
92
65
```
93
- $ sudo apt-get install python3-pip htmltest
66
+ $ docker run -it --rm -v "$PWD:/test" wjdp/htmltest:v0.12.0 htmltest
94
67
```
95
68
96
- Then create a [ virtual environment ] [ venv ] to host the dependencies:
69
+ ### VS Code
97
70
98
- [ venv ] : https://virtualenv.pypa.io/en/stable/
71
+ If you open this repository in VSCode, and you have Docker, and you
72
+ have the VSCode extension for remote containers, then VSCode will
73
+ offer to open the folder in a container. Accept that, and you'll have
74
+ a development environment with the right tools installed.
99
75
100
- ```
101
- $ pip3 install virtualenv
102
- $ mkdir ~/.venvs
103
- $ echo "export PIP_REQUIRE_VIRTUALENV=true" >> ~/.bashrc
104
- $ source ~/.bashrc
105
- $ virtualenv ~/.venvs/docs
106
- ```
107
-
108
- With the virtual environment created, activate it in the current
109
- terminal:
110
-
111
- ```
112
- $ . ~/.venvs/docs/bin/activate
113
- ```
114
-
115
- and install the dependencies into it:
116
-
117
- ```
118
- $ pip install -r requirements.txt
119
- ```
120
-
121
- #### Testing and serving
122
-
123
- Every time you want to work on this repository, you need to activate
124
- the Python virtualenv in your working terminal:
125
-
126
- ```
127
- $ . ~/.venvs/docs/bin/activate
128
- ```
129
-
130
- After making changes, you can test them by building the documentation
131
- in strict mode.
132
-
133
- ```
134
- $ mkdocs build --strict
135
- ```
136
-
137
- The run ` htmltest ` .
138
-
139
- ```
140
- $ htmltest -c .htmltest.yml site
141
- ```
142
-
143
- To review your changes in a browser, you can serve the documentation
144
- locally by running:
145
-
146
- ```
147
- $ mkdocs serve
148
- ```
149
-
150
- and browse the documentation at http://127.0.0.1:8000 . To stop the
151
- server, press ` Ctrl-C ` in the terminal.
152
-
153
- ## Code snippets
154
-
155
- [ code-snippets ] : #code-snippets
156
-
157
- You can create code snippets in the [ atomist/samples] [ samples ]
158
- repo. Demarcate a code snippet using the following comment
159
-
160
- ``` typescript
161
- // atomist:code-snippet:start=SNIPPET_NAME
162
- CODE HERE
163
- // atomist:code-snippet:end
164
- ```
165
-
166
- replacing ` SNIPPET_NAME ` with a unique name for the snippet.
167
-
168
- You can then include that snippet in the docs using the following HTML
169
- comment in the Markdown source.
76
+ In the terminal inside VSCode, you can type
170
77
171
- ``` html
172
- <!-- atomist:code-snippet:start=SNIPPET_NAME -->
173
- <!-- atomist:code-snippet:end -->
174
- ```
78
+ ` serve ` and then access your local, hot-reloading version of these docs on localhost:8000.
175
79
176
- Then, when either this docs repo or the samples repo is updated, the
177
- snippets will be updated in this docs repo.
80
+ ` build ` will build the site and test the links.
178
81
179
- [ samples ] : https://github.com/atomist/samples
82
+ You may now skip the rest of this section. Continue with [ including code snippets from other repos ] [ code-snippets ]
180
83
181
84
## Styles
182
85
@@ -227,16 +130,14 @@ Items on the same line create a visually equivalent admonition.
227
130
## Releasing
228
131
229
132
When a push is made to this repository, the documentation is built by
230
- the [ docs-sdm] [ ] and published to the S3 bucket
231
- [ docs-sdm.atomist.com] [ docs-sdm-s3 ] under a path starting with the
232
- full commit SHA.
133
+ [ atomist-web-sdm] [ ] and published to
134
+ [ https://docs.atomist.services/ ] [ docs-staging ] .
233
135
234
- If the publication to the docs-sdm bucket is approved, the site is
235
- "published" to the docs.atomist.com S3 bucket, making it available at
136
+ If the the staging deployment is approved, the site is "published" to
236
137
[ https://docs.atomist.com/ ] [ atomist-doc ] .
237
138
238
- [ docs- sdm] : https://github.com/atomist/docs -sdm
239
- [ docs-sdm-s3 ] : http ://docs-sdm .atomist.com.s3-website-us-west-2.amazonaws.com /
139
+ [ atomist-web- sdm] : https://github.com/atomist/atomist-web -sdm
140
+ [ docs-staging ] : https ://docs.atomist.services /
240
141
241
142
### Updating dependencies
242
143
@@ -256,15 +157,6 @@ To update html-proofer and its dependencies:
256
157
$ bundle update
257
158
```
258
159
259
- ### Shortcut
260
-
261
- The ` activate_and_serve.sh ` script activates the virtual environment
262
- and builds, proofs, and serves the docs with a single command.
263
-
264
- ``` shell
265
- ./activate_and_serve.sh
266
- ```
267
-
268
160
## Conditions of use
269
161
270
162
This documentation build process is provided to the public purely for
0 commit comments