History: Advice for alternatives

If you are building something like WikiSuite,

Do your proper due diligence

You will invest a crazy number of hours in this. It is a wise investment to do thorough research into all the Alternatives. Is there really nothing out there which corresponds to your vision?

Think about the project as a whole

It's not just the code. You'll be running a full-fledged organization.

Here is an example to illustrate the various roles and responsibilities in a large software project: https://tiki.org/Teams

Recommend reading:

• https://producingoss.com

Don't underestimate the integration challenges

Think of the flow from the end user perspective as they move from feature to feature.

Be in this for the long run

End users will have all their data in this. You need to do this having in mind to support it for the next 20+ years

Know when to build vs integrate

Developers want to jump in and code. Be careful: it's not just building it, it's supporting it for the next 20+ years

Pick all major components before you commit to them

WikiSuite was announced in 2011. There were several iterations before getting to today's list of components. Sometimes, changing one component has a cascading effect.

Deal with the overlap

• Tell end users when to use each one.