I think we’re on the same page.
But there was initial misunderstanding.
By (re)building an additional site our interest is not to double the workload - the absolute ideal situation would be a setup that allows parts of ER to act as CMS for the site. (e.g a wiki page would serve up blocks of content but redact comments, in a way that is stylistically more accessible). Technically, we could just write a page scrapper with something like python but I’d say this is less than ideal - some technical understanding from [elf Pavlik] and [Matthias] of what options are available would be useful. RSS, JSON, etc?
I don’t see creating an additional site for unMonastery as a move away, I see it as a lightweight portal, through to EdgeRyders, individual websites, social network profiles and the networks of individual’s. Similar to the way that twitter is utilised by ER and other organisations to drive traffic in different directions.
“Edgeryders (not just teh website, but the community and the company)”
I agree but I felt in someways this was lost in the points that were being made - and this is what I was gesturing towards when I said there needs to be a service design approach to user journeys. It’s worth saying that some of the most valuable members of the ER community don’t post or read very often/ever, but I don’t believe that they feel any less a part of the network and when it comes to the moment when they’re needed, our workflow seems to bring them in at the right time.
“If the platform is underperforming, it is likely to be because building good platform is very expensive and hard. This means it will probably be hard for you too.”
It is hard but there are varying gradients of difficulty, drupal development is really hard in the context of platform utilised by a diverse group, a (relatively) straightforward presentation platform less so, we’re not aiming to construct any kind of workspace - more similar to what the EdgeRyders business site is aiming for, which as a front of house requirement, I think it is essential.