React JS Property Management Application Project Overview
Hi there and welcome back to the course in this set of videos we're going to be building out a property management style application.
Guide Tasks
  • Read Tutorial
  • Watch Guide Video
Video locked
This video is viewable to users with a Bottega Bootcamp license

So what you can see here is that we have a login and a couple of different links. All right. So we can say OK we're not a member, so set's go register. Very similar form with a lot of similar features up top and or styles. Alright, now let's go ahead and go back. I'm going to go to sign up or sign in and I'm going to go to the first sign in page.

large

So you can see you can see that there's a lot of different pages except for they are the same page just with different styles. Ok, so you click on it. We are on this new page separates the same page just with a few different things you an e-mail password and red log in button.

Now we're obviously going to be implementing both of these in the same J.S. file. I just want to make it clear that there's 32 screens in this design except for most of them are the same. There's probably less than 10 overall.

Basically what we're going to be learning in this, and this course in this section is a lot about user permissions and functional components and a little bit more. So let me tell you what I mean by user permissions.

If I go to this tab we have a bunch of screens. These are all the 32 screens right now. You can see we have admin newsletter admin requests and so on, and then we have user requests and user newsletter okay.

large

So there's two different types of users there's an admin and a user. What this application does, if I've made it clear, is that you log in and there's a newsletter for the apartment complex so the people can read a newsletter every month.

Then we have a requests tab that says "hey, something in my apartment broke. Can you fix it? or can you have someone come out and fix it?" Here's an image and a dropdown.

large

Then an admin can say: "OK I want to move this to in progress and have someone go fix it or something". And an Admin can also add a request. Well, actually that is a user feature the user will be able to add the requests.

So for an admin, this will be here just because the admin is going to have supreme control except for they most likely not going to be creating requests unless someone had them created for them, like a customer or something.

Right, now back to the newsletter. I'm going to explain that permissions a bit more. So an admin can create new newsletters and add at the newsletters. Obviously, we don't want normal users to be able to edit these newsletters. This is purely for the management team to add new newsletters.

large

There's also an archive that will show the users different newsletters over the past months. If you click on that it brings us to a detailed screen. So just kind of get familiar with this design. It can be a little confusing sometimes, and make sure you understand what's going on here before we start the application.

So let me go to the requests real quick, and I want to show you this drop down. You'll see that it's very similar to our last applications. One of our last application features. Now open a new tab we just built this application and basically we have this dropdown on these items so very similar.

large

We're not going to be using the component we built in this although, but that would be kind of a fun idea because we've already built it, but we're going to be building it from scratch. Just wanted to let you know that that's kind of an example of where you could reuse that component.

large

Okay I'm going to close out of this since that's all the course is on, and go back up here okay. So we have all these different features and permissions. That's the main thing I want to get out is that we have different permissions.

Now I've built a server that you're going to pull down from github, and we're going to be communicating with on an application with. So it's going to have actual usernames and passwords.

We need to create actual accounts and we're going to create actual items on the backend and I'll show you how you can pull that down and get it running locally on your machine, so that we're not all dealing with the same data because that could get real messy real quick.

I want you to have a copy of the server that you could even go through and learn how it works yourself. But mainly just so we don't have a bunch of data for everybody using the same data. So let's go ahead and hop into the next video where we will generate our project and go from there.