Explore a new direction with Mythos Drafts

A page can be working well and still leave you wondering whether another direction would be better. Perhaps a studio's project grid needs more space. Perhaps a product page would be clearer with the demonstration above the feature list. Making the change is often easier than deciding whether to keep it.

Mythos Drafts gives that experiment its own source version. You can develop a different layout, review the result, and decide whether it belongs in Main. The published site stays on its published version until you choose to update it.

A draft is especially useful when the question is visual: which arrangement makes the work easier to understand? Give each attempt a clear purpose so the comparison has an answer beyond personal preference.

Open the project-name menu, choose New draft, and describe the change you want to explore. For a studio portfolio, that might be a larger opening project followed by a quieter two-column grid. Keep the project names, descriptions and enquiry route consistent so you can judge the layout itself.

Work in the draft through the familiar chat and Preview flow. Before sending a request, check the selected draft in the menu. A useful brief says what should change and which working behavior should remain: make the photographs larger while keeping project navigation and the contact form intact.

For a small correction you already know you want, editing Main may be simpler. Drafts earns its place when you need to compare a direction before choosing it.

The draft review lets you compare against Main or another available draft, inspect changed files, and open the previews. Look at the same page and screen width on both sides. Follow a project link, return to the collection, and open the enquiry page.

In the portfolio example, a stronger opening image is useful only if the next project remains easy to find. Check the narrow layout too: a spacious desktop composition can become a long sequence of oversized images on a phone.

When the draft is ready, Accept changes brings its source into Main. If Main has changed since the draft began, acceptance is blocked. Start a fresh draft from the current Main rather than assuming two independent changes can be combined without review.

After acceptance, review Main and use Publish → Update when you want visitors to receive the new version. Accepting a draft and updating the public site are separate decisions.

Drafts separates source changes; it is not a separate copy of every database or external service your project uses. Use suitable test information when trying connected forms. A test submission can still reach the service behind that interface.

For a previous result you want to recover, use version history. For a direction you have not decided on yet, create a draft and compare it. The building and editing documentation explains how requests become reviewable results.