Create workflow to list all repos with their descriptions and URLs to list on "product page"

[lwjohnst86]

e.g.:

gh repo list seedcase-project --json name,description,homepageUrl,repositoryTopics --visibility public --no-archived --source --topic website,project

So that way, we can always list the products we are building by using repository topics as a way to include them on our product page.

[signekb]

Based on me and Luke's discussions on Discord, something like this, maybe?

Four pages (all in navbar): Roadmap, Products, Platform, Examples

Roadmap

Work in progress and future repos

• Repo labels/topics: wip
• Repos: Propagate, Garden, other future repos?, maybe on-limit datapackage?

Products

More "user-facing"

• Repo labels/topics: product, package, python?
• Repos: template-data-package, Flower, check-datapackage, Sprout, community, guidebook, design, seedcase-website

Platform

• Repo labels/topics: platform, internal?
• Repos: template-website, zen-do, Soil, Actions, decisions, seedcase-theme, t-squared, spaid, template-python-package, team

Examples

• Repo labels/topics: example-datapackage
• Repos: example-rhesus-monkeys, example-seed-beetle, example-rainforest

Under Roadmap, Products, and Platform, maybe split into packages, templates, and docs?

What do you think, @lwjohnst86, @joelostblom, @martonvago ?

[joelostblom]

Just so I understand, this is not just about a spaid command that is run locally, but also a facelift of the main seedcase webpage? If so, some thoughts:

1. Are "Examples" and important enough part of seedcase that we want to have a separate header for that in the navbar? Could an alternative to put it as a heading under Platform or Products (depending on how we view it)?
2. I like the division into packages, templates, and docs (or something similar).
3. Could the order in the Navbar be Products, Platform, Roadmap, About? To highlight products first.
4. Maybe we want a navbar item that is called Collaborations/Implementations/Projects or something similar where we list projects where seedcase is currently being implemented/used?

[lwjohnst86]

1. I think of "Examples" as what Quarto has in their "Gallery" page, which is also on the top navbar. Something that people can refer to so they can better understand what Seedcase software does.
2. Agreed, except add "Examples" between Roadmap and About.
3. That could go under "Examples". Or maybe rename it to "Gallery" or "Cases"?

[signekb]

@joelostblom Yes; this is about a facelift for the website, using the gh cli to get the repos, their descriptions, and their labels in a json instead of adding them manually as we do currently. We'll use the labels to filter what will be shown on the individual pages.

[joelostblom]

Thanks for the elaboration!

I agree that the examples and collaborations could be listed under the same page. I'm fine with either "Examples" or "Gallery"; I see both used and projects switching between the two. And I agree its useful to include this in order to show off what a data package created with the seedcase tool suite would look like.

Maybe the example data packages could also get a facelift and have generated pages from flower? Then they would be a bit more striking/visually tangible.

Another thing I thought of when contemplating this was how it could be clearer how the different seedcase tools each contribute to different parts of the examples. E.g. when I see an example in quarto, altair, matplotlib etc, my first thought is "how do I do that?". For viz-libraries, it is usually pretty straightforward, copy a code snippet and you're done. Quarto is a bit more involved but a lot of the logic lies in a central _quarto.yml file. I was initially thinking of detailing this in the readme, but maybe it will be noisy and just repeating the same comments in each of them. Maybe it's better to have a page somewhere describing each step in creating a datapackage at a high level with links to the respective package for details; like an overview of what Jenny Bryan would call "The whole game" (I think going through it in detail would be too much and is better referred to individual packages). What do you think?

[signekb]

Nice, it seems like we've reached a consensus, so I've start playing around with this.

I completely agree, @joelostblom: The example data packages need a facelift and need to include Flower as well. If we want the examples to show what Seedcase does, they need to be up to date 🚀

I've added your last comment to new issue, #424, and will reply there.