Work ↓ https://feed.grantcuster.com/post/1655663971/
Almost done with the bare-bones user account and place creation features for the div and CSS building blocks app.
Work ↓ https://feed.grantcuster.com/post/1654088755/
More work on setting up a system of building blocks using divs, text fields, and CSS.
I'm excited about letting users write CSS in apps and this morning I tried to write down why: https://writing.grantcuster.com/posts/2022-05-22-css-as-end/
Work ↓ https://feed.grantcuster.com/post/1652744517/
I keep bouncing off ideas for the next Constraint Systems thing, this isn't quite it... but maybe near.
Work ↓ https://feed.grantcuster.com/post/1651524527/
Some early work on integrating css.gui with Sprout. Getting cautiously excited about the possibilities here.
from https://github.com/components-ai/css.gui
Maybe:
Any edits create a new 'version'. Page creator gets to pick which version is pinned (version seen by default when you visit the page). Edits by page creator are pinned by default...
If I wanted to make a site (or an internet) where anyone could create a page and every page was editable. What are the main editing models I could use?
- page creator has to approve edits (probably more system than I want to create)
- version control so you can go back through each version of a page (doable but I bet people rarely go back much)
- edits automatically create a new page (fork). maybe my top pick but new forks aren't necessarily discoverable.
Anything else I should be looking at?
Going out on a limb. Creative interface experiments at http://constraint.systems. Recent Linux convert. Foster parent. Work and inspiration in progress. He/they.