Latest version in production?

[Potherca]

There is a typo in the UI, "Applictions" is missing an a.

This seems to have been fixed in the repo here:

4cb5e6d#diff-29c7b4a1584ea9cefd8b9b40b4ebe3d286091b33d192d09d7ecc545beb6d42d3L157

Maybe the site has not been updated?

[jeff-zucker]

Sorry, I'm behind schedule and haven't figured out how I want to sync between github and the pod so, as of now, you are right, they are out of sync.

[Potherca]

Should we start thinking about automation, or is that still too early?

[jeff-zucker]

Should we start thinking about automation, or is that still too early?

re automating the upload of the data - I am investigating github actions to automate posting to the pod on merge, need to set up the repos first (this repo will be for the app, the other repo will be for the data).

re automating the catalog itself - I will be uploading a roadmap and other notes this week. Automation is definitely in the plan but I think we need to pin down the shape and get it working as a static RDF first. Later today I'm going to upload my proposal to use an ADMS/DCAT profile to define the shape and structure of the catalog. ADMS is specifically designed to work with aggregation.

[elf-pavlik]

I assume the automation would be to deploy the catalog app automatically whenever the main branch changes.

I also understood that all the catalog data work has moved to https://github.com/solid/catalog/

[jeff-zucker]

Yes, correct, the automation would be to post changes from both repos to the pod on merge. The RDF, SHACL, and SKOS files will be uploaded from https://github.com/solid/catalog/ and the JavaScript, HTML, and CSS will be uploaded from https://github.com/solid-contrib/catalog/ and all will end up in https://solidproject.solidcommunity.net/catalog/. That will allow separation of the app from the data and structure.