Let's Discuss Customizations...

[rajikaimal]

Upto what level customizations can be done ? For an example:

• Styling the step name
• Adding custom previous and next buttons

[romanlex]

+1, and please add custom class for actions wrapper or another elements

[newbreedofgeek]

@rajikaimal at this stage

• You can hide the next/prev buttons
• Change the text of both the next/prev buttons
• Use CSS to style the next/prev buttons
• Add custom text to the last "action" next step (i.e. make the last action step save "Save")
• Hide the top navigation (e.g step 1, step 2... )
• Prevent navigation via the top navigation links

Check out the full list here: https://github.com/newbreedofgeek/react-stepzilla/blob/master/README.md

And basically you can style all the wrappers using CSS, the example CSS shows you how: https://github.com/newbreedofgeek/react-stepzilla/blob/master/src/css/main.css

@romanlex you can pretty much target all the StepZilla wrapper components using existing CSS classes. The actual "Steps" are your own custom components so you can use your own CSS classes.

e.g. All the green items can be targeting using CSS, the blue item is your own Step components so you control the what CSS classes you use.

If there is anything specific you need and can provide a strong use case, then please raise it and I'll add it as an enhancement.

Bets of luck.

[wassimz]

@newbreedofgeek Is it possible to add new button like for example a reset button that clear everything before finalyzing and go back to step 1

[rajikaimal]

@newbreedofgeek Great, thanks for the quick reply. Feel free to close this issue if you want to. (unless you want to continue a discussion here with others for queries related to this question)

[newbreedofgeek]

@rajikaimal let's keep this open for now. So others can list any ideas/requests and we can collaboratively decide on new customisations.

[newbreedofgeek]

@wassimz you could implement a reset button inside each <Step>. And position it using CSS to sit inside the footer.

When a user clicks on the Reset button your can clear your store state and then call "this.props.jumpToStep(0)" to send the user back to the first step. This this.props.jumpToStep() utility is injected into all StepZilla Steps.

[wassimz]

@newbreedofgeek Thanks for your quick response. Can we access the jumpToStep from the main components (not from steps) ?? I need to reset the steps when a user refresh or click on the steps links.

[newbreedofgeek]

@wassimz at this time you can't access it from the "host" component, you can only access it from inside the "Step" components.

If you really want to "reset" from the host component just re-render the host component and it will reset.

[slashwhatever]

Would be great to be able to supply custom components as the Next and Previous buttons. I'd like to be able to use glyph icons instead.

Quick question on points above by @wassimz - are you saying we can call jumpToStep manually from inside our step component? Reason I ask is that for some steps, I want the action of a user clicking an element inside the step to move to the next step.

It would also be really nice to have hooks into the navigation action from outside so you could create a completely custom navigation component without worrying about whether you can push the existing CSS hard enough to get what you need. For example, I'm currently trying to have a wizard where the prev and next buttons are to the left and right side of the viewport. While I'm sure I can get close to what I want, I'm not sure I can get 100% of the way there if bound by existing markup and CSS hooks.

[CleverMobile2811]

When i click title in top navigation. it doesn't work.

[rickerd]

"You can hide the next/prev buttons" I prefer not hiding the buttons but don't render the buttons. Now in the element inspector of the browser the div can be showed and messed with the form.

I hope this can be changed.

Also what i would like is a progress bar or a possibility to do this.

[osdiab]

I would love ability to use a custom button component. For my project we have a standardized button component used all over the place, passing a class name isn't convenient since it's written with styled-components and so the classname is generated at not easily accessible—but if I could just wrap that button with something that takes in whatever Stepzilla uses, that would be very cool :)

[Bhushan001]

@newbreedofgeek I think some kind of nesting approach here would really help. Like first step can spawn multiple paths according to users selection.

[rickerd]

How about that reset button? Or can you just put the answers the null again?