Repository navigation
Feature complete full-stack application templates with screenshots - #6097
Merged
Merged
Conversation
Contributor
Cloudflare Preview
|
shai-almog
changed the title
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.
Make complete full-stack application templates prominent on the homepage and README. Savor, Parley, Wayline and Skirmish now have a screenshot-led showcase near the top, descriptions of their included Java client/backend/admin features, and links to explore or generate an application. Reuse the real screenshots already in the repository.
Add responsive homepage styling and template-specific interest tracking. Keep Unity as a brief experimental compatibility note outside the README's main choices. Restore the existing theme-interest event, preserve acquisition attribution, and leave the current hero and benchmark comparisons unchanged.
Validation: Hugo build; generated-site build-first routing; Crisp consent/event and acquisition tests; GitHub-rendered README screenshot/link review; Chrome at 320, 390, 820 and 1440px with all four images loading and no horizontal overflow. All four template landing pages returned HTTP 200.
git diff --checkpassed.Public files: README.md, homepage template and its responsive stylesheet. No internal review or analytics files.