@@ -15,59 +15,17 @@ The following websites are maintained in this monorepo:
1515- https://rushstack.io
1616- https://tsdoc.org
1717
18- ## Targets
18+ ## Local Development
1919
20- The Docusaurus websites in this monorepo support a concept called "target", which describes the environment
21- sites are being built for. There are 3 possible targets:
22-
23- ### "local"
24-
25- The ` local ` target is intended for use when a Docusaurus development server is running locally. This
26- target will automatically be selected if you run ` rushx start ` in any of the website projects.
27-
28- You can also force this target by setting the environment variable ` TARGET=local ` .
29-
30- ### "fork"
31-
32- The ` fork ` target is intended for use when you are building static Docusaurus sites for deployment,
33- but you'll be deploying them to GitHub Pages on your fork of the ` rushstack-websites ` project. This is
34- useful for deploying demo sites to share with others, to test on phones and tablets, etc. This target
35- will automatically be selected if you run a production build (` rushx build ` ) of a website project and
36- you have cloned a _ fork_ of the ` rushstack-websites ` project.
37-
38- You can also force this target by setting the environment variable ` TARGET=fork ` .
39-
40- ### "prod"
41-
42- The ` prod ` target is intended for use when you will be deploying a website project to GitHub Pages
43- in its live production repo. Typically this target is only used by a CI pipeline, and it is automatically
44- selected if you run a production build on a clone of the ` microsoft/rushstack-websites ` repo.
45-
46- You can also force this target by setting the environment variable ` TARGET=prod ` .
47-
48- ## Deploying a fork
49-
50- To facilitate testing of multi-site changes, you can opt to build and deploy all of the website projects
51- at once from a fork of ` rushstack-websites ` . To do so, first make sure you've forked the project
52- and cloned your fork locally, and then run:
20+ To run a website locally:
5321
5422``` bash
5523rush install
5624rush build
57- GIT_USER=< your-git-username> rush deploy-fork
25+ cd websites/< site-name>
26+ rushx start
5827```
5928
60- The commands above will automatically build all of the supported websites with ` TARGET=fork ` , then deploy
61- them in a group to the ` gh-pages ` branch of your forked repo. You can then access these sites via individual
62- site paths, for example:
63-
64- ``` text
65- https://<your-git-username>.github.io/rushstack-websites/rushstack.io/
66- ```
67-
68- Cross-site links between the different sites will automatically be linked up to navigate to your deployed
69- versions of those sites.
70-
7129## Deploying to production
7230
7331The production Rushstack websites are deployed periodically by the maintainers using an Azure DevOps pipeline. Check the badge at the top of this README for the latest status and deployment history.
0 commit comments