Beautiful, and once we're done setting up the profile page, essentially we're done with this controller.
And that means that we can switch gears, start dealing with AAA jobs.
So eventually, yes, it's going to look something like this where we can have the job, all jobs and
stats, but we'll start with adding the job.
And yes, we'll set up the model will set up the controller, but I want to showcase something when
it comes to our job, it's going to be faster.
You notice here how it's very similar to the profile.
And that's why it took us longer because we needed to do all the set up first, for example, off.
Now we have that in place so we can simply reuse it.
When I'm trying to say, is that yes, I know it took us a little bit longer than probably you expected,
but now it's going to be smooth sailing where everything in the front is already prepared.
So on the front end, we simply want to add things to the state and then keep setting up our functionality.
We already have all the components.
I mean, almost all the components not notice.
We still here have the select ones that we need to create, but pretty much everything is already in
place.
Now we can just start knocking out the pages one by one and effectively we want to start by creating
a job model.
So hopefully it is clear that it is in the models.
We create a job model.
I'll call this job.
Yes, we want to get the mongoose.
And then we want to set up the schema company position both required.
One is going to be maxlength 50 other 100 for both of them on set ups, some messages.
Then there's also going to be status and the job type.
Now these ones will be select winners.
These ones will be select elements with the possible choices.
That's where we'll go here within them and set them up as default planning for standard and default,
full time for the job.
Then as far as the job location, it's going to be type string default, my city.
And in this case, I will set this one up as true.
And if you're wondering why is that why I wish them was equal to required true, if we already have
the default or remember not only we can create the job, eventually we can update the job.
And if we set this up as required, true and then try to update with empty values, it's not going to
work.
And here I also have created by because we need to keep in mind that every job will be tied to specific
user.
That's the whole idea.
If I create a job, that's my job.
I can modify it.
I can look at it.
But it's only accessible to me now will be equal to created by Typekit will be mongoose, Typekit and
abjectly.
And then we'll reference the user, the user model and set it equal to required.
At the very end, we'll set up timestamps equal to true simply because I want to have that created out
and modify the fields, which will be equal to the timestamps.
And at the very, very end, we want to export that.