You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I remember discussing this with Chance when we extracted examples from the main remix repo, but we didn't have a chance (🥁) to follow up on the idea, so logging it here to see if it gets some traction.
What if we added a dedicated examples section on the site, automated by the CI, to give them more visibility ?
We'd scan entries in the examples repo and read the various package.json files to generate a JSON data file.
An index page with the list of examples with their name, description, keywords, code sandbox link, create-remix cmd, etc.
An input field on top of that to be able to filter out the list.
We could also exploit proprietary fields in the package.json files to do all sort of things, like categorising or whatever, if needed.
WDYT ?
The text was updated successfully, but these errors were encountered:
I like this idea @machour! It could potentially live alongside the resources. I'll need to keep thinking about it, but thanks for opening up this issue to get the conversation started
I remember discussing this with Chance when we extracted examples from the main remix repo, but we didn't have a chance (🥁) to follow up on the idea, so logging it here to see if it gets some traction.
What if we added a dedicated examples section on the site, automated by the CI, to give them more visibility ?
We'd scan entries in the examples repo and read the various package.json files to generate a JSON data file.
An index page with the list of examples with their
name
,description
,keywords
, code sandbox link, create-remix cmd, etc.An input field on top of that to be able to filter out the list.
We could also exploit proprietary fields in the package.json files to do all sort of things, like categorising or whatever, if needed.
WDYT ?
The text was updated successfully, but these errors were encountered: