-
MODX Staff
- 10,725 Posts
There’s a painful balance that must be struck when developing a web community using a CMS tool. I’ve developed or been involved with development projects for web communities for some very large organizations, including assisting in developing some early forms of CSC’s Communities of Practice extranet portals, as well as attempted to develop some with many YAPS (Yet Another Portal System; though I refer mostly to PostNuke and then MD-Pro in my experience). Though the YAPS solutions tend to make it easy to get started, extending these systems is quite a challenge and at times seemingly impossible. With MODx, currently, it would be a little bigger start-up curve, as you need to take control of the simpler activities take for granted in YAPS, such as user registration processes, user security, community organization, and more. But once you have the foundation in MODx, extending and expanding your community is only as difficult as the task at hand. The flexibility of MODx helps you take those communities to the next level, unhindered by the rules imposed by a typical YAPS architecture, but you need to do a little construction and customization to get the foundation ready.
So, your only limits are your MODx knowledge, your PHP skills, your XHTML/CSS skills, and your ability to imagine your community. If you need assistance with certain portions of the process, understanding how portions of MODx work, or anything else, feel free to ask more specific questions (i.e. how do I setup or customize the WebSignup snippet to do this or that?); this community is wonderful at providing support and feedback on your ideas.
