Here we explore wqhat's involved in creating a new site. Currently this is for devs and design purposes. Later it will be for writers.
# Registration of membership When a stranger who is not in the wikiverse finds one of my wiki.cafe sites, can they create a wiki .cafe site directly from that location? - They will need to be offered membership in wiki.cafe. - They will need an oAuth login.
wiki.cafe will need: - a **member-registration** process (triggered by an OpenCollective subscription) - which issues **oAuth login credentials** and which - **pops up** whenever a reader of a wiki.cafe site follows the standard protocol of wiki, which is to spin-up a site on the same server as the site they first encountered, by entering a new url under the same domain.
Operational questions: - Does our **Keycloak machinery** support this transparently and reliably? Is it production-ready? - Do we need a **staffed location** aka helpdesk/front office, where the manual processes are carried out, and members are entered into a registry and issued with credentials? Do we intend to automate this from the start? Maybe SSO? - Do we have standard subscription rates (eg a **basic individual account**, with a defined *maximum of sites* and a defined *envelope of functionality aka plugins*) which can be advertised and accessed in OpenCollective? - Are we ready to advertise individual (and organisational) accounts in wiki.cafe? Or is this still alpha development status (like RelocalizeCreativity)? Where do we advertise accounts: OC? Our own website (where is this)? Who maintains this - an *operational role* question for a **Product circle** within the wiki.cafe organisation. Is it time to create this circle, as distinct from the sysadmin traffic? I’ve created a room in our matrix space, and the wiki xxx to support this circle.