Thread

HI all we are going to develop a new blogging application with CI.

We are on initial phase so we need your creative and fresh ideas to be implemented with our APP.

You all are welcome….

Please let us know what the drawbacks with current blogs, and what are the features to be included newly?

Thanks all!

We are doing this for our own good. We realize that there are many blog applications out there, but we all want to progress with out coding. Also, In Lou of the fact that we do have some problems with current blogs, and plus, if we want to re-invent the wheel; why can’t we?

Yes Blaze and InkType are good software, but blaze development has been put on hold it seems, and Developer13 isn’t interested in helpers just yet.

The Blaze license is because Elliot doesn’t feels his blog software ready for production. He mentioned when it is ready the license will be changed. Your reaction proves people are only going to use if if they really want 😊

Hi, I’m interested in helping you with the application. Some problems I see with blog systems is they don’t understand that a blog is just a newspaper with usually only one author.  That hardly stays true and as the blog tries to grow it ends up dead, The basic implementation of a blog post (title, content, author) is muddled with other data in the database making upgrades difficult.

Another problem is that because Blog systems are so focused on adding features right off the bat the whole system becomes muddled with extensions data that is messily slopped next to basic blog data.

I’ve got more interesting ideas that a blog could use.

Why not create a bloat free blog. Simple, fast, secure and stylish?

Woow!! Thanks for all of your suggestions opinions and all….

“re-invent the wheel”

No brother I’m asking what is good and what is bad with the “inverted wheel” so we can make it more soft running….ha?
while(!(succeed=try())); right?? So we will try!

@ Jemgames

In Lou of the fact that we do have some problems with current blogs, and plus, if we want to re-invent the wheel; why can’t we?

Your are 100% up with the point!!!

@ kowboy
I agree with you sir…. We need to make it simple and cool…. Easy to manage…
You are always welcome bro, I think we need to talk a little more…
I have sent you a PM. Please check that out…

@JasonS
Yes! That what we are going to do…
To make it a success we need your ideas and opinions…

And yes it’s always “GOOD” to do some thing with the intention of learning new areas.
And its “VERY GOOD” if we make it free for community…
And we are “GRATE” because we hope to teach people How to develop a web application from A-Z with video tutorials!!!!

Hope you guys can give us more ideas…

Again thanks for all…

Why not create a bloat free blog. Simple, fast, secure and stylish?

A blog without distractions? Now why would someone want to do that? lol

Ya, seriously.

Who in the world would use a blog without bloat?

Come on now. Let’s be realistic. Or something.

1.) Allow for multiple blogs. Have a ‘blogs’ table, and every post should have a ‘blog_id’ foreign key. User permissions could be set up so access could be restricted per-blog.

2.) Base your theming engine off of Views. There’s always a trade off between having a pure MVC-style app and one that you can distribute and expect people to muck with. Think about theming in Wordpress: You’re essentially calling in posts and plugins for the given template, kinda Controller-ish, but not completely. All WP does on this front is call the template with some vars set. Something like Drupal, on the other hand, favors configuration in the admin over making custom calls from templates, although the latter is still an extra option.

3.) Go for a robust plugin architecture. The beauty of building on CI is that all people would need to do to extend your app is create their own models, views, and controllers. But they need ways to interact with the blog app, most likely via views, models, and libraries. In this respect, you need to develop a solid API for interacting with the core features of the blog app. The other option to consider is an event-driven or aspect-oriented system, whereby plugins can react to events in the blog app and perform actions respectively.

4.) Easy installation. CI can gain ground via your blog app if it is easy for average Joe to download and install, like WordPress.

Those are just a few to consider, and they are certainly things I’m considering for blogenfuego.com 😉 Good luck.