Websites, documents, photos, tables, chats and files — one construction

The diagram shows eight projects by different people: websites, an album, a document, a prototype, a client base and a developer’s app. Beneath them are three levels: products, components and shared services.

Scroll — the diagram shows how they connect.

The projects illustrate how the system is structured.

An author builds a website from blocks

In this example, the yoga studio website is built in Init. The product uses page blocks, which rely on shared file storage.

Each block is a component. The same components work in the photographer’s portfolio, the price list and the developer’s app.

A developer connects to the same data

The proposed developer flow defines a table in Tables, exchanges data through the API and embeds schedule and gallery widgets in a custom app.

A published view will define which table fields appear on a website. Hidden fields must stay on the server.

Each product does one job

Frame for screens and prototypes, Init for websites and documents, Images for albums, Tables for data, CRM for clients, Disk for files.

The shared Redactor.dev editor is planned as one interface for the components. Each product keeps its own interface for focused work.

Shared logic holds the whole system together

Users handles accounts and sign-in. The same account connects Init, Images and Frame, while each product keeps its own interface.

The three products and their connections to the shared account service are highlighted.

The levels fold into one construction

A project rests on products, products on components, components on shared services. You can start with any available product.