- Joined
- Jul 21, 2005
- Messages
- 10,479
I have a love/hate relationship with vBulletin forums. They are extremely powerful and currently dominate the professional forum market (for good reasons). However, I feel that vBulletin has stagnated in the last while. It has reached the point where the team insists on patching up an ancient core over and over rather than overhauling for the modern age.
I am beginning a project codenamed "vBuzzetin" (no, it will not be called that in the end). It will take a few years to complete (especially if I am forced to code the project entirely alone), so, don't get your hopes up that this project will have releases in the next while. I am here to ask for your guys' opinion of vBulletin. What do you like about it? What needs to change?
In offering your suggestions, keep the ideas on the large scale. Ideas like "the User CP link is too small" are not what I am talking about. I am referring to things that span across all vBulletin communities. One prime example would be "the admin control panel (for those who have seen it) is too blasted complicated/cluttered with too many options". To help you spark a few ideas, here are my primary goals with this project.
- open source + free: I am bit tired of vBulletin's ridiculous license costs
- standards-compliant code: This is fuzzy to the casual Internet user, but programmers will welcome this change greatly (table layouts must die); sites will load much faster thanks to standards-compliant code
- better content management functionality: It pains me to see a "site" built around strictly forum threads. The ability to add actual site pages inside the forum framework needs to be simplified.
- native blog support: Again, vBulletin charges an extra fee for blog enhancements. I believe these features should be built in.
- Web 2.0 quality: Needs moar AJAX
- less bloated back-end: vBulletin is just too slow. It loads up far too much junk before doing the simplest operations.
- simpler template system: Making a forum skin is a royal pain. This process should be simplified to where any web designer can put something together.
I realize many of these sound really technical, but you don't have to be. Just share your thoughts with me.
I am beginning a project codenamed "vBuzzetin" (no, it will not be called that in the end). It will take a few years to complete (especially if I am forced to code the project entirely alone), so, don't get your hopes up that this project will have releases in the next while. I am here to ask for your guys' opinion of vBulletin. What do you like about it? What needs to change?
In offering your suggestions, keep the ideas on the large scale. Ideas like "the User CP link is too small" are not what I am talking about. I am referring to things that span across all vBulletin communities. One prime example would be "the admin control panel (for those who have seen it) is too blasted complicated/cluttered with too many options". To help you spark a few ideas, here are my primary goals with this project.
- open source + free: I am bit tired of vBulletin's ridiculous license costs
- standards-compliant code: This is fuzzy to the casual Internet user, but programmers will welcome this change greatly (table layouts must die); sites will load much faster thanks to standards-compliant code
- better content management functionality: It pains me to see a "site" built around strictly forum threads. The ability to add actual site pages inside the forum framework needs to be simplified.
- native blog support: Again, vBulletin charges an extra fee for blog enhancements. I believe these features should be built in.
- Web 2.0 quality: Needs moar AJAX
- less bloated back-end: vBulletin is just too slow. It loads up far too much junk before doing the simplest operations.
- simpler template system: Making a forum skin is a royal pain. This process should be simplified to where any web designer can put something together.
I realize many of these sound really technical, but you don't have to be. Just share your thoughts with me.