Hey, welcome back.
So we finished up our first section, our first here in terms of our sitemap recently, and there's
other things we can do that we haven't necessarily thought about because our actual sign up doesn't
necessarily start at our home page.
It starts with our onboarding.
So what I'm going to do is I'm going to just duplicate that.
And this is where I kind of like to merge these site maps with a flow chart.
I like to call them product maps.
I mean, it's whatever you like to call them.
Just make sure you don't call them something that totally doesn't relate to what you are doing.
But so when I come to the onboarding, I will have an option to go to registration.
I will have an option to log in.
This could be like our welcome screen if I if I have logged out from the app and I will have the option
to skip the onboarding.
So this is like generally we have to think about first time users and also for users that block out,
even though that's probably doesn't happen as often.
So if the user decides to log in and register, look at a log in the register screen and that's where
they can log in.
And that's where they'll be able to register.
So we're going to make those instances in and sign up.
We will make those instances logon and sign up.
Perfect.
And if they do register.
Remember when we created this user flow, we'll go through a registration process.
And that will be profiled details.
That they'll have to enter and interest based details.
So I'm just going to do that and I like to line everything up with each other, so it's nice and neat.
What else is next?
We have to also think about, sir, so we can actually link these.
So if I bring in auto flow, onboarding could lead directly into.
That's where it will typically lead.
If they do skip the process, it can go there.
So what we can actually do is let's delete that line.
Another thing with auto flow is you can select directly from inside the container as well.
So I'm going to take my log in.
That's going to go there and my registration is going to go right there.
I can also go from registration to there.
And this is going to take me back, but I'm not going to actually do that right now.
So, OK, that looks good.
I like that.
And this log in will take me back into there.
So actually, that's getting a little confusing.
I don't think we need that.
I think that's pretty self-explanatory.
What else do we need to do?
Let's talk about search.
If Regis.
So now it's not necessarily looking like a site, not any.
I mean, this portion is we know the hierarchy of our entire product, but over here we're just thinking
about like what happens even before the product and what that hierarchy looks like.
So it's just something that helps me figure out how I want to approach wireframe and actually kind of
helps me think about the different types of.
Inputs or elements?
I'm going to have to design for.
So we're going to have a search.
And we'll have the input, we'll have a way to have previous searches so this can be like a member only
thing, and I'll just change in a second, actually.
Let's just leave it at that.
I like that it's totally fine.
So what do we have here?
We have members only, so that's good.
And search results.
I wanted to kind of just create a little screen for them.
Let's fix that search results.
Perfect.
So we'll have.
Don't like that and listening to the content here, so we'll definitely have an input for a search.
We'll have filters.
We will have items.
So now I know essentially what this is going to have.
Let me just make sure everything is.
Lines.
OK, let's just bring it autofill one more time.
And I know that search is going there and I know that this is going to lead to my search results so
I could actually go in and individually link all the different pages to their part.
I mean, you could do that.
It starts getting confusing because there's so many crossing lines.
But this is what our Senate has begun to look like.
And you can definitely build this out more.
You can go into here and think about what the categories mean, what do those pages look like?
But as you can tell, we're probably not going to go past another level.
We'll probably go one more level in certain areas.
And that's it.
The main content that we're really focused on, like searching, is going to be very big primary action.
Same with things like shopping interests and habits I have.
It's structured so that these are this is the way that you're necessarily going to come across on the
screen.
That could change.
But that's the way I'm thinking about it right now.
So I want you to continue building out this site map as you see fit.
I mean, go for it based off of your sketches and your user flows.
Think about those a bit more.
If there's pieces that you think come up that you or I have missed, I mean, fill in those blanks,
have fun with it and.
Yeah, go ahead and build your own sitemap.