I think we need to start with a few basic topics, in order to organize the communications plan behind the website design.
So… if we follow a simple communication schema, we need to think about WHAT we want to said and to WHO its the message directed to, and only after that (or at least with those answers in mind) we could discuss HOW to deliver our message.
I`ll try to summarize some ideas that I heard in the las two days about the previos questions.
About the “What?”… we could start with a really (but really) basic question, but the general idea its useful for almost every other content: “How we define Tryton ? “
Of course, for developers its really clear (“Is a three-tier high-level general purpose […]”) but, is this an attractive definition for companies/users who wants to use Tryton ? Personally, I think, for example, that a manager reading that definition will never be aware of Tryton’ s functionalities such as accounting or stock, among others. Result: one guy escaping really fast from the website.
So, should we change that definition ? I don’t think so… but at this point its important to note that the “WHO?” Question its becoming a central point. In the las days, we were talking about different “Entry Points” and It could be a good approach, cause it allows us to create different messages for different targets (a different answer to “What?”, defined by the “Who ? “).
Following this scenario, we need to define two concepts yet:
a) Each message content:
Initially, we could think about two potential targets: Developers (the current site content its good for this target) and Companies who are not initially interested in the platform,
but they are on the functionalities (Tryton “as an ERP”, for example).
Considering this, I propose to work on this areas content as “different projects”, and we could even set different teams for each one of them.
¿Why? Cause I strongly think the contents and guidelines should be completely different from each other, so has no sense to treat them as a single speech.
b) How to “split” them:
If we recognize different targets, we need to split different content to each one. So, at this point i can think about two options:
- Two websites: we could use Plone or Drupal as examples and publish a tryton.org and a tryton.com. (If you check those sites, .com and .org has different targets)
- a “Splitter” Landpage: Having a clear path for the user from the beginning.
There just a few ideas, intended to be useful as starting point for discussion.