Erik Moeller

@joaedwar Good candidate issue for you to work on, as well.

Per @zenmonkeykstop's point above, I do think it's worth auditing the docs to make sure we're consistently instructing users to `cd` into the right directory before running the command(s). Retitled...

I can't speak for Harlo but IMO we should still flesh out the "Onboard Journalists" section a bit to clarify before calling this done (maybe a single paragraph will suffice),...

See the related #86 (multiple SVS) and #63 (more efficient journalist provisioning); there's likely potential for consolidating certain recommendations for provisioning multiple Tails drives.

I agree that the "Installation" section currently has wider scope than a typical software installation - but note that we also already have a "Deployment Best Practices" section (mapped to...

> @eloquence is there any plan in place for the reorganization of the doc? Not really, but @gonzalo-bulnes has started some work in #141 to reorganize a section of the...

This is still a valid proposal; we should re-evaluate the information architecture of the install guide. Divio's [documentation system](https://documentation.divio.com/) offers some useful pointers for how explanatory content can be set...

Should every point release be considered a hotfix release? Historically we've sometimes issued point releases with several changes batched up, e.g., https://securedrop.org/news/securedrop-121-released/, where the branch logic described here may not...

To add a bit more context, the restore docs currently [say](https://docs.securedrop.org/en/stable/backup_and_restore.html): > This documentation applies to a SecureDrop instance using v2 onion services. If your instance uses v3 onion services,...

(Removed from board as #133, which is expected to fully resolve, is tracked there.)