4 ms·

I've browsed the site, the documentation, repo and tutorial. I still don't know what the content model or publishing flow is. I realise that the concept of a g

by thruflo 12y ago

I've browsed the site, the documentation, repo and tutorial. I still don't know what the content model or publishing flow is. I realise that the concept of a generic CMS implies DB backed with bespoke content types. However, it would be nice to know whether there are any 'first-class-citizen' types (user, profile, blog post, etc.), how pages are built or constructed (static html export? dynamic templates?), how edited content is stored and how / whether I might intermingle CMS edited content with UGC content. This kind of information would be much more interesting to me than learning that the thing is "Beautiful", "Light" and "Agile".

tomd 12y ago
Thanks for the feedback, @thruflo. The project site is really focused on potential clients, but you're right that the documentation should be clearer about these basics. The README lists a 'feature' as 'Configure content types through standard Django models', which hopefully makes sense to Django developers; essentially you configure your own content types as Django models and register them as pages, where they inherit tags, slugs, publication dates etc. Users are standard Django users and can be augmented with profiles if you want. The wagtaildemo project [1] includes blog posts as a fully worked-up content type, but you don't have to include these in your project. Pages are constructed on the fly, and Wagtail is Varnish- / Squid-friendly if you have lots of traffic. FWIW we're working on a static HTML export feature which could be used for archiving or publishing to S3 etc. Edited content is stored in the database. You can intermingle CMS and UGC content - students at the Royal College of Art are uploading their own work alongside the content managed by the site's administrators, for example. Plus it's really beautiful, light and agile :) [1] https://github.com/torchbox/wagtaildemo https://github.com/torchbox/wagtaildemo
- thruflo 12y ago
  Thanks for the info. And for the record, I very much welcome the beauty, lightness and agility :) Just as a ref, here's a CMS intro that focuses on the content model and workflow: https://github.com/SpontaneousCMS/spontaneous#features-currently-supported https://github.com/SpontaneousCMS/spontaneous#features-curre...

by thruflo 12y ago

tomd 12y ago

Thanks for the feedback, @thruflo. The project site is really focused on potential clients, but you're right that the documentation should be clearer about these basics. The README lists a 'feature' as 'Configure content types through standard Django models', which hopefully makes sense to Django developers; essentially you configure your own content types as Django models and register them as pages, where they inherit tags, slugs, publication dates etc. Users are standard Django users and can be augmented with profiles if you want. The wagtaildemo project [1] includes blog posts as a fully worked-up content type, but you don't have to include these in your project. Pages are constructed on the fly, and Wagtail is Varnish- / Squid-friendly if you have lots of traffic. FWIW we're working on a static HTML export feature which could be used for archiving or publishing to S3 etc. Edited content is stored in the database. You can intermingle CMS and UGC content - students at the Royal College of Art are uploading their own work alongside the content managed by the site's administrators, for example. Plus it's really beautiful, light and agile :) [1] https://github.com/torchbox/wagtaildemo https://github.com/torchbox/wagtaildemo

thruflo 12y ago
Thanks for the info. And for the record, I very much welcome the beauty, lightness and agility :) Just as a ref, here's a CMS intro that focuses on the content model and workflow: https://github.com/SpontaneousCMS/spontaneous#features-currently-supported https://github.com/SpontaneousCMS/spontaneous#features-curre...