Tools overview
The tools/ folder in this repo is the main content hub for tool documentation. Each file describes one platform, product, or self-hosted service in the Pacing stack. Tools are organised by category with cost tracking, renewal dates, and access information.
📦 Tool Stack Overview
Quick Reference​
Each category page includes:
- Summary table with total costs and tool count
- Tool list with monthly/annual costs, account types, and login links
- Upcoming renewals for that category
For automation scripts, exports, and backups attached to a tool, check the matching folder under scripts/resources/<tool-name>/ (for example, scripts/resources/webflow/, scripts/resources/twilio/, scripts/resources/n8n/).
FAQs
How do I add documentation for a new tool?
Create a new Markdown file in the tools/ directory with the tool name (e.g., tools/newtool.md). The file will automatically sync to the Docusaurus site on the next build. Make sure to include a clear H1 heading at the top for the title.
Where do I find automation scripts and resource files for a tool?
Automation scripts, exports, and backups are stored in scripts/resources/ followed by the tool name. For example, Webflow resources are in scripts/resources/webflow/, and n8n workflows are in scripts/resources/n8n/.
Can I edit the generated tool documentation pages in Docusaurus?
No. The files in docusaurus/docs/tools/ are auto-generated from the source files in tools/. Always edit the source files in tools/ - your changes will be overwritten if you edit the generated files directly.
What information should I include in a tool documentation file?
Include the tool's purpose, account details (IDs, URLs, owners), key features, integration points with other tools, and any automation workflows. See existing tool files like tools/webflow.md or tools/gtm.md for examples of the expected format.