Add community-maintained starters discovery page#2224
Open
MDF-1951 wants to merge 1 commit into
Open
Conversation
Signed-off-by: MDF-1951 <mohammedfahim2027@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR proposes an alternative approach to Issue #185.
Rather than linking users to an external page of third-party starters, it introduces a dedicated "Community-Maintained Starters" experience within the start.spring.io UI.
Motivation
PR #261 previously attempted to address this issue by adding a Help menu link to an external starter catalog. During review, concerns were raised that the relationship between the selected Spring Boot version and the linked starter information was not obvious.
This implementation keeps users within start.spring.io and provides additional context around community-maintained starters.
What Changed
Notes
The catalog is intentionally small and serves as a discovery mechanism for community-maintained starters that are not part of the curated Initializr dependency catalog.
Compatibility remains the responsibility of each starter project and users are directed to official project documentation for verification.
The initial catalog contains a limited set of well-established community-maintained starters and is not intended to be exhaustive. The metadata-driven approach is designed to scale incrementally, allowing additional community-maintained starters to be proposed and reviewed through the normal pull request process without requiring changes to the UI implementation.