Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Parse readme data into profiles and inject into frontend #536

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
f0ssel opened this issue Mar 26, 2025 · 0 comments
Closed

Parse readme data into profiles and inject into frontend #536

f0ssel opened this issue Mar 26, 2025 · 0 comments
Assignees

Comments

@f0ssel
Copy link

f0ssel commented Mar 26, 2025

This issue hinges on #530, but this issue can still be started async with mock/test data.

We need to add a new step to the build process that takes all user READMEs in the Hub repo, and processes them into JSON payloads for the frontend to display as Partner pages.

As mentioned in #530, each README will have a standard, enforced schema for its frontmatter. But we need to decide if we want to do anything with the main README body, or if we just want to ignore it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants