@f0ssel can we add a new field called Tags or Categories for filtering?

Also, we need an endpoint to fetch one single example. Something like /examples/{exampleId}

Another thing, sorry 😅, I'm missing the icon field.

@f0ssel can we add a new field called Tags or Categories for filtering?

Where would we populate this data from? I don't think we can do much manually, but we could possibly parse the markdown or something.

Also, we need an endpoint to fetch one single example. Something like /examples/{exampleId}

What additional data would you expect to return here, that /template/examples isn't already returning?

Another thing, sorry 😅, I'm missing the icon field.

Okay, I can see if I can grab this by adding something to the examples package on the backend.

Where would we populate this data from? I don't think we can do much manually, but we could possibly parse the markdown or something.

Good question. I really don't know but getting it from the markdown, as you said, using frontmatter sounds reasonable.

What additional data would you expect to return here, that /template/examples isn't already returning?

Yes, all the data is there but let's say the user navigates to the "aws-docker" example page and it has to fetch all the examples, which I'm considering can grow up fast, just to get one result. I think it could be better to have an endpoint to just return an example by ID so it works well independent of the number of examples we have. Not a big thing tho, whatever you think is better.

Okay, I can see if I can grab this by adding something to the examples package on the backend.

Nice! Maybe this could be a markdown thing as well?

What additional data would you expect to return here, that /template/examples isn't already returning?

Yes, all the data is there but let's say the user navigates to the "aws-docker" example page and it has to fetch all the examples, which I'm considering can grow up fast, just to get one result. I think it could be better to have an endpoint to just return an example by ID so it works well independent of the number of examples we have. Not a big thing tho, whatever you think is better.

This dataset is not crazy large is size and static once loaded into memory on app startup. Returning the entire set is already how the package api is made, and it's essentially free for us to return, so I think it would be better to just load the entire set into context once and use it to show separate info pages as well.

Where would we populate this data from? I don't think we can do much manually, but we could possibly parse the markdown or something.

Good question. I really don't know but getting it from the markdown, as you said, using frontmatter sounds reasonable.

I looked and see the tags yaml in the markdown files. I'll parse these and expose them through the API as well.

@BrunoQuaresma both tags and icon are in the API now. Currently none of the templates have icon urls but they can easily be added to the markdown if you have them.