docs: lead with Taskade's story (demote n8n, add ToC) - #41
Conversation
- Drop n8n from the headline tagline (n8n is a converging competitor in automations/Genesis); feature VS Code instead. - Remove the dedicated 'n8n Automation Integration' section and its dead ./N8N_WORKFLOW_GUIDE.md link (the 'connect Taskade to 400+ apps via n8n' framing positioned Taskade as a spoke of a competitor's hub). - De-brand the HTTP/SSE section header from 'for n8n' to 'remote & custom clients'. - Add a Table of Contents (444-line README) for navigation + anchor SEO. n8n compatibility is unchanged (examples/n8n-taskade-mcp-workflow.json kept; HTTP mode still works for any HTTP MCP client) — this is editorial positioning only. Note: glama.json was NOT enriched — its schema only permits 'maintainers'.
|
There was a problem hiding this comment.
Pull request overview
This PR updates the repository README to reposition Taskade as the primary orchestrator (removing competitor-centric framing), improve navigation with a Table of Contents, and eliminate a previously broken n8n guide link—without changing any runtime behavior or compatibility.
Changes:
- Updated the top tagline to remove
n8nand includeVS Codeas an example client. - Added a README Table of Contents for easier navigation across major sections.
- De-branded the HTTP/SSE mode heading and removed the n8n-specific integration section (including the dead
N8N_WORKFLOW_GUIDE.mdlink).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
✅ Validation & QA — ready to mergeCopilot reviewed with no inline comments. Re-validated:
Markdown only. Confidence: high · zero regression. Merging. |
What & why
The README promoted a converging competitor (n8n) and cast Taskade as a spoke of n8n's hub ("Connect Taskade to 400+ apps via n8n"), while also linking a dead
N8N_WORKFLOW_GUIDE.md. This reframes the README around Taskade as the orchestrator.Changes
n8n, featureVS Codeinstead.### n8n Automation Integrationsection + its dead guide link (also fixes the broken link — by deletion).### 4. HTTP / SSE Mode (for n8n…)→(remote & custom clients).Zero-regression
examples/n8n-taskade-mcp-workflow.jsonstays, and HTTP mode still serves any HTTP MCP client. This is editorial positioning, not a capability change.n8nreferences remain in README; 0N8N_WORKFLOW_GUIDElinks; all 11 ToC anchors resolve to real##headers.glama.ai/mcp/schemas/server.json) permits onlymaintainers; adding description/tags would be schema-invalid.Stacked on
mainwhen fix: reconcile advertised tool count to 57 #40 merges.