Repository navigation
Show XEvents with real product screenshots and a short walkthrough - #6
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 README previously had only branding artwork and a screenshot capture plan. This adds actual mobile-size Mini App captures and a 25-second silent walkthrough so visitors can see event creation, RSVP management and code-based group check-in.
docs/demo.md. The real frontend and Worker ran against disposable local D1 with fictional identities and events. Telegram launch identity was simulated; all outbound calls were mocked. No production records or credentials were used.Validation: Worker bundle and mocked local integration checks passed; all 46 changed-document file/image links resolve; whitespace checks passed; heuristic credential-pattern scan covered 606 historical blobs and changed text without matches. Images were visually reviewed; MP4 is H.264, 430 × 932 and 25 seconds, with a frame extracted for verification.
This is a sequence of actual screenshots, not a continuous recording or a live Telegram demonstration. Telegram WebView, chat RSVP, live notifications, QR scanning and payments were not manually verified. No application modules, deployment configuration or production data changed. No deployment or merge performed.