Replies: 6 comments 7 replies
-
@salty-ivy I think this is a good idea! Wagtail has a We’ve discussed adding support for templates to this in the past. This would allow us to keep the "bootstrap a project" logic in Wagtail itself, and make it possible to support arbitrary templates. Some of those templates could be official ("simple blog"), and some could be from third parties. There’s also been some work on doing this kind of project bootstrapping with a UI in the past – see for example https://wagtail.build/. |
Beta Was this translation helpful? Give feedback.
-
Just a note to say we’ve discussed this in today’s core team meeting, and are quite keen to invest in |
Beta Was this translation helpful? Give feedback.
-
👋 for anyone interested – we’re actively looking for feedback on people’s expectations with that kind of feature. For example:
|
Beta Was this translation helpful? Give feedback.
-
Really nice idea thanks for all I think, you should have a look here https://github.com/copier-org/copier https://copier.readthedocs.io/en/latest By example Copier allow to synchonize all 229 repo here https://github.com/OCA My 2 cts |
Beta Was this translation helpful? Give feedback.
-
Another template idea: a very minimal template with Wagtail stripped down to the core (no contrib packages), no That would also be a good starting point to monitor the coupling of some packages (e.g. |
Beta Was this translation helpful? Give feedback.
-
All project templates should use a custom User, Images and Documents model. Or maybe opt out of this with a command arg. These are hard to change later. |
Beta Was this translation helpful? Give feedback.
-
As far as i have seen the most generic usecase for any CMS is the blog sites. they help us create easy blog sites really fast.
this idea occured to me as i was creating multiple blog sites for my friends lately i was doing the same process over and over again...
IDEA
i have seen what most of the application organizations do as they monitor the use-case by their clients as it becomes so common amongst people they sort build and a generic abstraction of that process and add it as ready to go feature.
this is what i propose for wagtail as well as wagtail is not only limited to blog site but blog sites is still grabs majority part of in usecase graph for any CMS.
we can have generator command that can build the basic boilerplate or ready to use structure for blogs.
something like
python3 manage.py createblog
that would do the following..models.py
with generic blog structure likeBlogPage
BlogIndexPage
orArticle
with common attributes liketitle
body
datatime
or may beimages
3.creates a template and static files for it.
4. Equip the template with links to its static files CSS and JS.
5. may be adding a little bit of styling already.
we can also get into more choosy part of this later on if implemented.
Alternatives
instead of command line, we could make this UI based.
as individual package. what comes along with its data migrations, just like
modeladmin
, adding it toinstalled apps
and so on...
we can provide some ready to use layouts as well similar to
hashnode
i.estacked
,grid
etc.Beta Was this translation helpful? Give feedback.
All reactions