On Page Navigation
On Page Navigation
Documentation that lives on your own site, with a full record of who changed what and a review step before an edit goes live. We design the space structure, move what you already have, repair what breaks in transit, and run it after launch.
What Managed Frappe Wiki Covers
Installing Wiki takes an afternoon. The work is deciding the space and group structure before any content moves, because Wiki v2 organises pages two levels deep and a deeper hierarchy gets flattened on the way in. Where the material is something a person has to complete rather than look up, the learning platform we manage is the better home for it.
So the first pass is an inventory of what you already have and an honest decision about what is worth keeping. Most documentation migrations fail because everything gets moved, including the pages nobody has opened in three years, and the result is a search that returns noise. We agree the structure first, move what earns its place, set permissions by team, and put a review date on the pages that go stale fastest. What arrives is smaller than what you started with, and people use it.
A space is a self-contained wiki with its own route, sidebar and landing page. Customer documentation and an internal handbook belong in different spaces, because they have different readers and different rules about who may open them. We settle this before content moves. Splitting a space afterwards means re-routing every page inside it.
Frappe's own migration guide is blunt: every Wiki Group comes out un-nested on the other side, however deeply you had nested it. Two quieter traps sit next to that one. Sidebars sharing a name have all their children merged under a single group, and an empty sidebar title stops the run. We audit for all three before anything moves.
An edit from someone without publishing rights becomes a patch waiting for review rather than a live change. What is worth knowing before you design the workflow is that the people who can publish directly are the ones holding System Manager, which is administrative control of the entire site rather than a documentation permission. We keep that list short and put the wiki somewhere a short list is workable.
Wiki permits guest reading until the Disable guest access setting is turned on. That is correct for public product documentation and wrong for a staff handbook. We set it during the build and check it again after every upgrade, because it is the one setting most likely to quietly put something internal on the open web.
Wiki search runs on RediSearch, and the setting that shows the search bar is a different setting from the one that uses RediSearch to answer the query. Enable only the first and you have shipped a search box that disappoints people. We configure both and test against your own pages rather than against the word test.
Every change is stored with its author and its timestamp, and older versions stay available. That is what makes it safe to let more people edit, because a bad change becomes a revert rather than an incident. We show your editors how to read a revision and restore one. A safety net nobody knows about changes nobody's behaviour.
Frappe Wiki Against the Alternatives
Most teams arrive here from a per-seat tool whose bill has quietly grown, or from a shared drive with no history at all. The honest comparison is not a feature count. It is whether you want the content in a database you control, and whether somebody is going to own the thing once it exists. We manage the rest of the Frappe application range on the same footing.
In your own database, authored in markdown, on an openly licensed application. Export it whenever you like. A hosted tool holds your documentation and prices your access to it, which is comfortable until the renewal arrives. Our knowledge base software comparison sets out where each of the hosted tools stops.
One flat monthly price that does not move when you add readers or authors. Per-seat documentation pricing charges you for the exact behaviour you are trying to encourage, which is more people reading it and more people fixing it.
Contributor edits are held as patches until somebody approves them. Lighter tools tend to either let everything through immediately or lock editing down to a few accounts. The space between those two is where wrong instructions get published and stay published.
Wiki sits on the same Frappe site as your other apps and shares its user accounts, so an employee exists once. A separate documentation product is another account list to keep current and another one somebody has to remember at offboarding.
Self-hosting is real work. Upgrades, backups, Redis, TLS and the restore you hope never to need. That is the true cost of ownership and taking it is what you are paying us for. If nobody is going to take it, a hosted tool is the better answer and we will tell you so.
Markdown converts well. Internal links, hotlinked images and tables built in a proprietary editor do not. Whoever moves the content owns those repairs, and the number of them is the real size of the project.
Who This Is Built For
There is a floor under this. If you are a handful of people who need somewhere to write down how things work, running your own application is more machinery than the problem deserves, and a hosted knowledge base we set up and manage will serve you better for less. Frappe Wiki starts to pay when you want the content in a database you control, when an approval trail matters to somebody outside your team, or when you already run a Frappe site and this is one more app on it.
How We Get You There
Most of the risk in a documentation project sits at the beginning rather than the end. Structure decided badly is expensive to undo once pages have routes and other people have linked to them.
1
We look at what you have now, who reads it, and who should be allowed to change it. Out of that comes the space layout, the group and page structure inside each space, and the permission model. If you are migrating, this is also where we find the duplicate sidebar names and the empty titles that would otherwise break the run.
2
We install Wiki, apply your branding, configure approvals, guest access and search, then move the content and repair what broke in transit. You read the pages that matter most before anything gets announced internally.
3
We train the people who will write, on the parts they will actually touch. After that we hold backups, upgrades and support. On Priority we review structure, permissions and stale pages once a quarter and hand you the list.
Pricing
Standalone Service
DETAILS
Standalone Service
DETAILS
Testimonials
Everything we set up and support
