Better to know now than to find out after writing forty pages.
Everything published is public#
There is no private, password-protected or team-only site. Publishing sets your Drive folder to "anyone with the link" and a site with two or more pages is indexable by search engines.
Do not publish an internal handbook, runbooks, customer data, or anything under NDA. Access control is the next major thing being built.
Your own domain#
Sites live at markloom.app/u/<handle>/<collection>. Serving them from
docs.yourcompany.com is designed and being built, but is not available
today.
One level of pages#
The published folder is flat. Subfolders are ignored — their files do not
become pages. _assets is the exception, and only for images.
Publishing is Google Drive only#
You can edit files in a GitHub repository, but publishing a collection currently requires Drive. GitHub publishing is planned.
Handles cannot be changed#
You choose a handle once. Changing it later would break every URL you had published, so it is fixed for now. Choose carefully.
One person per account#
There are no teams, shared ownership or roles. A collection belongs to the account that published it. Two people cannot edit the same document at the same time — Markloom will spot the conflict and ask, rather than silently overwriting, but it will not merge for you.
No analytics for publishers#
You cannot see how many people read your pages. This is a deliberate trade against the privacy story, and it may change if publishers ask.
Files, not a database#
There is no tagging across pages, no collections of collections, no scheduled publishing and no drafts workflow beyond keeping a file out of the folder until it is ready.
If one of these is blocking you, say so — what people are actually stopped by decides what gets built next.