Modules
A module is a building block of your software, dedicated to one topic — customers, billing, scheduling… Your modules, put together, make up your tailor-made application. Each module groups features (its main capabilities), and each feature is made of pages (the screens). From Modules you see every module and its progress, create new ones, open a module to read its specification and browse its features and pages, ask for changes or a fresh analysis, answer the questions the system raises, and create a module's database once its spec is ready. Open Modules to start.
Before you start — Your project's infrastructure must be installed (until then the page shows Your infrastructure is not yet fully installed.). A module moves through statuses as it's prepared and built: Analyzing (the system is writing its specification), Clarifications requested (it needs information from you), Ready (its spec is settled), Building, then Shipped. A module's status reflects its whole tree — if any feature or page still needs information, the module shows that.
See your modules
- Open Modules. Two boxes summarise the area: Modules — your Active modules and your Included modules quota — and Tokens, the Total used so far.
- The table lists each module with its name and description, its Status, a Features bar with the feature count, a Pages bar with the page count, and its Token usage.
- Click Refresh (top-right) to reload the latest progress.
Note — If the infrastructure isn't ready yet you'll see Your infrastructure is not yet fully installed.; once it is but you've created nothing, No modules yet.
Create a module
Add a building block to your project. The system queues it for analysis and writes its specification.
- On Modules, click Create a module (top-left).
- Enter the module's name and a description, and say what it's for (the problem it solves for you).
- Click Create.
The module appears with the status Analyzing while the system writes its specification, and your team is notified. A name is required.
Tip — If your onboarding suggested modules, a Recommended modules section lists them. Click Create this module to start from a pre-filled form, or Remove to dismiss a suggestion.
Open a module
- In the table, click Configure on the module's row.
- The module opens on its Overview — its Status, a Progress bar, its Description, a Database card, and the Features it groups.
- Use the tabs to move through the module: Overview, Configuration (its full specification), Features and Pages.
Note — A banner on the Overview reflects the status: The system is analyzing your module. while it's being studied, Clarifications are requested on this module. when it needs input; while it's being built a banner links to the build, and once its spec is Ready a banner invites you to start building.
Read a module's specification
- Open the module and click Configuration.
- Read the specification — what the module does, the need it answers, what's included and what's out of scope, and the list of features (split across the Application and Administration spaces).
The specification is written and kept up to date for you, so it's read-only here. From the top of this tab you can Request a change, Request an analysis, or Answer the clarifications.
View a module's features
- Open the module and click Features.
- Choose a space — Application (what your end users use) or Administration (your back-office); if your plan includes them, Website or API are also available.
- Click Detail on a feature to expand its fiche — what it does, the need it answers, what's included and excluded, and its pages.
To add a feature, click Create a feature and describe the one you want.
View a module's pages
- Open the module and click Pages.
- The table lists each page with its status, its feature, its URL and its Token usage. Choose the space (Application / Administration) at the top.
- Click Detail on a page to expand its fiche.
To add a page, click Create a page and describe it.
Note — Until a page is built, its planned version is shown; as building progresses, the real pages replace the planned ones.
Request a change
Ask for a change in plain words — the system folds it into the next analysis and reworks the affected part.
- Open the module's Configuration (or expand a feature or page and use its change action).
- Click Request a change.
- Describe the change you want, then submit.
Your request is recorded — for a module-level change your team is notified — and the item returns to Analyzing while it's reworked. Come back to see the updated specification.
Request a new analysis
Have the system re-study a module, feature or page from scratch — useful after you've filed changes, or if the generated specification looks incomplete.
- Open the item and click Request an analysis.
- Confirm.
The item returns to Analyzing and its specification (its features, pages and data model) is regenerated.
Answer the clarifications
When the system needs information to continue, the item enters Clarifications requested and is listed under Waiting for information — both on the Modules list (every open question across the project) and on the module's Overview.
- On Modules (or the module's Overview), find Waiting for information and click Answer on the row.
- Answer the question or questions.
- Submit.
Your answers feed the specification and the item returns to Analyzing.
Create a module's database
Each module is built on its own database; create it once the module's whole specification is Ready.
- Open the module's Overview. When it's ready, the Database card shows To create and a Database to create table appears.
- Click Create.
- Confirm on the page that opens — it shows the module and whether its database is shared or dedicated.
The request is recorded and the Database card follows its progress.
Note — While another database is being created on the project, the button is disabled (Another database is being created — please wait). A failed attempt shows Failed — retry.
Related
- Getting started — set up the project before you build its modules.
- Deployment — release your built modules to staging and production.
- Infrastructure — the environments and databases your modules run on.
- Feedback — report a bug or suggest an improvement.