Asset catalog prototype

[mattrosno]

Summary

As a development-driven prototype, build a prototype for the asset catalog backed by real data from GitHub repositories.

1. Determine if the prototype should be built with Gatsby 4 or Next.js
2. Define the schema to classify libraries and assets
3. Apply schema to Carbon core (and possibly PAL) libraries through forked/branched GitHub repositories
4. Fetch that data to populate the various asset catalogs, catalog filtering, and entries in each catalog

Job stories

• When I know the type of asset that I'm looking for but not its name, I want to browse assets visually so I can find the asset I need without knowing the exact asset name or details. carbon-job-stories#24
• When I'm looking for an asset, I want to find assets based on what kind of asset they are (elements, components, patterns, shared services, etc.) so that I don't waste time looking for assets that are inappropriate for the problem at hand. carbon-job-stories#28
• When I already know what asset I'm looking for, I want to sort assets alphabetically so that I can find it quickly. carbon-job-stories#31
• When I'm searching for a solution for a user need, I want to see fully-qualified assets (status, framework, maintainers, dates, usage, etc.) so that I can find the asset I need. carbon-job-stories#23
• When I'm looking for an asset, I want to look at only assets that are stable and trustworthy so that I don't waste time with looking for assets that are unstable or that I and my development team won't trust. carbon-job-stories#27
• When I'm looking for an asset, I want to find assets based on what kind of asset they are (e.g. input, navigation, information, container) so that I don't waste time looking for assets that are inappropriate for the problem at hand. carbon-job-stories#29
• When I'm looking for an asset, I want to rank assets by usage so that I can prioritize assets the community trusts the most. carbon-job-stories#30
• When I'm looking for an asset, I want to see assets by last updated so that I can prioritize assets that are more recently updated, and thus likely fresher and more supported. carbon-job-stories#32
• When I'm browsing an asset catalog without having logged in, I want the catalog to initially show the system's highest quality and most used assets so I can get a feel for how others use the system. carbon-job-stories#49

Success measures

• Decisions made: React framework
• Concepts proven: remote, versioned, GitHub content
• Outstanding issues and questions identified to address in a follow-up sprint

Definition of done

The follow items don't need to be "done done" in the prototype to hit the success metrics:

• Browsers and devices other than Chrome
• Accessibility (screen readers, keyboard navigation, etc.)
• Design pixel precision, especially when the underlying issue is with a Carbon component and outside the scope of the platform squad to fix

Tasks

• Create initial Next.js app #10
• Populate web app with catalog data from remote repositories #11
• Add initial standards and assets routes and UI shell side nav to prototype #24
• Generate library and asset routes and populate with unstyled content #30
• Optimize images coming from remote repositories #34
• Host asset catalog prototype someplace #28
• Create components needed for asset catalogs #12
• Asset catalog item components for prototype #31
• Asset catalog pagination for prototype #33
• Catalog search, sort, filter, pagination #135
• Asset catalog filtering components for prototype #32
• Apply schema forked open-source Carbon libraries/assets #16
• Apply schema to forked PALs #29

[mattrosno]

From @theiliad https://www.kenny.engineer/blogging/gatsby-v4-dsg-on-netlify