|
|
||
|---|---|---|
| .github | ||
| .well-known | ||
| docs | ||
| includes | ||
| mkdocs-material@2b4e34c0dc | ||
| theme | ||
| .allowed_signers | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .markdownlint.yml | ||
| CITATION.cff | ||
| crowdin.yml | ||
| LICENSE | ||
| mkdocs.production.yml | ||
| mkdocs.yml | ||
| Pipfile | ||
| Pipfile.lock | ||
| README.md | ||
Your central privacy and security resource to protect yourself online.
About
Privacy Guides is a socially motivated website that provides information for protecting your data security and privacy. We are a non-profit collective operated entirely by volunteer team members and contributors.
Our current list of team members can be found here. Additionally, many people have made contributions to the project, and you can too!
Contributing
- 💬 Start a discussion or suggest an idea
- 💖 Sponsor the project
- 🈴 Help translate the site [Matrix chat]
- 📝 Edit the site, everything's accessible in this repo
- Browse our open issues to see what needs to be updated
- View some contribution tips on our contributor's wiki
Blog
We aspire to publish the best articles about privacy on the net. From hot-takes to long-form essays, we are looking for stylish and well-written pieces.
This not a place for sponsored content or SEO-obsessed posts. Please do not pitch us this, as we don't take kindly to it and your email will be blocked. Caveat scriptor.
Submit stories or requests to: freddy@privacyguides.org
Mirrors
Developing
Committing to this repository requires signing your commits (git config commit.gpgsign true) unless you are making edits via the GitHub.com text editor interface. As of August 2022 the preferred signing method is SSH commit signatures, but GPG signing is also acceptable. You should add your signing key to your GitHub profile.
This website uses mkdocs-material-insiders which offers additional functionality over the open-source mkdocs-material project. For obvious reasons we cannot distribute access to the insiders repository. You can install the website locally with the open-source version of mkdocs-material:
- Clone this repository:
git clone https://github.com/privacyguides/privacyguides.org.git(thencd privacyguides.org)git submodule initgit submodule update docs/assets/brandgit config gpg.ssh.allowedSignersFile .allowed_signers
- Install Python 3.6+
- Install dependencies:
pip install mkdocs mkdocs-material mkdocs-static-i18n typing-extensions - Serve the site locally:
mkdocs serve- The site will be available at
http://localhost:8000 - You can build the site locally with
mkdocs build - Your local version of the site may be missing functionality, which is expected. If you are submitting a PR, please ensure the automatic preview generated for your PR looks correct, as that site will be built with the production insiders build.
- The site will be available at
Team members should clone the repository with mkdocs-material-insiders directly. This method is identical to production:
- Clone this repository and submodules:
git clone --recurse-submodules https://github.com/privacyguides/privacyguides.org.git - Enable SSH commit verification with our local
.allowed_signersfile:git config gpg.ssh.allowedSignersFile .allowed_signers - Install Python 3.7
- Install pipenv:
pip install pipenv - Install dependencies:
pipenv install --dev - Serve the site locally:
pipenv run mkdocs serve --config-file mkdocs.production.yml- The site will be available at
http://localhost:8000 - You can build the site locally with
pipenv run mkdocs build - This version of the site should be identical to the live, production version
- The site will be available at
If you commit to main with commits signed with your SSH key, you should add your SSH key to .allowed_signers in this repo.
Releasing
- Create a new tag:
git tag -s v2.X.X -m 'Some message'- View existing tags
- Tag numbering: Increment the MINOR (2nd) number when making significant changes (adding/deleting pages, etc.), increment the PATCH (3rd) number when making minor changes (typos, bug fixes). Probably leave the MAJOR number at 2 until a massive revamp (v1 -> v2 was the Jekyll to MkDocs transition).
- Push the tag to GitHub:
git push --tags - Create a new release selecting the new tag
- Title the release the same as the tag version number, i.e.
v2.X.X- For more significant releases, add a short title, for example v2.3.0 - Localization Support or v2.2.0 - Removing Social Networks
- GitHub should let you auto-generate release notes based on PR titles
- Mark more significant changes in bold, see v2.12.0 for example
- Title the release the same as the tag version number, i.e.
- Publish release, it will be deployed to the live site automatically
- When publishing more significant releases (generally any with a MINOR version increment) check the "Create a discussion for this release" box to post an announcement