Live data from Hacker News

Show HN: Wagtail, our new Django CMS

news.ycombinator.com

71–80 of 99 posts

Re: Show HN: Wagtail, our new Django CMS

#71
Really nice. One question:

One feature I always wanted implemented in whatever CMS I was using was the ability to enter, say, a comma-delimited list of page titles, select the parent page and template to use, and have the CMS generate those pages in one go, instead of having the content editors hit the "New page" button fifty times.

I used to work for a large medical company, and they're departments always had special requirements, with lists of sub-pages to create for their department. Three hours later (it was a Java-applet-based CMS :( ), I was just about done with creating their pages.

Re: Show HN: Wagtail, our new Django CMS

#74
post #67

Would you gents (upstream wagtail guys) be interested if I took a shot at integrating pelican into this? I'd like a static blog and semi dynamic site and <3 django.

That sounds very delicious to me. this CMS to build sites, and S3 static to host them :)

The Royal College of Art (for whom Wagtail was originally developed) have commissioned an 'archive' feature, which will take a snapshot of the whole site, or a sub-section of it, and export as standalone HTML with all assets. We're planning to extend this feature to support publishing to S3 / Github Pages / SFTP etc.

Re: Show HN: Wagtail, our new Django CMS

#76
post #5
post #3

The first thing I look for on a marketing site for a CMS is the link to the demo, which isn't there. Generally, I think demo videos don't fill this void and this one does a particularly bad job, unless maybe played at half speed. Apart from that, Wagtail looks very interesting and I'll take the time and install the demo app. Thumbs up for choosing Postgres and integrating CoffeeScript and LESS.

The video is intended to pique the interest of CMS choosers with short attention spans... you're right that it's a poor substitute for a real demo, and we'll try to get something up as soon as possible. What's the best practice for refreshing the content on demo sites? I worry that a scheduled content reset will confuse people who are halfway through trying publishing a test page. The CoffeeScript and LESS integratio…

SASS for sure. I've used sass in development for years now, and I prefer to not use LESS. Having LESS as a requirement was an immediate read flag for me :)

Re: Show HN: Wagtail, our new Django CMS

#77
post #71

Really nice. One question: One feature I always wanted implemented in whatever CMS I was using was the ability to enter, say, a comma-delimited list of page titles, select the parent page and template to use, and have the CMS generate those pages in one go, instead of having the content editors hit the "New page" button fifty times. I used to work for a large medical company, and they're departments always had specia…

Wagtail is open-source, so there's nothing stopping you/someone adding that functionality - indeed, it'd be pretty trivial do to as a Django management command that would work something like:

     ./manage.py create_page_stubs path/to/your/list.csv

Re: Show HN: Wagtail, our new Django CMS

#79
post #5

Earlier quoted context omitted.

The video is intended to pique the interest of CMS choosers with short attention spans... you're right that it's a poor substitute for a real demo, and we'll try to get something up as soon as possible. What's the best practice for refreshing the content on demo sites? I worry that a scheduled content reset will confuse people who are halfway through trying publishing a test page. The CoffeeScript and LESS integratio…

SASS for sure. I've used sass in development for years now, and I prefer to not use LESS. Having LESS as a requirement was an immediate read flag for me :)

Thanks. Can you recommend a pure-Python SASS compiler? The ones we've found seem to struggle with relative imports.
Post reply on HN