Post
Generally my idea is based around easy uploading on the frontend (such that it is easy to keep your info up-to-date) and deep customizability on the web design/dev side bsky.app/profile/anna...
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.
0 reposts5 likes
I want to build my own site for interfacing with all these external tools. (Allowing people to upload projects, manage domains, choose between existing web templates, or delegate authority to a web dev.) My first thoughts would be: * @marque.at for domain management * @wisp.place for hosting
But when it comes to content, I am more in the market for feedback! @standard.site lexicons are an obvious place to start -- although they indicate/allow much of their own formatting and I'm wondering if that limits customizability on the web design side cc @schlage.town since we were discussing!
There's also the @sifa.id project lexicon. If I *don't* use that lexicon to represent projects, I would surely want to create dupe records so that they can show up on sifa as well. Although those records don't seem to allow photos yetπ€ But would be nice to auto-populate your projects from sifa!
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.
I'd love to contribute to the use of these lexicons, so I guess my questions are: * Are there any tools/lexicons I'm missing that could be interesting to interface with? * How do y'all recommend I work with @standard.site? Maybe I support more nebulous project data and/or more structured posts?
@hyl.st @anna.germnetwork.com if someone forked lichen.page and made a new cms frontend etc that would be a dream outcome from my perspective lichen supporting any ssg in the backend does fit the βa webdev can do anything with it modelβ, but it did add complexity in the end too