DEV Community

Cover image for Consistent Onboarding - Building SaaS #52
Matt Layman
Matt Layman

Posted on • Originally published at mattlayman.com

2 2

Consistent Onboarding - Building SaaS #52

In this episode, we glued together some of the onboarding steps. I added data validation so that future steps depend on data existing from previous steps. Then we added page messaging to direct users to a proper page.

We reviewed the way that the form validates certain data from the form submission so that data is kept safe between users. I showed how I switched from the model and fields attributes of CreateView to a form_class containing the form that does the necessary validation.

We talked about how the onboarding flow is interconnected. With that context, I updated the first step to ensure that the school year data can only be created once.

We also updated the second step to ensure that a user can't proceed until the necessary data from the previous step is present.

I added tests to check the various conditions and updated templates to render the right thing for the various states.

This article first appeared on mattlayman.com.

Heroku

Simplify your DevOps and maximize your time.

Since 2007, Heroku has been the go-to platform for developers as it monitors uptime, performance, and infrastructure concerns, allowing you to focus on writing code.

Learn More

Top comments (0)

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay