Product Decisions This Supports
- Build vs. buy for knowledge-base features: A v1.0.0 with wiki-link syntax, automatic backlinks, and missing-link detection covers the core of a "personal wiki"/internal docs experience (Notion, Obsidian, Roam-style linking). This lets you evaluate buying/integrating rather than building link-graph logic, index rebuild tooling, and UI components in-house.
- Roadmap sequencing: The feature set maps cleanly to a phased roadmap — (1) linking syntax and rendering, (2) backlink index and sidebar, (3) missing-link detection plus page creation from links, (4) discovery surfaces like the dashboard widget. You can ship phases incrementally using the same package.
- Content architecture decisions: Configurable collections, fields, and CSS classes means the content model (what counts as a "page," which fields are linkable) is a product/config decision, not a code fork. That supports decisions about content taxonomy and how many content types get wiki behavior.
- Scope validation for internal tooling: Backlinks and missing-link detection are the highest-signal features for content discoverability. The dashboard widget gives a proxy metric (backlink activity) that supports decisions about whether to invest further in knowledge management or documentation tooling.
- Use-case fit assessment: Strong for internal wikis, documentation hubs, team knowledge bases, and help-center content where entries are cross-referenced. The
backlinks:rebuild command signals operational maturity — useful when deciding whether this can run in production without dedicated ops effort.
- Migration/replatform decisions: If you're considering Statamic (Antlers tags/modifiers indicate a Statamic addon), this package reduces the custom-code delta versus an incumbent wiki tool, which is a factor in replatform cost estimates.
When to Consider This Package
Adopt when:
- Your product or internal tooling includes cross-referenced content (docs, wiki pages, knowledge entries) and users currently link manually or not at all.
- You're on a Laravel/Statamic stack and want wiki-link behavior without building a link parser, backlink index, and UI yourself.
- You need missing-link detection and click-to-create as a content-authoring workflow — this is the differentiator that reduces friction for non-technical authors.
- You want configurable behavior (collections, fields, CSS classes) so design/content teams can adapt it without engineering work.
- You can tolerate a v1.0.0 dependency: the presence of a rebuild command is a plus, but it's early-stage.
Look elsewhere or build when:
- You need multi-tenant or permission-aware link graphs, versioned content links, or analytics-grade link metrics — none of that is indicated here.
- You're not on Statamic; the Antlers tag and modifier tie the rendering layer to that ecosystem, so portability is limited.
- You need real-time collaborative editing or rich block-based authoring — this is linking, not editing.
- Your content volume requires search-backed link resolution at scale; a v1.0.0 index with a manual rebuild command implies you should validate performance and index freshness before committing.
- You require a stable, long-supported API with deprecation guarantees — a 1.0.0 release with no prior assessment history is a risk to price in.
Open questions to resolve before adoption: backlink index storage and refresh strategy (on-save vs. rebuild-only), behavior when entries are renamed or deleted (orphaned backlinks), and whether missing-link page creation respects permissions and publishing workflow.
How to Pitch It (Stakeholders)
To executives: This package gives us wiki-style linking and automatic backlinks in our Laravel/Statamic content system — the feature set users expect from modern documentation tools — without a custom build. It covers the full loop: authors write [[Page Title]], the system tracks backlinks, flags links to pages that don't exist yet, and lets authors create them in one click. That's a measurable reduction in authoring friction and a direct improvement to content discoverability, delivered as configuration rather than bespoke engineering.
To engineering: It's a v1.0.0 addon providing a link parser and renderer (wiki_links modifier), an Antlers backlinks tag, an automatic backlink index with a backlinks:rebuild command, an entry sidebar, a dashboard widget, and configurable collections/fields/CSS classes. Integration is additive and config-driven — no schema forks. Key diligence items: index refresh semantics, rename/delete handling, and performance at our content volume. Recommend a time-boxed pilot on one collection before wider rollout.