Post

This kind of thing really resonates with the website builder structure I'm interested in.

anna πŸ‚πŸπŸŽ@anna.germnetwork.com

Okay I think primarily it's that I want two things able to be plugged inβ€”I want my friends to be able to easily upload project information (photos/description/title), and I want separately to be able to craft a custom website that they like that consumes that data.

In particular, I'm super excited about the idea of allowing easy cycling through different website themes, with your data already plugged in. (So you're not just previewing a template theme, you're looking at your already-fully-built website, in this new theme.)

anna πŸ‚πŸπŸŽ@anna.germnetwork.com

That way if any friend wants to hire a web dev/designer to make a really fancy new site for them, they don't need to start from scratch. They can just leave their projects plugged in, and the web dev can consume the data to make the new site. So I'm in the market for strong, from-scratch flexibility

And with easy implementation of website themes, it's easy to commission your own personal designer, or... even more exciting... it would integrate perfectly with an open theme marketplace!

Mathew Lowry@mathewlowry.eurosky.social

All I want for Christmas is an ATproto site Theme library: a marketplace of site lexicons (blog, hub. newsletter, digital garden), each with a marketplace of design themes.

0 reposts3 likes

Also, in the realm of the atproto artistic marketplace, want to flag that @rpg.actor has been talking about how to support commission requests! (And they have already implemented artistic provenance.)

rpg.actor@rpg.actor

We've been having this conversation too! Few folks been hiring or wanting custom sprites for their rpg.actor characters, and we're trying to figure out the right way to connect wires for everyone. We already have paired records for artistic provenance, but trying to figure out commission requests.

Yeah, it seems there are several layers that you could standardize (the more you standardize, the simpler to start, and harder to customize): 1) the atproto schema (like the database schema that WordPress standardized)

2) if you have a fixed set of HTML templates that get rendered you can still switch the CSS (a la CSS Zen Garden) 3) and if you even fix the CSS, you could still have sliders and color pickets etc to modify CSS variables.