So I’m developing the sites again, trying to figure out what broke the story creation process on the original site, and I get to thinking. As I’m basically rebuilding from scratch trying to find the problem here I was wondering what I can do to make things better. This goes through from content viewing to content creation. It’s difficult though as I can’t do much as I wanted. I’m just trying to get through it all.
I’ve been trying for instance to do from scratch what I used modules for in some cases before. Trying to limit the number of modules needed SOUNDS like a GREAT idea. Use some panels and views and you SHOULD be able to pull it off. What’s not to improve on with that sort of thing. But the thing is that I’m not a coder, and I’m not sure how to go about recreating functionality that a module already makes use of.
There are some that will always say that you need to minimize the number of modules used. The more you use the slower things get. And there is a good logic behind this. Fewer modules means fewer resources. But at the end of the day you are really trying to prototype, deploy and maintain as easily as possible. For a lot of us, myself included, that means you have to look at things from the perspective of what you can do.
Taking that into account and looking at it fact is that the basic site needs really only need a few modules to run in general. The rest of the modules are just integration of other items and the like. Things like CKEditor, Fivestar voting, Disqus comments, and Twitter/Facebook integration are all just modules that really you don’t do anything but set and forget hopefully. They can’t be modifier and frankly it’s best to just use an available module for them.
Everything else really comes down to a couple of modules, views and panels. Everything else is for all intents and purposes an extension of these modules. When you figure that, it becomes less about finding more modules and more about creating more views. That way things turn out better.