[TODO: make a nice logo]

Technologies used:

  • Python
  • SQLite
  • REAL XHTML (screw IE)
  • CSS 3 (if we banish IE anyway, why not?)
  • JavaScript: jQuery

Features:

For now just the basic CRUD and template stuff. Oh, and speed and security are very important for me.

Why not stay with the crowd and use PHP+MySQL or follow the hype and use Ruby on Rails?

The question already is part of the answer, I am not a crowd or hype person. I know humans are herd animals, but humans also try to belong to ‘the elite’.  But another reason is that I think PHP is messy(look at the function names!), slow(I know benchmarks are evil…) and noob territory. Ruby is cool, but I feel out of control with rails. Java is cool also, but have these guys ever heard about rapid development? Python is cool but… Well, it’s just cool! Don’t know if that has anything to do with Monty Python’s Flying Circus.

The same is true for MySQL, besides the fact that everyone uses it, it doesn’t adhere to SQL standards. And since I don’t expect my website to become high traffic I want to use SQLite.

[edit]
I stopped working on the CMS for now… I’m buzzy doing other things(like deciding on what I’m going to do next year). I’m also working on another CMS now, which includes in place editing, which means a lot of javascript. I actually call my new CMS a rapid prototyping tool. Maybe I’ll combine all 4 CMSs I made so far into one perfect CMS to finally build my own website.


3 Responses to “About PepSite CMS”


  1. July 31, 2009 at 2:53 pm

    I built my CMS in PHP/MySQL and used Ajax to handle the editing and deleting of articles, downloads, snippets, etc. It’s not entirely secure at the moment because the JavaScript functions are plainly visible to anyone with the will to find them. I authenticate usernames and passwords before any real database interaction occurs, but I’ve never done any work with Python or SQLite.

    I completely agree with you about humans being herd animals. Especially the part in another post about the noob Ruby on Rails programmers.

  2. 2 Nick Wood
    January 6, 2010 at 3:20 am

    It’s good that you’re trying to take advantage of python’s speed, but I don’t think that not following the crowd is a particularly convincing reason for avoiding php and mysql. Also, “humans are herd animals”? Spare me the pontification, please.
    I dont want to be rude, but it’s probably a good idea to support mySQL as well as SQLite. If you want anyone to actually use your CMS, you should make it as user friendly as possible, while maintaining speed, and minimizing file size (as-per your specifications).

    There’s a pretty good framework for python web applications called Django that you might like. Python’s not my thing, but you may find it extremely useful.

    http://www.djangoproject.com/

  3. 3 pepijndevos
    January 6, 2010 at 11:37 am

    I actually never started doing this. I’m now working with Clojure to make a static site generator. Changing interests as ever…

    I never intended for anyone to use it. There are enough good CMSes out there. This was just me telling about my plans probably.


Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s




My blog has moved!

My blog has permanently moved to a self hosted Wordpress at http://pepijndevos.nl

This blog will stay around for accidental search engine visitors.

Me

This is me

Blog Stats

  • 22,233 hits

@PepijnDeVos


%d bloggers like this: