What is planned
Where Trama stands today, the work that is scheduled next, and the things it is deliberately not going to do.
Where it stands
Spaces, an ordered page tree that stays where you put it, backlinks and the stub list all work.
Current work is about a wiki being useful to a reader who is not the person who wrote it — terminology, publishing, and the ceiling on what a page can contain.
Planned work
What is being built
Grouped by theme and ordered by intent. These are horizons, not dates — nothing on this page is a delivery commitment, and the order can change when a customer gives us a reason to change it.
-
In progress
A vocabulary a reader can rely on
Most internal documentation fails newcomers on terminology rather than structure. This group lets a space hold its own definitions and have them explain themselves wherever the term appears — company-wide underneath, space-specific on top, and never leaking a term out of a space the reader cannot open.
- A glossary page: how a space declares that it holds the terms
- A layered dictionary, company beneath and space above, permission-aware
- Acronyms defined once and expanded everywhere they are used
- A marker in the reader that leaves the underlying document untouched
- Clicking a term to reach its definition, without breaking selection or middle-click
-
In progress
Publishing, and taking it back
A page shared outside the company needs to be listable and revocable. Neither is true today: nothing lists what a company has published, and a link outlives the reason it was created.
- A list of everything a company has published
- Revoking a published link after the fact
-
Next
Raising the Markdown ceiling
Trama supports a deliberately bounded subset of Markdown. The bound was the right call early and is now the thing people hit — a page that renders correctly elsewhere loses content here, and the round trip through export must not quietly drop what it cannot represent.
- A wider Markdown subset, with the boundary documented
- Syntax highlighting for fenced blocks that already declare a language
- Ordered lists that start where the author said they start
- Export and re-import proven to round-trip without loss
Out of scope
Not on the roadmap
Said plainly, because the alternative is a sales conversation that ends in disappointment. If one of these is the thing you need, Trama is not the product for it.
-
Real-time multi-author editing
Trama is a wiki, not a shared canvas. Pages are edited and saved, not co-typed.
-
Being a file store
Attachments support pages. Trama is not a place to keep the company’s documents.
How this is maintained
Every item above corresponds to work tracked in our own issue tracker, and this page is rewritten from that tracker rather than kept by hand. What is not shown: unfixed defects and security work, which belong in the tracker until they are closed, not on a product page.
Want the detail behind a line on this page, or a view of where something sits? Write to dmoore@dwmmholdings.com and ask.
Next
Bring Trama into your company
Ask about onboarding an organisation, migrating existing records, or a demonstration.