Adding a CMS to Your Flask Web App Transcripts
Chapter: Welcome to the course
Lecture: Welcome to the course
0:00 welcome to the course. Thank you for considering adding a CMS to your Web app as one of the courses that you're going to study.
0:08 Now let's dive right in and talk about data driven pages. And CMS Page is understanding the difference between these two things will show you the value
0:17 of this course and what you're gonna learn during most Web applications we build. These are data driven Web APS,
0:24 and what I mean is the page always looks the same, no matter what thing you're looking at. Here, for example, is Pipi.
0:31 I i p I don warg and we're looking at the AWS seal I package the command line interface were working with AWS in this page.
0:39 It's always gonna look like this, but little elements will be filled with parts of the data from one or more tables from the database. For example,
0:48 here we have the name of the package and its version. Here we have how to pip install name of package.
0:55 Over here we have whether or not it's release is the latest release. And when that was, here's a little summary that comes out of the database.
1:02 Some details about links and information the project description all of these things. No matter what package I look at,
1:09 it's always gonna be little cookie cutter stuff that fills in these pieces of information.
1:14 Another example might be Amazon. You go and you had a category, then you pull open item and it showed you a picture and has the reviews in
1:20 the price and that kind of stuff. Those are the data driven world.
1:24 They're very, very structured. They're HTML template is all built around having this little holes where you plug in the data in.
1:32 It's the data that varies. On the other hand, in the much more freeform world, we have things like WordPress and medium and other sites.
1:41 Jumla, you name it. There's a bunch of these that are much more. I'm going toe log in, get a text editor.
1:48 I'm gonna type information that's going to create pages and blog's and articles and all that kind of stuff for reward press.
1:55 We could come here with that log in, and we would get something that looks like this is my personal blogger WordPress here and
2:01 notice It's not just a block, it has pages. It has a navigation it has Bobo's. Of course. Here's some of the pages, and if I want to go edit him like,
2:10 for example, that contact Michael one. Unlike a data driven app, I don't go and start editing source code and redeploy
2:16 the website. No, I can go and pull this up and set the title and right arbitrary HTML. And here and notice on the right have a bunch of
2:23 capabilities toe change the layout to change the URL toe published or unpublished this page and so on. And then eventually,
2:31 once I write and publish it, you can see here is the page that you saw in that editor. This is very different than the data driven world.
2:39 You basically have a freeform editor that creates all of this content. But the most important thing is sometimes you want this behavior from the CMS,
2:48 and sometimes what you want is that data driven behavior, most e commerce or other types of abs along those lines. There the data great driven kind.
2:56 They've got categories, they've got details and so on. But you probably want a little bit of this CMS stuff as well.
3:04 And the big challenges should we create our site in a CMS like WordPress,
3:09 Or should we create our own data driven site and just suffer the deficiencies or require that developers set up the landing pages and stuff like that?
3:17 And what we're going to find in this course is that it doesn't have to be either or we're gonna take carpet Web.
3:23 Apple will have data driven pages and CMS pages. The data driven pages will be powered by the database with their very close structure.
3:32 As you see over here, the other pages will be more like landing pages,
3:35 marketing people support people can log in into a very rich editor that we're gonna add and they're going toe just right,
3:42 content that's going to generate our site. But the important thing is the CMS side of this story over here on the right
3:49 will still have the capabilities of our website, for example, notice in the top. This site will still know that were logged in.
3:56 It will still have access to a lot of the functionality that is this rich Web application that we built. So it's not like,
4:03 well, half of the site is now this weird, disjointed CMS thing and the other half is the proper Web app know they're the same
4:10 thing and we're just gonna learn how to add this cool seem s capability that's gonna
4:14 be high performance. Has rich editing all sorts of cool capabilities plugged that into our
4:20 existing data driven web app without interfering with what's happening there,
4:23 but adding this great capability that non developers can contribute to the content of the site