Hacker News Reader

Comment by yaph | Hacker News Reader

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.

View on HN

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 integration is a tricky one. We like LESS but we're worried that npm / lessc is an annoying dependency, and we're considering switching to SASS / SCSS, which has a pure-Python compiler, unlike LESS. Opinions very welcome.

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...

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.

+1 for compiled CSS/JS. I'd love that and it would get me up and playing with it much faster, personally.

It would be great if you would switch it to SASS in the future. Although for me personally its not the npm dependency but that i like SASS much better then LESS.

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.

I struggled with finding a way to compile SASS last summer and my solution wasn't great[1]. Nowadays, this version of libsass for Python[2] looks pretty stable, and failing that Grunt would work well enough.

[1] http://blog.danieljost.com/scss-on-a-remote-server/ [2] https://github.com/dahlia/libsass-python

Another one: https://github.com/pistolero/python-scss

I haven't. I've never used SASS directly on the production server, I just run Compass on dev and push the compressed css to a cdn or media server.

You might want to look into the C implementation? https://github.com/hcatlin/libsass

Reply on news.ycombinator.com