Forums Feature Requests Thread

[New] mobieusKnow: No internal wiki-links or backlinks (related pages are tag-derived only)

Patrick Bass · Jun 6 · 10 · 0
[Normal Priority] [New Feature] [Under Consideration]
🚀 OP Jun 6, 2026 6:11pm

Area: mobieusKnow (audit p6) · Surface: /know/{slug} · Dimension: competitor-gap · Severity: minor

Confluence, Notion, Slab, and MediaWiki make internal linking and backlinks ('what links here' / 'mentioned in') central to KB navigation and knowledge graph building. mobieusKnow's only relationship signal is shared tags, which is coarse and noisy. First-class internal links ([[Page Title]] or a link picker) plus a backlinks panel ('Pages that link here') would create real navigational structure between articles, help authors discover orphan pages, and improve the AI retrieval graph. The post-mention card pattern already in MarkdownService is a proven template for rendering resolved internal references with a write-time snapshot.

Evidence

'Related pages' is computed purely from shared tags: show() takes the page's first 3 tags and does `tags LIKE :t` lookups (KnowledgeController.php:82-91). MarkdownService has no [[Page]] / wiki-link handling — it adds post-mentions (@post:N) and gallery embeds (MarkdownService.php:149-305) but no page-to-page linking syntax; a grep for '[[' in MarkdownService.php and KnowledgeController.php finds nothing. There is no 'what links here' / backlinks query anywhere in the Know model or controller.

Suggested fix. Add a [[slug-or-title]] internal-link syntax resolved in MarkdownService (mirroring the @post:N card pattern), persist link edges in a knowledge_links table on save, and render a 'Linked from' backlinks panel on show.php plus an 'orphan pages' surface for moderators.

Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.


Patrick Bass
@mobieus

Log in or register to reply to this thread.