You can also use the and keys
Deletions are marked like this Additions are marked like this

__under constructiong__

git clone ⇒ page creation

TL;DR: Rough idea: make it possible to interact with Encycla by entirely using the git workflow.

  • User is cloning the yet non-existant page @user/Page_name.
  • The clone contains the skeleton files content.md, CONTRIBUTORS.yml, et cetera.
  • User edits content.md, commits their changes, then pushes the local commit(s) back to Encycla.
  • The page /@user/Page_name is now visible on Encycla.

Authentication — whether by username/password, certificate, or ssh-key — is a necessity in order to prevent spoofing.

I don't know how Encycla works behind the curtains, but perhaps it is easier to implement git interactions via two protocols:

  1. git clone https://encycla.com/*
  • User can clone whichever page from Encycla they want.
  • User can only clone already existant pages.
  1. git clone ssh://encycla.com/@user/*
  • User can only clone pages in their own name space.
  • Cloning a non-existant page will “create” the page as a draft and populate the local directory with the necessary skeleton files, as per the initial description.

Would that work?

Comments