Integrations
Works with the stack you already run on.
ilumd isn’t another place to put docs. It reads the Markdown you already keep in your repos, governs who sees what, and writes back into the tools your teams live in — issues, wikis, trackers and Slack.
Sources
Your docs stay where they are.
ilumd reads the Markdown you already keep in your repositories. Nothing moves, nothing to migrate — every portal is a live view of the source.
GitHub
Point ilumd at your org — it finds every Markdown doc across every repo and keeps each portal current with the code.
GitLab
The same governed, always-current docs, sourced straight from the GitLab repositories you already work in.
Publish & write-back
Governed docs, in the tools your teams use.
Publish an always-current doc into the surfaces people already open, and let a reader's request for an update land as an issue in the system you deliver from.
Notion
Publish a governed doc into a Notion page and keep it in sync with the source — no copy-paste, no drift.
Confluence
Push always-current docs into Confluence spaces without the copy-paste drift that stales a wiki within a week.
GitHub Issues
Turn a reader's “request an update” into a GitHub issue on the source repo, linked back to the exact doc.
GitLab Issues
Raise update requests and change suggestions as GitLab issues, so doc work lands in your normal backlog.
Jira
File doc change-requests and provenance straight into the right Jira project — the same trail your delivery already runs on.
Linear
Route documentation work into Linear so it shows up in the team's cycle instead of a forgotten inbox.
Notifications
The right people hear about a change.
When a doc moves or a portal ships, ilumd tells the channel that needs to know — no one has to go looking.
Slack
Ping the right channel when a doc changes, a client portal is published, or a reader asks for an update.
Don’t see yours?
We’re building the write-back integrations agencies ask for first. Tell us which tool your clients live in and we’ll weigh it up front.