Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine URI paths for each page #9

Open
neatonk opened this issue Apr 26, 2023 · 1 comment
Open

Determine URI paths for each page #9

neatonk opened this issue Apr 26, 2023 · 1 comment

Comments

@neatonk
Copy link
Collaborator

neatonk commented Apr 26, 2023

Many questions to consider here:

  • How much of the builder state should go in the url vs. memory/local storage?
  • Which steps should cause a URI change and be navigable via browser history?
  • Does each layer in the builder have a distinct URI?
  • Etc.

Much of this will be answered while building the UI and assessing the tradeoffs.

@neatonk
Copy link
Collaborator Author

neatonk commented Apr 26, 2023

E.g.

/destroy  --> all-in-one construction page and pre-mint preview page, with construction state in memory.
/nft/[id] --> post mint page

OR

/destroy  --> construction page, all layers.
/mint     --> pre-mint preview page, with construction state in memory.
/nft/[id] --> post mint page

OR

/destroy/[n]  --> construction pages, one for each layer 1-5.
/mint/[0x...] --> pre-mint page with state in URL e.g. as hex encoded string.
/nft/[id] --> post mint page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant