Adding a CMS to Your Pyramid Web App Transcripts
Chapter: Welcome to the course
Lecture: Welcome to the course
Login or
purchase this course
to watch this video and the rest of the course contents.
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.
0:12
And CMS Page is understanding the difference between these two things will show you the value of this course and what you're gonna learn.
0:18
During most Web applications we build in pyramid or other frameworks like Flask and Jingo.
0:24
These are data driven Web APS, 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:35
I might be I don't warg and we're looking at the AWS seal I package the command line interface were working with AWS in this page.
0:43
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.
0:51
For example, here we have the name of the package and its version. Here we have how to pip install name of package.
0:58
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:05
Some details about links and information, the project description, all of these things.
1:11
No matter what package I look at, it's always gonna be little cookie cutter stuff that fills in these pieces of information.
1:18
Another example might be Amazon.
1:20
You go and you had a category, then you pull open item and it showed you a picture and has the reviews in the price and that kind of stuff.
1:26
Those are the data driven world. They're very, very structured.
1:30
They're HTML template is all built around having this little holes where you plug in the data in. It's the data that varies.
1:38
On the other hand, in the much more freeform world, we have things like WordPress and medium and other sites. Jumla, you name it.
1:46
There's a bunch of these that are much more. I'm going toe log in, get a text editor.
1:51
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:58
We could come here, we could log in and we would get something that looks like this is my personal blogger, WordPress here and notice.
2:05
It's not just a block. It has pages. It has a navigation. It has Bobo's. Of course.
2:11
Here's some of the pages, and if I want to go edit him like, for example, that contact Michael one.
2:16
Unlike a data driven app, I don't go and start editing source code and redeploy the website.
2:20
No, I can go and pull this up and set the title and right arbitrary HTML.
2:25
And here and notice on the right of a bunch of capabilities toe change the layout to change the URL toe publish or not unpublished this page and so on.
2:34
And then eventually, once I write and publish it, you can see here is the page that you saw in that editor.
2:40
This is very different than the data driven world. You basically have a freeform editor that creates all of this content.
2:48
But the most important thing is sometimes you want this behavior from the CMS, and sometimes what you want is that data driven behavior, most e commerce or other types of abs along those lines.
2:59
There the data great driven kind. 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:08
And the big challenges. Should we create our site in a CMS like WordPress?
3:13
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:21
And what we're going to find in this course is that it doesn't have to be either or we're gonna take our pyramid Web.
3:27
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:36
As you see over here, the other pages will be more like landing pages, marketing people support people can log in into a very rich editor that we're gonna add, and they're going toe just right content that's going to generate our site.
3:48
But the important thing is the CMS side of this story over here on the right will still have the capabilities of our website, for example, noticed in the top.
3:58
This site will still know that were logged in.
4:00
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, well, half of the site is now this weird, disjointed CMS thing.
4:11
And the other half is the proper Web app know they're the same thing, and we're just gonna learn how to add this cool seem s capability that's gonna be high performance.
4:20
Has rich editing all sorts of cool capabilities plugged that into our existing data driven web app without interfering with what's happening there, but adding this great capability that non developers can contribute to the content of the site.