| News | |
 |
Latest |
|
Archive |
|
Community news |
| Articles | |
|
C++ |
|
Communities and Content |
|
Databases |
|
Editorials |
|
Emacs |
|
General |
|
HTML |
|
Java |
|
Notices |
|
PHP |
|
XML |
| Links | |
|
Apache |
|
C++ |
|
Database |
|
General |
|
HTML |
|
Java |
|
Javascript |
|
Linux |
|
Object oriented programming |
|
Open source |
|
Perl |
|
PHP |
|
Python |
|
Ruby |
|
SOAP |
|
XML |
|
Suggest a link |
| About | |
|
Advertise on zez |
|
Contribute |
|
Contact us |
|
About zez |
Planning Your Site - Community Building Part 2 |
Existing Solutions
Get one which is open, one you can hire someone to customize. You'd be surprised to learn how often developers put in arbitrary limits to their software. Some are intentional ("We'll make someone pay for that development themselves."), some are more practical ("Only 1% of our customers have ever requested that.") and then there are just things left out because no-one thought about it.
An example of an limitation, you have a department store, you get a shopping system and start off trying to create a virtual representation of your store on-line.
Unfortunately the software you bought doesn't help you out. It talks about categories or departments. Fine thus far, but consider this. You're selling shoes and clothes (among other things), and you have the following departments:
Then you'll add different articles of clothing:
The software you've bought will now require you to add the following "departments" to your apparels department, within each existing I might add:
We're ending up with a hierarchy of stuff which shouldn't be modeled as a hierarchy. A shoe might be for men and be casual. Those are attributes of an object.
You're still set on shopping around? Unfortunately you don't know what you're looking at, and the pitfalls are many. You might want to hire someone to help you out with your specific needs, but read on first.
Comment List
There are no comments.
