Update help site documentation for 2025-2026 features

[Copilot]

Help Site Accuracy Review - COMPLETE ✅

Review Completed

• Explore repository structure and understand documentation organization
• Review English source documentation files (14 .md/.mdx files)
• Research current web-xforge features and recent updates (2025-2026)
• Compare help documentation against actual Scripture Forge features
• Review all documentation files for accuracy
• Address all reviewer feedback

Changes Made

• FAQ Update: Added information about new 2025-2026 features

  • Reordered draft notification information to prioritize email notifications over manual page checking
  • Fixed FAQ numbering by adding blank line after question 3
  • Access to previously generated drafts (Question Fix/community checking missing translations #6)
  • Viewing all community checking answers without answering (Community Checking section)
  • CSV export for community checking questions (Community Checking section)

• Community Checking: Documented new permissions and export features

  • View all community answers permission
  • CSV export capability

Documentation Verified as Accurate

• Draft generation process and timing (3 hours estimate still valid)
• Onboarding workflow through registration form
• Paratext integration and syncing procedures
• Translation suggestions feature documentation
• Community checking workflow and permissions
• All external links and feature references

Testing & Validation

• Build documentation site successfully for all 6 locales
• Verified FAQ numbering renders correctly in markdown
• All changes to English source files only

Summary

All English documentation has been reviewed and updated to reflect current Scripture Forge features as of January 2026. All reviewer feedback addressed: FAQ numbering fixed and draft notification information reordered to prioritize email notifications.

Original prompt

Scripture Forge help is the help site for the web-xforge repo. In general, it needs to keep up with changes in web-xforge. Changes should only be made to the English files, which then have a process by which they are localized. Please review the contents of the help site and verify its accuracy, and propose any needed changes.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Nateowami]

@copilot - I don't think the sync with paratext addition to the getting started page is helpful

• I think it would be more helpful to add the information about draft completion notifications to the "How will I know when my draft is done?" question

[Copilot]

@copilot - I don't think the sync with paratext addition to the getting started page is helpful

• I think it would be more helpful to add the information about draft completion notifications to the "H...

Done! Removed the syncing link from the getting started page and added the draft notification information to the "How will I know when my draft is done?" question in the FAQ instead. (605e900)

[Nateowami]

@copilot The numbering in docs/faq.md is wrong.

Also, I think it makes more sense for the information about draft notifications to come before suggesting constantly refreshing the page. In fact, that entire FAQ item could probably be rewritten.

[Copilot]

@copilot The numbering in docs/faq.md is wrong.

Also, I think it makes more sense for the information about draft notifications to come before suggesting constantly refreshing the page. In fact, ...

Fixed both issues:

1. Added blank line after question 3 to fix markdown list numbering
2. Reordered question 2 to prioritize email notifications before manual page checking

The FAQ now suggests email notifications first, with checking the page as the alternative method. (2b586e1)