Skip to content

Classic wizardry components #9

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

Open
wants to merge 6 commits into
base: classic-wizardry-templates
Choose a base branch
from

Conversation

chancancode
Copy link
Owner

No description provided.

@chancancode chancancode force-pushed the classic-wizardry-templates branch from adf2b43 to 3d3c540 Compare October 4, 2023 04:08
@chancancode chancancode force-pushed the classic-wizardry-components branch from f82e7e0 to 3fef4f6 Compare October 4, 2023 04:10
@chancancode chancancode force-pushed the classic-wizardry-templates branch from 3d3c540 to f8a1eb9 Compare October 19, 2023 22:46
@chancancode chancancode force-pushed the classic-wizardry-components branch 2 times, most recently from 893a2a9 to e7026b4 Compare October 19, 2023 23:28
This code has gone through a lot of refactors and repurposing, and
things have become more complicated and confusing than they needed
to be.

At present, the Wizard goes through a few "required" steps for the
basics, then shows a "ready" screen directing the user to "jump in"
but have an option to continue on for optional screens, eventually
ending on the "corporate" screen which is the final step.

On desktop, there are two groups of buttons –

1. on the left side, it shows a back button except for the first
   screen

2. on the right side, there is a always a primary button (either
   "next" or "jump in"), and then to its left, there is sometimes
   a secondary action styled as a link (either "configure more" or
   "exit setup")

On mobile, these buttons are stacked, with the back button sitting
at the bottom, if present.

In table form:

Step        Back Button?     Primary Action      Secondary Action
------------------------------------------------------------------
First            No               Next                  N/A
------------------------------------------------------------------
...             Yes               Next                  N/A
------------------------------------------------------------------
Ready           Yes              Jump In          Configure More
------------------------------------------------------------------
...             Yes               Next              Exit Setup
------------------------------------------------------------------
Last            Yes              Jump In                N/A
------------------------------------------------------------------

Back Button: without saving, go back to the last page
Next Button: save, and if successful, go to the next page
Configure More: re-skinned next button
Exit Setup: without saving, go to the home page ("finish")
Jump In: on the "ready" page, it exits the setup ("finish"), on the
last page, it saves, and if successful, go to the home page

This commit re-aligns the code to reflect this reality without the
unnecessary indirections leftover from previous refactors.
@chancancode chancancode force-pushed the classic-wizardry-components branch from e7026b4 to 3a9dab6 Compare October 20, 2023 00:17
Move field components into subfolders, remove dependency on string
resolution with the runtime resolver.
@chancancode chancancode force-pushed the classic-wizardry-components branch from 3a9dab6 to b5ec3b1 Compare October 20, 2023 04:04
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

Successfully merging this pull request may close these issues.

1 participant