Comments on: Keeping Things Simple http://www.tentonnebaby.com/2007/01/17/keeping-things-simple/ Discussion on Web Technologies, Design and London Fri, 23 Sep 2011 09:41:33 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Jake http://www.tentonnebaby.com/2007/01/17/keeping-things-simple/comment-page-1/#comment-1068 Jake Wed, 14 Feb 2007 12:07:38 +0000 http://www.embeddedstream.com/2007/01/17/keeping-things-simple/#comment-1068 It's based heavily on wordpress I think, so you'd probably find them quite similar. It’s based heavily on wordpress I think, so you’d probably find them quite similar.

]]> By: Oli http://www.tentonnebaby.com/2007/01/17/keeping-things-simple/comment-page-1/#comment-1017 Oli Wed, 07 Feb 2007 20:13:16 +0000 http://www.embeddedstream.com/2007/01/17/keeping-things-simple/#comment-1017 The basic model sounds quite similar to wordpress. Curious to know how they differ - should probably download and have a play. The basic model sounds quite similar to wordpress. Curious to know how they differ – should probably download and have a play.

]]> By: Jake http://www.tentonnebaby.com/2007/01/17/keeping-things-simple/comment-page-1/#comment-997 Jake Mon, 05 Feb 2007 16:24:53 +0000 http://www.embeddedstream.com/2007/01/17/keeping-things-simple/#comment-997 Sorry - tag soup is the common expression, but with asp.net, it's more usually attribute-soup! Sorry – tag soup is the common expression, but with asp.net, it’s more usually attribute-soup!

]]> By: Jake http://www.tentonnebaby.com/2007/01/17/keeping-things-simple/comment-page-1/#comment-996 Jake Mon, 05 Feb 2007 16:23:39 +0000 http://www.embeddedstream.com/2007/01/17/keeping-things-simple/#comment-996 In my current CMS of choice (Expression Engine), it's not the html that's embedded into the php, but the other way around. You start off with the html, but some sections have embedded CMS commands, and, optionally, php. The nice thing is that you get to hide the implementation of often very rich CMS functionality (or custom stuff you write yourself), but you're always working with the html page. You never lose sight of the important stuff - what's going to hit the client. I'd agree with you, the tag-soup that's produced by the average asp.net developer is partly a symptom of the development environment shielding the developer from stuff they should think about. The model used by EE has the added benefit that you can create php-based custom modules and extensions, but you can make the CMS itself refuse to parse php, so you can restrict more junior developers from doing potentially unsecure things, and just get them to focus on building sites. Jake. In my current CMS of choice (Expression Engine), it’s not the html that’s embedded into the php, but the other way around.

You start off with the html, but some sections have embedded CMS commands, and, optionally, php.

The nice thing is that you get to hide the implementation of often very rich CMS functionality (or custom stuff you write yourself), but you’re always working with the html page. You never lose sight of the important stuff – what’s going to hit the client.

I’d agree with you, the tag-soup that’s produced by the average asp.net developer is partly a symptom of the development environment shielding the developer from stuff they should think about.

The model used by EE has the added benefit that you can create php-based custom modules and extensions, but you can make the CMS itself refuse to parse php, so you can restrict more junior developers from doing potentially unsecure things, and just get them to focus on building sites.

Jake.

]]>