Skip to content

docs: how to write secureblue FAQ section #362

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Commenter25 wants to merge 2 commits into
base: live
Choose a base branch
from
Open

docs: how to write secureblue FAQ section #362

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1642cdc
docs: how to write secureblue FAQ section
Commenter25 May 2, 2026
784e660
un-incorrectmaxxing
Commenter25 May 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions content/FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ permalink: /faq
- [Another security project has a feature that's missing in secureblue, can you add it?](#feature-request)
- [How do I get notified of new releases?](#releases)
- [What do the GitHub releases involve?](#release-content)
- [How do you write the project name?](#secureblue-stylization)

- [System information](#system)
- [Why is Flatpak included? Should I use Flatpak?](#flatpak)
Expand Down Expand Up @@ -147,6 +148,11 @@ If you prefer to use an Atom feed, supported by many RSS clients, you can use th

Substantial testing for new changes is done in the `staging` and `next` branches. However, once a commit is merged into `live`, a new set of builds is immediately generated and deployed. As such, the GitHub releases are an informational measure to track progress and communicate changes to users. This is only the case for the secureblue main repo, it isn't the case for Trivalent. For Trivalent, GitHub releases correspond to RPM releases to the RPM repo.

### [How do you write the project name?](#secureblue-stylization)
{: #secureblue-stylization}

secureblue should always be written as one lowercase word, even at the beginning of sentences. If it is absolutely mandatory, such as when title casing is strictly enforced, "Secureblue" is acceptable. It would be incorrect to write it in mixed case like "SecureBlue" or as separate words like "secure blue".

<hr>

## [System information](#system)
Expand Down