Live data from Hacker News

Show HN: Pagekit – A new, modern CMS built with Symfony components

pagekit.com

21–30 of 62 posts

Re: Show HN: Pagekit – A new, modern CMS built with Symfony components

#22
post #21

Was it essential for this project to use PHP to compete with Wordpress? In other words, does cheap, cheap hosting still imply PHP?

Basically. You can get cheap VPSes but knowing what to do with it still has a high learning curve. An alternative could be docker images with something like orchardup but thats still a little ways out IMHO.

Re: Show HN: Pagekit – A new, modern CMS built with Symfony components

#23
post #16

I was excited until I got to this: > Razr Template Engine Even if you don't like Twig (why wouldn't you?) there are at least a dozen template engines already. I wonder in what other places did NIH take over?

You can also use Twig as template engine. Not a big deal.

That wasn't really my point. Yet another PHP templating engine is a code smell to me. Or project smell, if you wish.

Re: Show HN: Pagekit – A new, modern CMS built with Symfony components

#25

I've been looking forward to someone publishing a new CMS. WordPress is great, but I've been wanting something new and fresh. I got the alpha installed and it looks good but there is still work to do, but I like what I see. Keep it up!

My neighbor is the guy behind this one that's fairly new on the scene: https://buildwithcraft.com/

Re: Show HN: Pagekit – A new, modern CMS built with Symfony components

#27
post #16

I was excited until I got to this: > Razr Template Engine Even if you don't like Twig (why wouldn't you?) there are at least a dozen template engines already. I wonder in what other places did NIH take over?

Pretty sure Razor is a .NET thing. This looks like the same syntax. The Play framework's Scala based template engine is based on it as well.

Re: Show HN: Pagekit – A new, modern CMS built with Symfony components

#28
post #16

I was excited until I got to this: > Razr Template Engine Even if you don't like Twig (why wouldn't you?) there are at least a dozen template engines already. I wonder in what other places did NIH take over?

You can also use Twig as template engine. Not a big deal.

I'm inclined to agree with adamors, any time a framework says you can plugin any templating engine, it's almost always more of a hassle than not. If you choose a templating engine that is not a first class citizen of the framework, you're often blocked from key features or functionality offered by the framework. Even if a third party library bridges the feature gap, that library often trails development of the framework or ends up unmaintained and outdated.

I also agree that it's disappointing Twig wasn't selected. It's syntax is incredibly common among templating engines so ramp up time for new developers is usually short - and once you get into the more complex features it's pretty dang cool.

Re: Show HN: Pagekit – A new, modern CMS built with Symfony components

#29

I've been looking forward to someone publishing a new CMS. WordPress is great, but I've been wanting something new and fresh. I got the alpha installed and it looks good but there is still work to do, but I like what I see. Keep it up!

If you're into shiny new things, I'd recommend Keystone:

http://keystonejs.com/

"Node.js CMS and web application platform built on Express and MongoDB."

It's a pain to get going on a Windows machine, but I got it working on my Linux box inside of 10 minutes. If you're on a Mac, its probably about the same time to get up and running.

It also uses Jade for templates along with Markdown.

Re: Show HN: Pagekit – A new, modern CMS built with Symfony components

#30

For those who don't know, the next version of Drupal (Drupal 8) has incorporated components of the Symfony project into the core CMS code. http://symfony.com/blog/symfony2-meets-drupal-8 It's still called Drupal, but in many ways it is sounding like a new CMS compared to Drupal 7.

My experience with building products with Drupal 6/7 is that it's great if your use case involves staying within the very rigid boundaries of what Drupal canonically does. If you need something custom or if you need highly-performant code, you're better off writing it from the ground up, because otherwise Drupal fights you the whole way.
Post reply on HN