Repository navigation
Show Image Update Monitor on the homepage (0.1.3) - #2
Merged
Merged
Conversation
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.
The English and German homepages now show Image Update Monitor immediately after the facts and before the project list. A real product screenshot, a short explanation about container updates and a link to the product make the benefit visible early.
The preview uses the existing desktop screenshots and the product repository's mobile captures, each in light and dark mode. Desktop shows five container rows; narrow screens show one complete container card. The shared Shot component selects the appropriate capture and serves responsive WebP files. Version and changelog are prepared for 0.1.3.
The build checker also resolves filesystem URLs and normalises route separators correctly on Windows; its existing checks previously failed there despite a successful build.
Validation:
npm ci: no known vulnerabilities.npm run design: no changes to generated styles.npm run build: 19 pages, 18 sitemap entries, all checks pass. GitHub release lookup used the checked-in versions because the local sandbox has no network access.