Getting Familiar with our Web Project

In This Lesson

We'll quickly walk through the web application we've cloned down to get familiar with the data at play, how it's presented to the user, and the features at hand.

Created by: @tomgobich
Published: 8 months ago

Join the Discussion 0 comments

Be the first to comment!

Transcript

Okay, so to pick right back up where we left off in the last lesson, let's go ahead and get a user registered inside of our application
and then go over what exactly our application entails so that we're familiar with what we're adding an API for. So I'm gonna call my user testuser1
with an email of testuser1@test.com and then something for the password. Let's go ahead and hit register here, which will take us to our create an organization screen.
I'm just gonna call this testorg1 and create that organization and then we're taken into it where we see the courses for this organization and currently we do not have any.
So overall, what this application allows us to do is create courses, modules within those courses and lessons within those modules, hence the name plot my course. It allows us to plot out
what a course structure would look like or a syllabus if you're familiar with that term. Each course has a difficulty and then each course and lesson has an access level
and then all three course, module and lesson have a status. So these difficulty, status and access level pages allow us to create difficulties, edit difficulties,
delete them, reorder them and then all of that is specific to the organization itself. So if we created a separate organization, we can have a completely different set of difficulties,
statuses or access levels. Access levels are kind of the tier of access. So whether or not it's free or paid, statuses are the current status that the item is within.
So not started, planned, recorded, edited and done are the defaults there. And then difficulties are obviously how difficult it is. So easy, medium, hard and expert are the defaults there.
Within our courses, we can add in a brand new course. I'll call this my first course where we can select the access level, status and difficulty out of the box.
We'll leave all of those as defaults and add our course in. Here we're taken to the actual course show page for the course that we've just created where we can see its status, difficulty and access level.
Click on any one of these to automatically change it to whatever value we see fit for all three. In addition to that, we can edit the course, delete it, add in a new module.
So my first module where that also has a status field and then lessons. So my first lesson,
we can set a designated publish at date and time and then its access level and status there too. So I'm gonna fill out just some very basic information here so that we have some simple stuff to work with
out of the box with our API. So I'm gonna create two modules. We'll call this one my second module and then three lessons. So we'll call this one my third lesson
and I'm gonna rename this one to my second lesson. Okay, and then just like with our difficulty, status and access levels, all of these can be resorted as well.
So if I wanted my third lesson to move up into module one, just do that like so, just drag and drop with that little arrow over there. Each module is given a number
which is the major number within this list. And then each lesson is given a number as well, which is the minor number in this list. So our first lesson in the first module is 1.0.
Then the second lesson in the first module is 1.1. And then our first lesson in the second module is 2.0 and it will continue so on and so forth in that manner. Just like with our series,
these two also have the ability to change their status and access level off the fly with these little dropdown menus. As covered in the introduction,
the one and only area that we are going to be altering is the organization settings. So let's take a look real quick through all of these settings. So we have our profile settings,
which just allows our user to change their name, account settings, which allows the user to change their email as well as delete their account. And then our organization settings, which we briefly saw in the introduction
where we can update the organization, invite and manage existing members and new members. And then the new panel that we will be adding, which is not yet inside of this application
to manage our access tokens for the organization. And then if at any point throughout any of these pages, you want to edit the organization, you can also do that right up here.
You can also delete it and add a new organization as well for your user. The last thing that we're going to do to familiarize ourselves with this project is to take a quick look at the schema
to see exactly what each of those entities actually looks like in terms of their columns. We're not gonna spend too much time there. We're just gonna do a quick overview.

Adding an API to an AdonisJS Web App

43 Lessons

5h 31m

Introduction

API Authentication

Getting Started with APIs

Organization Resources

Courses

Searching

Rate Limiting

Rate Limiting an Organization's HTTP Requests

13m 59s

Stop losing your best ideas!

Use our integrated note feature to capture and organize your key insights. Take a note at any timestamp and jump instantly back to that moment in the video with a single click.