We’re glad that you are interested in contributing to SuperTokens 🎉 We welcome contributions of all kinds (discussions, bug fixes, features, design changes, videos, articles) and from anyone 👩💻🤚🏿🤚🏽🤚🏻🤚🏼🤚🏾👨💻.
- The documentation for each recipe and sdk lives in it's own folder e.g
auth-react
for auth-react sdk. - Each of these folders is a docusaurus v1 project containing two important folders:
docs
- contains markdown files where we write the content of our documentationwebsite
- contains following important files and folders:build
- this is where final docs build is storedstatic
- static assets for the docsversioned_docs
- contains.md
files which contain versioned docsversioned_sidebars
- configuration file for sidebar in resulting docs build which link to a particular docs versioncreateVersion
,initVersions
- shell scripts for creating versioned docssidebars.json
- here we define the contents of sidebar menusiteConfig.js
- config for the docusaurus buildversions.json
- contains an array of versions being used in that particular docs folder
- You can ignore the docker files
- Run
./setupProject
. This script installs npm deps for each of the docs folders, for the local dev server and builds the docs pages. - run
./buildDocs FOLDER_NAME
from the root of docs repo e.g if you are modifyingauth-react
docs run./buildDocs auth-react
- Run the local server which resides in
docs_dev_server
:cd docs_dev_server/app
followed bynpm run start
. This will start the server onhttp://localhost:9001/
- Every time you make changes to a particular docs folder you have to run
./buildDocs FOLDER_NAME
from the root of docs repo and reload the browser page to see your changes. - NOTE: If you are working on the latest version of any docs, you will need to suffix the docs name in url with
/next/
to see your changes. For example, if you are working oncommunity
docs and made changes to theintroduction
page, then you will need to visit:http://localhost:9001/docs/community/next/introduction
instead ofhttp://localhost:9001/docs/community/introduction
to see your changes. This only applies to docs that have versioning (see the top left of the page. If you see a version number, then this applies) - To build docs for all the folders run
./buildAllDocs
from the root of the repo.
- For other cosmetic modifications, bugs etc please create an issue on github