Live data from Hacker News

Show HN: Wagtail, our new Django CMS

news.ycombinator.com

11–20 of 99 posts

Re: Show HN: Wagtail, our new Django CMS

#13
post #9
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…

An idea for a content reset, would be to warn the user before it actually happens and/or having a visible countdown widget that tells you when reset happens. I see that the npm dependency might draw away people, maybe provide and add-on that depends on npm and makes it easy to integrate CoffeeScript, LESS, SASS?

> An idea for a content reset, would be to warn the user before it actually happens and/or having a visible countdown widget that tells you when reset happens.

Right, that doesn't sound too hard, we'll aim to add that.

> I see that the npm dependency might draw away people, maybe provide and add-on that depends on npm and makes it easy to integrate CoffeeScript, LESS, SASS?

Or perhaps we'll just ship the compiled CSS / JS and provide instructions for people who want to use LESS etc in their Wagtail sites.

Re: Show HN: Wagtail, our new Django CMS

#17

Why is npm listed as dependency ? Just curious. Congrats on this, it looks awesome.

We currently need npm for lessc, as part of django-compressor, to compile LESS. We want to reduce the dependencies as much as possible, so we're looking into converting to SASS / SCSS, which has a pure-Python compiler, or simply shipping the compiled CSS / JS files for people who don't need to change them.

Thanks for the congrats!

Re: Show HN: Wagtail, our new Django CMS

#19
post #14
post #11

This looks interesting, but I can't take it seriously. From what I can tell, you haven't written any tests at all.

Some of the tests are the default django assert 1 + 1 = 2, but there are quite a few others scattered about the directories.

I wasn't counting the default django 1 + 1 test, but I did find one actual test. It's obvious that a lot of work was put into this, and I think it has potential. My suggestion to the creators is to start with tests from the beginning. However, it's not too late to start now and add tests for everything. It's a lot of work initially, but it will pay off for years to come.

Re: Show HN: Wagtail, our new Django CMS

#20
Seems really good! Are you planning to compare it with other CMS (especially Django-CMS)? I would like to see its performances (with or without varnish).

Would you like to add OAuth support or other auth mechanisms like CAS? =) I didn't find documentation for the "WAGTAIL_PASSWORD_MANAGEMENT_ENABLED" option.

Post reply on HN