The comment on the last post is a good one and the question: “Why not just use a pre-packaged solution like Wordpress?” is the central question for the next phase of www.bengfort.com evolution.
Before I start: I just want to say that I am about to review ExpressionEngine, Movable Type, TextPattern, WordPress, and Blogger and present a comparison of those pre-packaged solutions in the next post. The question for today’s post merely compares the suitability of using my own created blog engine vs. using a pre-packaged solution*.
Currently we are using a “pre-packaged solution”- blogger. As you read this post, you are reading a post that was created by blogger using the blogger engine, database, and server- that posted an html page via ftp onto www.bengfort.com into the correct folder for whoevers blog it is. When you write a comment- you leave www.bengfort.com and go to beta.blogger.com/comments- which then publishes the new html and sends it via ftp to the website. When a Bengfort.com Blogger signs into Blogger, they leave www.bengfort.com to create and publish their posts, then come back to view it. The only thing that happens on www.bengfort.com is the viewing of the blog.
There are benefits of using this method:
The Blog can be searched for on Blogger.com (I think)
Each Blog can have its own template and style that the girls wish- and they can do it without knowing HTML, because the minor things like navigation I can do myself. All they have to do is choose their template from the 26 on blogger.
I don’t have to do anything with RSS, run any applications on the server, or install anything into the domain for it to work- plus we get to deal with professionals, not a developing engine that I would be working on.
This is quick and easy, and linked to our google accounts.
However, these benefits can be annoyances, and there are some desirable aspects of having my own PHP, MySQL, Apache engine running on the server.
With a little work, I can index the blog on several websites including major blog search websites to expand readership. Also we would have to maintain our readership through ohter advertising of some sort. Essentailly in time I could counter the affect of the blogger search.
Blogger search only works in blogger.
Although the girls can choose their own basic template, they can’t personalize it any further. I could design and create templates for the girls that would be much more unique than the blogger website, while still maintaining the feel of the Bengfort website. It leaves all the design in my court- but in the end it would be a much more personalized solution.
We wouldn’t have to leave bengfort.com in order to blog
Easier website navigation, etc.
RSS applications are not necessarily what I want running with our blog. I would prefer that people go to the website and actually read it online, but if folks did use an RSS application- I could set up the site for use with it. I would also allow RSS into facebook, and other web-based applications
I would have full and better control over the website- and I wouldn’t be “blocked by the chinese government…”
My intitial reaction to build my own engine was when Devi couldn’t log into Blogger from China. We originally suppossed that was because the website was blocked so I decided to build my own engine that wasn’t blocked. However, Devi is now allowed onto blogger- so there is not so much a time issue, and we can take a good hard look at the pros and cons of using a pre-packaged solution vs. my own engine.
Of course, I’m leaning towards building my own: it would get me down and dirty with code I have never learned, and allow me to take full credit for my site, which would be nice. But I think an open dialogue about what is best for the site is needed. Please leave me comments with any pros, cons, concerns, applause that you can think of.
*Because we are using Blogger currently, I will probably refer to blogger as “the pre-packaged solution”.
The comment on the last post is a good one and the question: “Why not just use a pre-packaged solution like Wordpress?” is the central question for the next phase of www.bengfort.com evolution.
Before I start: I just want to say that I am about to review ExpressionEngine, Movable Type, TextPattern, WordPress, and Blogger and present a comparison of those pre-packaged solutions in the next post. The question for today’s post merely compares the suitability of using my own created blog engine vs. using a pre-packaged solution*.
Currently we are using a “pre-packaged solution”- blogger. As you read this post, you are reading a post that was created by blogger using the blogger engine, database, and server- that posted an html page via ftp onto www.bengfort.com into the correct folder for whoevers blog it is. When you write a comment- you leave www.bengfort.com and go to beta.blogger.com/comments- which then publishes the new html and sends it via ftp to the website. When a Bengfort.com Blogger signs into Blogger, they leave www.bengfort.com to create and publish their posts, then come back to view it. The only thing that happens on www.bengfort.com is the viewing of the blog.
There are benefits of using this method:
- The Blog can be searched for on Blogger.com (I think)
- Each Blog can have its own template and style that the girls wish- and they can do it without knowing HTML, because the minor things like navigation I can do myself. All they have to do is choose their template from the 26 on blogger.
- I don’t have to do anything with RSS, run any applications on the server, or install anything into the domain for it to work- plus we get to deal with professionals, not a developing engine that I would be working on.
- This is quick and easy, and linked to our google accounts.
However, these benefits can be annoyances, and there are some desirable aspects of having my own PHP, MySQL, Apache engine running on the server.
- With a little work, I can index the blog on several websites including major blog search websites to expand readership. Also we would have to maintain our readership through ohter advertising of some sort. Essentailly in time I could counter the affect of the blogger search.
- Blogger search only works in blogger.
- Although the girls can choose their own basic template, they can’t personalize it any further. I could design and create templates for the girls that would be much more unique than the blogger website, while still maintaining the feel of the Bengfort website. It leaves all the design in my court- but in the end it would be a much more personalized solution.
- We wouldn’t have to leave bengfort.com in order to blog
- Easier website navigation, etc.
- RSS applications are not necessarily what I want running with our blog. I would prefer that people go to the website and actually read it online, but if folks did use an RSS application- I could set up the site for use with it. I would also allow RSS into facebook, and other web-based applications
- I would have full and better control over the website- and I wouldn’t be “blocked by the chinese government…”
My intitial reaction to build my own engine was when Devi couldn’t log into Blogger from China. We originally suppossed that was because the website was blocked so I decided to build my own engine that wasn’t blocked. However, Devi is now allowed onto blogger- so there is not so much a time issue, and we can take a good hard look at the pros and cons of using a pre-packaged solution vs. my own engine.
Of course, I’m leaning towards building my own: it would get me down and dirty with code I have never learned, and allow me to take full credit for my site, which would be nice. But I think an open dialogue about what is best for the site is needed. Please leave me comments with any pros, cons, concerns, applause that you can think of.
*Because we are using Blogger currently, I will probably refer to blogger as “the pre-packaged solution”.
Recent Comments