Time for another feature post methinks! And a bit of chance for me to ruminate on some recent development work. That seems to happen so little at the moment that I love to have the chance to ramble about it…
{ 0 comments }
I asked a question on LinkedIn* a couple of weeks ago, the answers to which started me off on a long, ranty chain of thought in my head.
Most of the answers were very good (a few were just okay or didn’t really respond to the question), so there was no problem there. My thoughts were really triggered by how the answers showed how limited people’s thinking is around web design and technology.
I’ll explain…
{ 2 comments }
I’ve always been terrible at versioning software. Terrible. So terrible, in fact, that I’ve never done it. Renaissance is no exception. People have always exhorted me to do it, and, well, I guess I’m caving in…
{ 2 comments }
Okay, I’ve mentioned views a few times now and have oft promised to explain them, so now would probably be a good time.
It’s pretty simple stuff, but if you’ve not already done so, you should read my earlier post about content syndication in Renaissance, otherwise all this stuff about views might not make a whole lot of sense.
{ 0 comments }
I recently wrote a post (well, more of a ramble really) on the pros and cons of releasing a software project into the wild world of open source. My conclusion was something along the lines of it being a great thing to do, especially if you want to make money from it (not despite it). The open source movement, apart from its main point of producing useful products in the most ethical, open way possible, is also a great marketing platform.
But, you can only use it as such with,
- A great commercialisation model,
- A good bit of marketing savvy and,
- Healthy respect for its true reasons for existing.
{ 3 comments }
I’ve managed to get some stuff done over this weekend, for the first time in many moons. Feels good! Ignoring tweaks and bug-fixes, this has been my longest drought on Renaissance work in a while.
So on what have I been working?
{ 1 comment }
Yes, it’s yet another post on something that Renaissance does, well, a little bit differently. So, ladies and gentlemen, our topic for today is time-based content publishing.
{ 2 comments }
I guess this is a big struggle for most egalitarian coders, especially freelancers and small businesses. We love open source. We love to have grub on the table. We can’t have both. Or can we?
{ 4 comments }
I’d thought I’d address something pretty basic to Renaissance fairly early on, and that’s its content system.
(Side Note: You’ll have to forgive me for the completely random order of these early posts. It’s hard to know where to start, so I’m just going with it and jumping around from topic to topic).
First things first—Renaissance makes a clear distinction between pages and content. So unlike in, say, WordPress, so don’t just go to ‘make a new page’ and start typing in your content. You make the content first, and then go and create the page, slotting the content in just where you want it.
Sound backward? Allow me to explain…
{ 4 comments }
Setting up this blog meant working with WordPress for pretty much the first time (I’d set up the odd install before, but never customised). It also meant working with a WordPress theme for the first time (DIY’s Thesis—great stuff).
Needless to say, this got me thinking about templates, and how they’re handled in PHP applications. I don’t really know a lot about how things are done out there (I’ve worked with Joomla a tiny bit, and really wasn’t impressed, especially with the template system), so I was quite curious to see how templates are handled in WordPress.
{ 3 comments }
