- Conceptual information for company, contact, diary, document, project, quote, request, and sale was scattered throughout the five repos.
- Common settings (cspell), templates, and reusable text chunks were duplicated in each repo.
- We had to manage dependencies between repos. If you moved or renamed a file in repo A, you also had to make changes in the other repos to avoid broken links - which meant multiple branches and pull requests that had to be coordinated.
- We lost Git history when we moved content from one repo to another.
- The backlog was fragmented. We had to create an umbrella project and board to track and prioritize all issues in one location.
- The tools and build pipeline had to be aware of all repos and juggle Git submodules. It also added complexity for those who wanted to build the whole site locally.
- Grouped how-tos.
- Grouped all downloadable files.
- Got rid of most duplicates.
- Moved all whats-new pages to superoffice-docs/release-notes/.
- Updated all links.
- Updated table-of-contents files (toc.yml).
- Renamed and moved physical folders to match the output URLs.
- Created a new build file, which turned out to be a third of the old one.
- crmscript to superoffice-docs/docs/automation/crmscript/
- database to superoffice-docs/docs/database/
- data-access to superoffice-docs/docs/api/
- user-interface to superoffice-docs/docs/ui/
- CRMScript: automation/crmscript/reference/index.html
- Trigger scripts: automation/trigger/reference/index.html
- Webhooks: automation/webhook/reference/index.html
- bLogic screen elements: ui/blogic/reference/index.html