I'm so glad to be in touch again @alberto, despite the fairly extended time lapse in my communication (which is becoming more and more a condition, in this period of my life).
I hope I didn't give the wrong impression with my reply; I totally see the point of your choice and I back it fully (not that you need my blessing... )
My questions were not concerns; rather they came out of genuine interest: I was wondering if you assessed the usage and perception implications of such a big change, as I've been reasoning for quite some time about these and, despite the many opinions, I never got to an ultimate vision.
(I kinda feel some kindly patronizing rebuke coming, here, that I cannot aim to anything "ultimate" for something such organic and ever-changing as a community, but stil... )
I'll be happy to refer to Matt (that's @matthias, right?) for techy stuff but what I meant to ask was more in terms of usability and semantics.
I don't want to be vague though, so let me try expand a bit (and please consider I'm not a Discourse expert, so I might totally miss stuff which is already builtin).
Let's say you want to create a custom page which lists all videos from your Vimeo profile, dynamically, or you want to integrate the Edgesense Dashboard in your website or a page which reports updates happening on your Google Drive documents, a calendar, a ticket/task system... or anything of the sort.
My understanding is that building such dynamic pages is not straight forward in Discourse.
Am I wrong? If not, are you planning to keep this kind of features out of the main platform or not planning to rely on them, at all?
The Discourse model for forums is indeed very agile, it provides excellent content overview and fairly good navigation.
On the other end, being a forum, I feel it tends to "flatten a few semantic dimensions" when compared to a full CMS and, even more, to those with social networking capabilities.
My understanding, from a quick glance at current the re-organization, is that content has been remapped more or less as follows:
sections (or post categories) become forum categories
groups become sub-categories
blog posts and group posts become forum topics, being differentiated from each other via the categories they belong to
static pages become forum topics too, the main difference being that replies are locked
wikis (I couldn't actually find wiki pages yet) are forum topics as well, with special features (and caveats?)
- finally, I assume Discourse's groups will be used to handle private access and custom notifications (but AFAIK they're only managed by administrators)
Is this correct enough as an interpretation?
If that's the case, I assume some stantard concepts, typically existing in social networks, such as the following mechanism, dashboards, group summaries won't be available here. Same goes for blog views and multi-level menus (these last ones being the least missed feature, frankly).
Here's a few links about related topics where doubts and limits are presented, just to give a broader idea:
To sum up, the nature of my question was triggered by this renovation but was, let's say, on a higher level.
I consider you guys the heroes of hyper-active online communities and I'm simply keen to know all I can from stuff you learnt on the way.
Again, I don't want to sidetrack the original topic so feel free to move this elsewhere (I'd open a new topic myself but I'm still not aware of the way you'll structure categories in this new incarnation of ER).