Create your first project
A project is the container for everything else: its versions, its specifications, its documents and its environments. Here is how to make one.
In the appProjects
A project is the container for everything else: its versions, its specifications, its documents and its environments. Here is how to make one.
A project is one application you are building. Everything else in Maleus hangs off it: its versions, its specifications, its documents, its integrations, its environments. Nothing exists outside a project, so this is the first thing you make.
A workspace holds as many as you need. Keeping them separate is the point: versions, documents and settings live inside one project, neatly apart from the others.
Start from the project list
Open Projects from the workspace sidebar. It lists everything you can reach, pinned projects first, and New project sits in the top right. That button is the whole of this step.
Everything you can open, pinned first. New project sits top right.
Each project in that list carries a name, a slug derived from it, a short description, its owner, and when it was last active. A Maleus or External badge says whether Maleus built the codebase or you connected an existing one. See Find your way around the workspace for the rest of what that page does.
Fill in the form
New project takes over the screen: what a project is on the left, the fields you have to fill on the right.
Four fields and one decision about access. The panel on the left tells you what happens after.
Project access
Access is decided here, not later. Project access is the list of groups whose members will be able to open this project.
Leave it on No group (admins only) and the form says what that means: only admins will see this project until you assign it to a group. That is a fine state for something you are still setting up, and a bad one for something a team is meant to work in. See Control project access with groups.
Source control
If your workspace has a Git provider connected, a Source control block appears under access with three choices. If it does not, the block is simply not there, and you can connect a repository later from the project settings.
The repository is best-effort. The project is always created; if the repository step fails, Maleus says so in a toast rather than losing your project. You finish the setup afterwards under Source control.
Click Create project
Two things happen, in this order, and the screen shows you both.
First, Maleus provisions your development environment: the container your app runs in, and what every preview and every agent reads from. That takes a few minutes on a first project.
Second, without you asking for it, Maleus opens a workshop on the new project and puts you in it. So the screen you land on is that workshop, still waiting on the environment behind it.
Where creating a project drops you: an untitled workshop, waiting on the environment.
The workshop is saved, so you can leave the page and come back. Once the environment is up, the spinner is replaced by a prompt asking you to describe your idea.
You are now at step two
That handoff is deliberate. The best brief for a first version is one you talked through rather than typed alone, so Maleus does not leave you on an empty project with a New version button.
Carry on in Shape it in your first workshop.
Pin the projects you actually work on, from the row menu on the project list. Pinned projects sit in their own group at the top, and the pin is yours alone.