Versions and projects · Chapter 13

Drafts and publishing

A published version never changes again. What applied in March 2024 still stands exactly so in five years. You can only change a draft, and only publishing makes it the CI that applies.

Creating a new version

On the client's page, click New version in the time line.

• Name of the version: such as 2027 or Relaunch.
• Starts with: an existing version that is copied, or empty.

Create draft creates it. The old version stays as it was. If the name exists already, nexbrand adds “(2)”. A client holds at most 300 versions and 30 drafts.

The draft's bar

A draft has a bar of its own. It says where it came from: by hand, collected, over MCP or chosen by the client, plus “Draft by Robin”, which version it was made from and which version applies until it is published. Below come the buttons:

Editing and saving

In the editor a fixed bar at the bottom shows Unsaved changes or Everything saved, with Save and Done. If you leave with unsaved changes, nexbrand asks Discard unsaved changes?; the browser asks as well before you close the tab. Publishing only works once everything is saved.

Publishing

1. Click Publish

   The dialog asks for the Name of the version, so you can change it once more.

2. Choose Valid from

   Today by default. Use a date in the past for an old CI you record afterwards, and a date in the future for a CI that only applies from a set day.

3. Publish now

   From here the version is fixed. Any further wish becomes a new version.

A version with a later date counts in the app, the code and the API only from that day. Until then the previous one applies; the chapter Time line shows what that looks like.

Deleting a draft

If the draft is before the client right now, nexbrand warns you: deleting closes the review, and its comments are lost. If a project stands on the draft, it does not work: “A project builds on this draft. Move the project first.” Published versions cannot be deleted; they stay for the history.