Welcome to Astar Docs GitHub Repo.
This website is built using Docusaurus, a modern static website generator.
-
Method 1: Make sure
git
andyarn
exist as commands in your terminal or VS Code: https://yarnpkg.com/ (NOTE: Please make sure you use yarn 1 (classic) by using commandyarn set version classic
-
Git/Github: understand what the following commands do
- managing branches (
git checkout main
andgit checkout -b feat/your-new-branch
- Commits (
git add .
andgit commit
,git push -u origin feat/your-new-branch
) - Creating PR in Github
- maybe: stashing (
git stash
andgit stash pop
are your best friends)
- managing branches (
-
Markdown basics
- titles, subtitles
- lists
- hyperlinks
-
Method 2: Make sure
yarn
exists as a command in your terminal or VS Code and Github Desktop is installed. All thegit
operations described below can also be found within the menu of the desktop application, and common operations are clearly visible on launch.
- Clone repo
git clone https://github.com/astarnetwork/astar-docs
- Install dependencies by running
yarn
(cd astar-docs
,yarn
) yarn start
- spin up a realtime website that updates dynamically based on your changes to the code.
- Get latest version of docs locally
- Make sure you’re on the main branch (
git checkout main
) - Pull the latest version of the docs (
git pull
) - Create a new branch (
git checkout -b feat/new-feature-name-here
)
- Make sure you’re on the main branch (
- Create/update the docs as you please
- Spin up live docs (
yarn start
)- If you are working on a translation of a document use
yarn start --locale IT
(example for Italian) (checkout Docusaurus docs or further reference
- If you are working on a translation of a document use
- Add new page/tweaks/etc
- When you’re happy with it, ensure
yarn build
runs without errors
- Spin up live docs (
- PR and staging environment
- Commit your changes and push the new branch up to Github (
git add .
andgit commit
,git push -u origin feat/your-new-branch
) - Create a new PR on Github (https://github.com/astarnetwork/astar-docs)
- Once PR is up, CICD will automatically build you a unique staging link. You can view the progress of this on the Actions tab on Github
- Wait for feedback from the team
- Commit your changes and push the new branch up to Github (
-
Please import and use the
<Figure/>
tag instead of![image]
as this enables smoother translation of docs to other languages (automatic reference to original images, no need to copy images to translated subfolders) and automatically applies some styling such as line breaks.-
Example - as seen here:
top of file:
import Figure from "/src/components/figure"
within the file:
<Figure caption="Tokenomics Model" src={require('/docs/about/token-economics/img/tokenomics_1.png').default } width="100%" />
-
Please use absolute path to image (e.g.
/docs/about/token-economics/img/tokenomics_1.png
instead ofimg/tokenomics_1.png
-
- When a PR is ready for merge, click the button at the bottom saying Merge and Close and then Confirm
- After a few minutes you should see your changes updated on the production site at
[https://docs.astar.network](https://docs.astar.network)
- Likely, a broken build got pushed to
main
somehow. Remove the commit frommain
and force push tomain
, reopen PR in a new PR.