Looks great. One thing that I find not so good is: There are no tests.
It would be hard to convince anyone to contribute without some unit tests.
Show HN: Wagtail, our new Django CMS
31–40 of 99 posts
Re: Show HN: Wagtail, our new Django CMS
#32This looks interesting, but I can't take it seriously. From what I can tell, you haven't written any tests at all.
So a CMS that works as the client requires and has a very nice UI can't be taken seriously because it has no tests? That's a very developer focused mindset. I'm glad it's been open sourced and I hope to see tests added by them or the community, but it's not a deal-breaker for me. And if you contribute tests I hope they'll be full functional tests to spot cross-browser regressions, JS breaks and the rest ;)
Clients do care about having a stable and bug free software. Tests is one of the best way to achieve this.
Re: Show HN: Wagtail, our new Django CMS
#33Why 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!
Can we use our own frontend stacks to design the frontend?
Re: Show HN: Wagtail, our new Django CMS
#34What's API support like? IE if I wanted to create a search widget that uses JSON. Have you considered something like Django REST Framework?
Re: Show HN: Wagtail, our new Django CMS
#35Earlier quoted context omitted.
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…
+1 for compiled CSS/JS. I'd love that and it would get me up and playing with it much faster, personally.
Re: Show HN: Wagtail, our new Django CMS
#36Looks great. One thing that I find not so good is: There are no tests. It would be hard to convince anyone to contribute without some unit tests.
There are some https://github.com/torchbox/wagtail/blob/master/wagtail/wagt... - but not enough, we know. We're on it!
Re: Show HN: Wagtail, our new Django CMS
#37Looks great. One thing that I find not so good is: There are no tests. It would be hard to convince anyone to contribute without some unit tests.
See below - there are tests, see
https://github.com/torchbox/wagtail/blob/master/wagtail/wagt... and https://github.com/torchbox/wagtail/commit/a77977a31cdfcdf95...
but we need more, and to make it more obvious how to run them. You're right that we have to do more to attract contributors. In the meantime we're offering t-shirts for pull requests...
Re: Show HN: Wagtail, our new Django CMS
#38Earlier quoted context omitted.
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!
Can we use our own frontend stacks to design the frontend?
Yes, absolutely! Our first principle for Wagtail is that it should in no way impede design decisions.
LESS is (currently) used for the admin UI, and the compiler / compressor is available to the front-end if you want it, but you can easily plug in your own compilers or use plain CSS if you prefer.
Re: Show HN: Wagtail, our new Django CMS
#39Frameworks on frameworks on frameworks.
Re: Show HN: Wagtail, our new Django CMS
#40The 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…
I generally prefer SCSS to LESS as it's essentially a superset of LESS.
Relevant link: http://metaskills.net/2012/02/27/too-less-should-you-be-usin...