What have I done?
Actually, a better question would probably be, "what am I doing?" I've
been plowing through the better part of thousands of lines of code. Probably not the most exciting thing to do, but sometimes you do what
you must. To tell the truth, I've enjoyed working on my current,
self-imposed project. This doesn't really answer the question "what
am I doing," very well, does it? Remember that post about object-oriented content? Well, I started working
on an article talking about applying OOC in real life. Meanwhile, I
built an OOC-driven CMS for the company at which I work. Problem? I built an OOC-driven CMS FOR THE COMPANY AT WHICH I WORK. See, I can't just go around giving away the CMS I built for my company
as they own it. I mean, there are parts I could give away,
specifically the frameworks I used, but that doesn't do anyone very
much good as they would have a net-zero. So, to solve this problem, I decided to start over and build
everything again, from scratch. I'll feel okay giving this away. First, I'm building it completely on
my own time. Second, it varies significantly from the code I wrote for
my company. Third, I won't include some of the odds and ends I built
in for company-specific goals. What will the user lose because of this? Nothing. Ultimately, the first release may be underwhelming for some. It won't
have any of the neat toys and fun things that mature,
community-supported content management systems have, but that's not
the point, right? Right? It's all about thinking of sites and content in a totally new way. In the end, I want to build something kind of like an old hotrod.
People can take the chassis and tweak it to their ends. Even at the
core, people should be able to construct and deploy sites quickly. I
know this because I'm already doing it. There is so much more I could say about the system, but it's just not
ready for the daylight yet. It still needs a lot of code... and a
name. We have a long way to go, and much patience is required. While
you wait for my project to surface, go make the web a better place.
been plowing through the better part of thousands of lines of code. Probably not the most exciting thing to do, but sometimes you do what
you must. To tell the truth, I've enjoyed working on my current,
self-imposed project. This doesn't really answer the question "what
am I doing," very well, does it? Remember that post about object-oriented content? Well, I started working
on an article talking about applying OOC in real life. Meanwhile, I
built an OOC-driven CMS for the company at which I work. Problem? I built an OOC-driven CMS FOR THE COMPANY AT WHICH I WORK. See, I can't just go around giving away the CMS I built for my company
as they own it. I mean, there are parts I could give away,
specifically the frameworks I used, but that doesn't do anyone very
much good as they would have a net-zero. So, to solve this problem, I decided to start over and build
everything again, from scratch. I'll feel okay giving this away. First, I'm building it completely on
my own time. Second, it varies significantly from the code I wrote for
my company. Third, I won't include some of the odds and ends I built
in for company-specific goals. What will the user lose because of this? Nothing. Ultimately, the first release may be underwhelming for some. It won't
have any of the neat toys and fun things that mature,
community-supported content management systems have, but that's not
the point, right? Right? It's all about thinking of sites and content in a totally new way. In the end, I want to build something kind of like an old hotrod.
People can take the chassis and tweak it to their ends. Even at the
core, people should be able to construct and deploy sites quickly. I
know this because I'm already doing it. There is so much more I could say about the system, but it's just not
ready for the daylight yet. It still needs a lot of code... and a
name. We have a long way to go, and much patience is required. While
you wait for my project to surface, go make the web a better place.
