Add Glossary

[ninavizz]

• This should be thee top item in left-nav TOC.
  • Numero Uno. First. Most Important. :D
• Ideally could exist as one page, with content possibly shown in an Accordion—If RTD supports an Accordion interaction pattern.
  • This and that and this are examples of Accordion (or “Drawer”) interaction pattern.
  • An accordion may not be appropriate for a Glossary, if most definitions are contained to 1-2 sentences. For an FAQ, it feels more urgent.

Qubes

Not shown in alphabetical order—just things that came to mind, when thinking of terms I often hear used that could be helpful to define for Journos and Admins.

• VM
• Whonix
• Q-Menu
• Attachment Widget
• Qube Manager
• dom0
• (printer menu window, as its branding identifies it—tho this FAQ would speak to CUPS)
• Updater
• GPG Key
• RPC
  • From TechTerms.com: "Stands for 'Remote Procedure Call.' Most computer programs run procedures, or sets of instructions, using the computer's CPU. In other words, the instructions are processed locally on the same computer that the software is running from. Remote procedure calls, however, run procedures on other machines or devices connected to a network. Once the instructions have been run, the results of the procedure are usually returned to the local computer." Because Qubes is an operating system that exists as a bunch of virtual machines, RPCs are how many of its core functions happen. On a regular computer, they would simply happen as standard application calls.
• QSec

SecureDrop

A 1-2 sentence intro to the SD app on the Workstation. Link to general SD terms in regular SD Docs, would be included in this sentence.
(the below answers provide brief 1-2 sentence explanations about what each of the below items are—so that when a user reads about them in FAQs or long-form guide text, they can clearly know what's being talked about)

• Conversation Pane
• Sources List
• Bar Messaging
• Contextual Messaging
• Export
• Print
• Connection Widget
• Preflight Updater
• Login Window

[rocodes]

I'm happy to get started on this, but maybe we can finalize which terms are going to be in the public-facing docs/UI/communications.

cc @zenmonkeykstop