On Mon, Apr 11, 2011 at 10:06 AM, Jeff Lasman <jpli...@nobaloney.net> wrote:
> On Monday, April 11, 2011 09:18:42 am Peter Manis wrote: > > > It could be done in wordpress without changing much of the design, you > just > > use categories to separate the different types of data. > > "Could be" or "Should be"? > > Isn't this a bit like using a screwdriver to hammer in a nail? Sure it > could > be done, but it's not good for the screwdriver and it's hard to get the > nail > in straight exactly the way you want it. > That isn't really a good comparison to use for this. You are going to have to modify both a CMS and Wordpress in most cases, either with plugins, themes or custom code it isn't just picking something that is what it is and using it. Using things for their intended purpose is not always the best approach, why not be innovative or following those being innovative and use something that might end up being the better solution. Yes, using a screwdriver to drive a nail is not a good idea, but saying, "Hey, if I just make this new 'plugin' for this screw driver, this single handle can be used for a hammer, or a screw driver and prevent the person from carrying both around" might be the best approach. > > Could it be done as quickly as with traditional CMS? I think if I got > proposal from someone offering to do this in WordPress I'd either say "why" > or > skip that designer entirely. > So I ask you, "why should this be done in WordPress"? And "because it can > be" > is probably not a good enough reply. > I was simply replying with it could be done with minimal changes, which you assumed was not true. I didn't say it should be done with it. This is like asking why anything should be done with one over the other. There usually isn't a single answer. It depends on the needs and skills of those using it. Wordpress is pretty simple to work with, so you could save money going with it over having someone do it in Joomla, but it doesn't mean it is the right choice. My comments are based on personal experiences. Instead of saying "Wordpress isn't a CMS, I won't use it for that" I have used it for several things as experiments or because of financial limitations of the client and it worked out well, but I don't think it should be used for everything. Really it comes down to selecting what it right for the client. This thread is about pointing to a couple solutions, but as part of the process of working with the client multiple solutions should be evaluated for their specific project. I am simply saying instead of making things cut and dry about what is and is not created for an intended purpose you should keep an open mind and do what is right for the client. > Jeff > -- > Jeff Lasman > Post Office Box 52200, Riverside, CA 92517 > Our jplists address used on lists is for list email only > Phone +1 909 266-9209, or see: "http://www.nobaloney.net/contactus.html"; > _______________________________________________ > LinuxUsers mailing list > LinuxUsers@socallinux.org > http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers >
_______________________________________________ LinuxUsers mailing list LinuxUsers@socallinux.org http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
