3 ms·

With the explosions of frameworks lately, it's refreshing to see that people are still working on CMSs. It's interesting, though, why they made their own templ

With the explosions of frameworks lately, it's refreshing to see that people are still working on CMSs. It's interesting, though, why they made their own templating language rather than use an existing one (twig, for example, is used by OctoberCMS and there's even a Wordpress plugin.) Also in terms of clients, it'd probably be useful to have a wysiwyg editor or even just editable sub-fields that you can set for each page. Right now there's no clear-cut advantage for using this over, say, a static-page generator (except for the ORM, I guess).

u124556 12y ago
It looks (and sounds) like the [Razor](http://www.asp.net/web-pages/tutorials/basics/2-introduction-to-asp-net-web-programming-using-the-razor-syntax http://www.asp.net/web-pages/tutorials/basics/2-introduction...) template engine for asp.net, so maybe somebody there liked it? (because there's no way they think their target market has experience with that engine...)
snide 12y ago
Just an option, but I built a CMS system[1] that actually generates static websites that comes with options for WYSIWYG or markdown. It's node powered, but if you're a php coder it might not be what you want, but we do use the Swig template language (based off twig, based off django...etc). The biggest thing really is that it stores all it's data in a firebase, so the actual CMS is realtime even if the website is compiled staticly. We're launching later this week, but I can sneak you in early if you'd like. Just send an email to dave@webhook.com [1] http://www.webhook.com http://www.webhook.com
w0rd-driven 12y ago
Razr is largely inspired by the Razor view engine for ASP.NET. Twig is nice and looks to be inspired by Ruby syntax, something I'm a little more familiar with in using Octopress. Perhaps they wanted to introduce a templating engine that was a little more familiar with someone coming from ASP.NET? I can only really speculate as no definitive reason was given. Writing their own templating engine is definitely an interesting choice and one that follows the razor syntax makes it even more interesting indeed.
- riquito 12y ago
  Twig syntax takes from Django/Jinja [1], not Ruby. [1] http://fabien.potencier.org/article/34/templating-engines-in-php http://fabien.potencier.org/article/34/templating-engines-in...
woogle 12y ago
This choice is weird for a product based on Symfony, which, by default, includes the Twig engine. It means that it requires every Symfony dev (this CMS target) to maintain (at least) their brain plugged on two template engines.. Maybe the OP could explain?

u124556 12y ago

It looks (and sounds) like the [Razor](http://www.asp.net/web-pages/tutorials/basics/2-introduction-to-asp-net-web-programming-using-the-razor-syntax http://www.asp.net/web-pages/tutorials/basics/2-introduction...) template engine for asp.net, so maybe somebody there liked it? (because there's no way they think their target market has experience with that engine...)

snide 12y ago

Just an option, but I built a CMS system[1] that actually generates static websites that comes with options for WYSIWYG or markdown. It's node powered, but if you're a php coder it might not be what you want, but we do use the Swig template language (based off twig, based off django...etc). The biggest thing really is that it stores all it's data in a firebase, so the actual CMS is realtime even if the website is compiled staticly. We're launching later this week, but I can sneak you in early if you'd like. Just send an email to dave@webhook.com [1] http://www.webhook.com http://www.webhook.com

w0rd-driven 12y ago

Razr is largely inspired by the Razor view engine for ASP.NET. Twig is nice and looks to be inspired by Ruby syntax, something I'm a little more familiar with in using Octopress. Perhaps they wanted to introduce a templating engine that was a little more familiar with someone coming from ASP.NET? I can only really speculate as no definitive reason was given. Writing their own templating engine is definitely an interesting choice and one that follows the razor syntax makes it even more interesting indeed.

riquito 12y ago
Twig syntax takes from Django/Jinja [1], not Ruby. [1] http://fabien.potencier.org/article/34/templating-engines-in-php http://fabien.potencier.org/article/34/templating-engines-in...

woogle 12y ago

This choice is weird for a product based on Symfony, which, by default, includes the Twig engine. It means that it requires every Symfony dev (this CMS target) to maintain (at least) their brain plugged on two template engines.. Maybe the OP could explain?