Projects / Portfolio lexicon

[tynanpurdy]

I am working on a Astro powered personal website that pulls all of its data from the personal repo. Is there an existing lexicon that would be suitable for displaying projects or portfolio entries? Also on the table would be a resume lexicon or something good for building a CV. If the answer is no, any thoughts on how such a lexicon ought to be constructed? I could see it being mainly basic metadata, like date and tag and then an attribute for what kind of blob is included (markdown basic HTML react whatever) and then a blob for the actual content so that people can display their projects in any way they wish.

[snarfed]

Hi Tynan! We don't currently have either project/portfolio or resume lexicons. They could be good candidates, and resumes are somewhat structured, but project/portfolio feels pretty vague to me. Do you have a clear sense of the consuming use cases or user stories? And if both seem like minimal ish wrappers around unstructured content like HTML or Markdown, do you know why they'd benefit from being stored in ATProto repos, as opposed to normal web sites like now?

If/when we do want to make lexicon(s) for them, you'd start with a working group. Details: https://github.com/lexicon-community/governance/blob/main/CONTRIBUTING.md#how-do-i-add-a-lexicon

Thanks for asking!

[tynanpurdy]

Great points. Projects I could see an ATmosphere comparative to Behance. In a way, what I am working towards is quite similar to the Behance + Adobe Portfolio workflow where your Behance posts show up on your website. I could also see a great advantage to having project data stored in a PDS. Designers are want to change portfolios or switch providers. Owning the data outside of how it is presented on a website—in a recyclable format—would be quite handy. To a limited extent, the DID signing of work does also attest some authenticity to authorship. What if Framer or Webflow decided to integrate with ATproto? What if I could mention collaborators on a project directly in the record?

[tynanpurdy]

Essentially my repo as a CMS

[tynanpurdy]

And maybe a blob content isn’t the right way to do it, but there’s a balance between prescribing structure and giving creative freedom

[ronentk]

do you know why they'd benefit from being stored in ATProto repos, as opposed to normal web sites like now?

One benefit is the indexing and social graph connection. For the research use case, if I’m a researcher who published a new paper or blog post or even a reading recommendation, I want people to know about it, and just adding a new html section to my website won’t help with that. Yes, a lot of people also share their work on Bluesky/Twitter but a lot of researchers still avoid those platforms. If it automatically goes out to ATProto, it saves time and also provides a different way for people to stay updated (more like RSS?), especially as more apps to discover this kind of content become available.

[ronentk]

Just to chime in that this is a really cool idea and relevant to a use case we’re thinking about at Cosmik - personal pages for researchers. Lots of researchers have template based personal webpages, for example https://academicpages.github.io/. These include publication portfolios, talks, events and so on, and with Cosmik researchers will be able to create those records in ATProto.