Improve discoverability with feature/topic tags, e.g. records

[youngledo]

Hi, thanks for building java.evolved. The side-by-side format is very useful.

One thing I noticed while using the site is that some Java features are hard to discover as a group because their related examples can be spread across different categories.

For example, record-related patterns can show up in several contexts:

• basic record usage
• compact constructors and validation
• record-based error/result types
• records combined with pattern matching or sealed hierarchies
• records used in data-transfer or modeling examples

The current category structure is helpful, but when I want to learn or review one language feature end-to-end, I need to search around instead of browsing a focused collection.

Would it make sense to add a secondary organization layer, such as feature/topic tags?

Possible approaches:

• add tags like records, sealed-classes, pattern-matching, switch, streams, etc. to snippets
• show those tags on snippet cards and search results
• add topic pages such as /topics/records that collect related snippets across categories
• keep the current categories as the primary structure, so this does not require duplicating content

For example, a “Records” topic page could list all record-related snippets across Language, Errors, Enterprise, or other categories, optionally ordered by Java version.

This would make the site easier to use both as a reference and as a learning path for specific Java features.

[youngledo]

Adding a possible implementation path, in case this direction sounds useful.

A small first step could be to keep the current categories as-is and add a secondary topics/tags metadata field to snippets. For example:

topics:
  - records
  - pattern-matching

Then the first PR could stay fairly small:

• add topics to relevant content files, starting with obvious record-related snippets
• include those topics in the generated card/data output
• let homepage filtering and search match topics in addition to category/title/summary
• update the content template so future snippets can use the field

For the records example, likely initial candidates would include:

• content/language/records-for-data-classes.yaml
• content/language/compact-canonical-constructor.yaml
• content/language/record-patterns.yaml
• content/errors/record-based-errors.yaml
• content/language/sealed-classes.yaml
• content/language/exhaustive-switch.yaml

That would improve discoverability without changing the existing URL/category structure. A later follow-up could generate dedicated topic pages like /topics/records, but I think topic metadata + search/filter support would already solve most of the browsing problem.