status-im
/
help.status.im
mirror of https://github.com/status-im/help.status.im.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
LEGACY Status apps user documentation https://help.status.im
716 Commits 56 Branches 13 Tags 37 MiB
CSS 57.4%
HTML 23.2%
Dockerfile 19.4%
Go to file
Fabiomorais87 a14f54752c Update your-profile-and-preferences 2023-07-25 07:00:47 -03:00
.github/ISSUE_TEMPLATE ci: add Jenkinsfile, requirements.txt and redirect 2022-04-22 07:34:13 +02:00
config/en fix incorrect mkdocs.yml config file - replace ':' with '-' 2023-07-21 09:17:44 +02:00
docs/en fixing hyperlinks, article names, index and etc 2023-07-16 22:07:10 -03:00
includes Update your-profile-and-preferences 2023-07-25 07:00:47 -03:00
overrides Create leave-a-status-community.md 2023-06-21 21:29:52 +08:00
tooltips/en 443 keycard tooltip for mobile app 2023-02-20 17:04:12 +01:00
.gitignore 440 update .gitignore and delete .vscode folder 2023-02-17 15:24:25 +01:00
CONTRIBUTING.md remove style guide content and config from help.status.im repo 2022-11-30 16:38:49 +01:00
Dockerfile ci: install ghp-import via pip instead of apk 2022-07-28 14:31:03 +02:00
Jenkinsfile remove style guide content and config from help.status.im repo 2022-11-30 16:38:49 +01:00
LICENSE Initial commit 2022-03-17 11:47:53 +01:00
README.md Change Help and Style Guide colors and other minor changes 2022-07-22 16:19:48 +02:00
requirements.txt 492 add pytz module to requirements.txt 2023-03-03 10:00:13 +01:00

README.md

Status apps user documentation

Status Help illustration

This repository contains the documentation website code and Markdown files for help.status.im.

We use Material for MkDocs to build the user documentation site.

Repository branches and git workflow

This repository uses a simplified version of the Gitflow git branching model from Vicent Driessen:

  • The master branch stores the official release history, and the develop branch serves as an integration branch for new content or fixes.
  • The develop branch contains the complete history of the documentation project, whereas the master branch contains an abridged version.
  • Each new content should reside in its own topic branch. Topic branches use develop as their parent branch.
  • New content and fixes become part of the develop branch via pull request collaboration. When a feature is complete, it gets merged back into develop.
  • Once develop has acquired enough content for a release, we merge the develop branch into master.

Contributing

See the contributing guide for detailed instructions on collaborating with our project.

On every article in the Status user documentation, you can click the edit Edit button button to open a pull request for quick fixes like typos, updates, or link fixes.

For more complex contributions, you can open an issue using the most appropriate issue template to describe the changes you'd like to see.

If you're looking for a way to contribute, you can scan through our existing issues for something to work on. When ready, check our contributing guide for detailed instructions.

Continuous integration

We build two branches using our Jenkins instance:

The Status' Docs team adds new content and fixes to the develop branch and periodically merges updates into the master branch. When merging changes, we rebase on the develop branch. You can keep track of the documentation updates on the releases page.

License

The Status user documentation is licensed under the MIT license. The Material for MkDocs components of our documentation are licensed under the Material for MkDocs license.