You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following feedback from some people and for the sake of keeping the codebase lighter, let's discuss what we can do with Example UI.
The idea behind it was to show beginners how to use SE2 (components, hooks, styling, etc), but I don't think it has been very useful for that purpose. Also, types break the moment you start tweaking the contract, and it's something you have to remove when deploying.
I see a couple of options:
Remove it completely and create a good Recipes section in the SE-2 docs, where people can copy-paste examples that work out of the box. This is what most libraries/starter kits do. I already created the issue: Recipes se-2-docs#25, since the "Recipes" section is something that we wanted to do anyway.
Add it in as an extension for the CLI. People could opt in if they want. "Would you like an example UI that shows how to style and use hooks?"
My vote is 1, since I don't like cluttering the CLI options with this, something that I feel it's not that important / useful.
Let's hear what you all think!
The text was updated successfully, but these errors were encountered:
Following feedback from some people and for the sake of keeping the codebase lighter, let's discuss what we can do with Example UI.
The idea behind it was to show beginners how to use SE2 (components, hooks, styling, etc), but I don't think it has been very useful for that purpose. Also, types break the moment you start tweaking the contract, and it's something you have to remove when deploying.
I see a couple of options:
My vote is 1, since I don't like cluttering the CLI options with this, something that I feel it's not that important / useful.
Let's hear what you all think!
The text was updated successfully, but these errors were encountered: