fabrikaERP

One platform holding three things that are usually three products: the public website, the back office that configures it, and the ERP the company is actually run from. They share one database, one set of permissions and one idea of what an organization is.

That last part is the design decision everything else follows from.

One firm, one world

Every record, file, term, page and setting belongs to an organization. Two firms may run on the same installation and neither can see the other — not their products, not their files, not even a label. Where you are is whatever the toolbar says you have open.

The three doors

The websitePages, products, categories and everything a visitor reads. Address / — content edited in the back office.The back officeContent types, fields, listings, appearance, users, translations. Address /backoffice/ — where the platform is configured rather than programmed.The ERPStock, orders, customers, projects, helpdesk, people. Address /erp/ — always exactly one open organization.

Where to start

First loginGetting in, and what you see when you do.OrganizationsThe boundary everything else respects.Your first content typeDescribe a thing once; the forms, listings and pages follow.

What makes it different

Nothing is programmed, it is configured. A new kind of record — a machine, a certificate, a service contract — is a content type with fields. It gets a form, an address, a listing, revisions, permissions and translations because every record does, not because someone wrote them for that type.

The address is answered once. Where a record lives is decided in one place, so an editor's alias, a taxonomy term's own page and a plain record address are all the same question with one answer. Nothing hand-builds a URL.

Nothing happens silently. An import that skipped a file says so. A listing that refused to embed says so. A term nobody uses any more is reported and not deleted. The rule is old and dull and it is the reason the system can be trusted with a customer's data.

This documentation is the product documenting itself

You are reading pages that live in a git repository and are pulled into the platform by Sourcebook, the same engine your own documentation would use. See the dialect.