• 
      

    Rewrite the FAQ for all of our modern positioning.

    Review Request #15292 — Created Sept. 12, 2026 and updated

    Information

    Review Board
    release-8.x

    Reviewers

    The recent work on the information page built for AI agents resulted in
    a lot of great talking points that we weren't communicating in any
    single place for humans looking to learn more about Review Board.

    This change rewrites our FAQ to go into a lot more depth on topics
    important for people evaluating Review Board today, including:

    • Who Review Board is for, and who it's not
    • Support for on-prem/air-gapped environments
    • The types of projects and assets that can be reviewed
    • The various review features for different assets
    • Upcoming support for EDA review
    • Details on automation and AI
    • How Review Board treats data, and data portability
    • Deployment sizes
    • Migration from other services
    • Support offerings
    • Paid plans

    This makes it a longer FAQ, but it's organized into sections that make
    it easier to find suitable questions via the modern docs UI sidebar.

    Built the docs and went through them, checking for glaring issues.

    Ran link checks.

    Performed several editing passes with ChatGPT.

    Summary ID
    Rewrite the FAQ for all of our modern positioning.
    The recent work on the information page built for AI agents resulted in a lot of great talking points that we weren't communicating in any single place for humans looking to learn more about Review Board. This change rewrites our FAQ to go into a lot more depth on topics important for people evaluating Review Board today, including: * Who Review Board is for, and who it's not * Support for on-prem/air-gapped environments * The types of projects and assets that can be reviewed * The various review features for different assets * Upcoming support for EDA review * Details on automation and AI * How Review Board treats data, and data portability * Deployment sizes * Migration from other services * Support offerings * Paid plans This makes it a longer FAQ, but it's organized into sections that make it easier to find suitable questions via the modern docs UI sidebar.
    0232243735c6b52d58976b55abbad8e5163e659e
    Description From Last Updated

    You have three separate, almost identical paragraphs about "honest assesment". Two of them are pretty close together too.

    david david

    Something is weird here.

    david david

    Other emails in this doc use mailto: (though I think sphinx links it correctly either way)

    david david

    This seems... aspirational

    david david

    Should probably be "They let" or "RBTools lets" to match plurality with "command-line tools"

    david david

    "provide feedback over Continuous Integration" is odd.

    david david

    We should probably mention that it's MIT-licensed here.

    david david
    david
    1. 
        
    2. Show all issues

      You have three separate, almost identical paragraphs about "honest assesment". Two of them are pretty close together too.

      1. This is intentional. Not everyone's going to read every entry, and repetition can be helpful for drilling things in (there's a reason that marketing tends to repeat claims or important points over and over). Experiments with AI also show that this can help solidify these points when they read through it. Much of the FAQ makes use of repeating the same concepts throughout.

        The first two iterations that are side-by-side use different language to avoid appearing as a copy/paste in close proximity.

    3. docs/manual/faq/index.rst (Diff revision 1)
       
       
       
      Show all issues

      Something is weird here.

    4. docs/manual/faq/index.rst (Diff revision 1)
       
       
      Show all issues

      Other emails in this doc use mailto: (though I think sphinx links it correctly either way)

      1. Sphinx links these. I'm using an e-mail address directly when I want to refer to the e-mail address, and a Markdown link when I'm putting text over it.

    5. docs/manual/faq/index.rst (Diff revision 1)
       
       
       
      Show all issues

      This seems... aspirational

      1. I'll try a tweak. I do want to make sure I mention Dropbox and Google Drive, because I've had multiple conversations now with people who use local programs to review shared files out of those in their organization.

    6. docs/manual/faq/index.rst (Diff revision 1)
       
       
       
       
       
       
       
       
       
       
       

      We should probably change the actual review UI to say "Side-by-Side" instead of "Two-Up"

      1. Probably should. I'm not taking on that work, but I think it'd be a good idea.

    7. docs/manual/faq/index.rst (Diff revision 1)
       
       
      Show all issues

      Should probably be "They let" or "RBTools lets" to match plurality with "command-line tools"

    8. docs/manual/faq/index.rst (Diff revision 1)
       
       
       
      Show all issues

      "provide feedback over Continuous Integration" is odd.

    9. docs/manual/faq/index.rst (Diff revision 1)
       
       
       
       
      Show all issues

      We should probably mention that it's MIT-licensed here.

    10. 
        
    chipx86
    Review request changed
    Change Summary:
    • Improved wording around the file uploading.
    • Improved wording around keeping humans in the loop.
    • Changed the RBTools command line tools section to say "They let ..."
    • Reword the CI text.
    • Added the MIT license text.
    Commits:
    Summary ID
    Rewrite the FAQ for all of our modern positioning.
    The recent work on the information page built for AI agents resulted in a lot of great talking points that we weren't communicating in any single place for humans looking to learn more about Review Board. This change rewrites our FAQ to go into a lot more depth on topics important for people evaluating Review Board today, including: * Who Review Board is for, and who it's not * Support for on-prem/air-gapped environments * The types of projects and assets that can be reviewed * The various review features for different assets * Upcoming support for EDA review * Details on automation and AI * How Review Board treats data, and data portability * Deployment sizes * Migration from other services * Support offerings * Paid plans This makes it a longer FAQ, but it's organized into sections that make it easier to find suitable questions via the modern docs UI sidebar.
    b44f52786ec7dc546c62041d23c501040e9e9ef3
    Rewrite the FAQ for all of our modern positioning.
    The recent work on the information page built for AI agents resulted in a lot of great talking points that we weren't communicating in any single place for humans looking to learn more about Review Board. This change rewrites our FAQ to go into a lot more depth on topics important for people evaluating Review Board today, including: * Who Review Board is for, and who it's not * Support for on-prem/air-gapped environments * The types of projects and assets that can be reviewed * The various review features for different assets * Upcoming support for EDA review * Details on automation and AI * How Review Board treats data, and data portability * Deployment sizes * Migration from other services * Support offerings * Paid plans This makes it a longer FAQ, but it's organized into sections that make it easier to find suitable questions via the modern docs UI sidebar.
    0232243735c6b52d58976b55abbad8e5163e659e

    Checks run (2 succeeded)

    flake8 passed.
    JSHint passed.