AppsMorax Website Builder

Web storefront, still to build

Coming soon

Say what you want changed. The site changes.

The idea is a site you describe rather than assemble — and, months later, change the same way, in a sentence, instead of booking someone to do it. It would run on the same base as everything else: your delivered galleries feed it, and a campaign starts from it. A design intention, not an application. None of it is written.

Create a site — indisponible. No code exists. The site needs projects and multi-tenant galleries, and neither is built.

This surface isn't among the twelve in the product scope: today it exists only as a catalogue entry.

What this product does

  • Publish from the galleries

    The storefront should draw on the galleries already delivered rather than ask you to upload the same images a second time.

  • Changed by asking

    Building the first version from a few prompts is the easy half. The half that matters is the one after: changing a page, a price list or a whole section by saying so, without waiting on anybody.

  • Stay up to date on its own

    A gallery that changes should show up on the storefront with no manual pass, which means a live link between the two, not a copy.

In detail

  • Two entities are missing before the first line of code

    A synced storefront means galleries and projects exist as multi-tenant entities: with no owning organisation, you know neither what belongs to whom, nor what is allowed to be made public. The galleries run single-tenant in Morax-Master today, and the projects aren't built. While those two pieces are missing, there's nothing to sync.

  • No template to show

    There's no template library behind this page. Showing a preview would be selling something that has never been designed.

  • No domain, no hosting

    How it would go live isn't settled: domain name, hosting, search. Nothing about it's described here, for want of anything to describe.

  • A view, not a duplicate

    The storefront should stay a read of the galleries and the projects. Copying the media into a second store would create two truths and a permanent sync problem.

  • No date announced

    The timing depends on pieces that aren't settled here. Announcing a date would be one more invention.

Who it is for

A photographer's portfolio
You'd want to pick a few delivered galleries and make them public as they're, without rebuilding them somewhere else.
A page for one project
A project in progress should be able to have its own page, fed by what is already attached to it.
Updating after a delivery
Adding photos to a gallery should be enough to refresh the storefront, with no second step.
Introducing the studio
A few fixed pages, like contact, approach and the studio’s own rates, should sit alongside the pages fed by the galleries.

An intention, named as one

This page says what a Morax storefront should be, and says just as plainly that none of it exists. It fills up when galleries and projects are shared entities, not before.

Create a site — indisponible. No code exists. The site needs projects and multi-tenant galleries, and neither is built.