Repository navigation
Docs/readme diagram and submission form - #23
Merged
Merged
Conversation
Ready-to-paste title/description/tags for the "Create an article" form, plus an image-generation prompt for the optional cover image (abstract, no text/logos, AWS orange + indigo palette) since that field needs an actual uploaded file this repo can't produce on its own. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… list The boxed ASCII architecture diagram forced horizontal scrolling in the AWS Builder Center article editor (screenshotted: only ~half the diagram fit before the code block cut off). Blog platforms aren't guaranteed to render Mermaid the way GitHub does, so this replaces it with an ordered list that reads the same pipeline top to bottom with no fixed-width box-drawing characters — renders correctly in any Markdown editor. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Replaces the solo-build draft with role-based splits across the three team members (Maha Kisore, Ramkumar, Yashwanth) — correctness core/CDK, client/auth/UI, and observability/notifications/AI respectively. Still flagged for the team to review and adjust before submitting, since this is a drafted split rather than a verified record of who did what. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Timestamped beat-by-beat script covering all four required points from the submission form (about the project, tech stack/architecture, AWS usage, learning/growth) inside the 3-minute cap, built on top of the existing rehearsed demo plan (docs/general/10-DEMO-PLAN.md). Includes a literal transcript per beat, what to show on screen, a timing cheat-sheet, and a fallback cut if something goes wrong live. Narration word counts checked against a realistic ~2.3-2.5 words/sec speaking pace, not just against the raw second budget. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ay split Previous draft skewed toward the team leader (correctness core plus the hardening pass and property tests on top). Rewritten so each person's paragraph is the same shape and depth, and the cross-cutting work (hardening pass, property tests, UI/UX pass) is now credited to all three jointly instead of stacked onto one person. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ecording The original script assumed you'd perform the demo live in real time to fill exactly 3 minutes. Since a real 43-second silent recording now exists (demo-assets/stocksync-demo-silent.mp4), this rewrites the script around it instead: verified timestamps (read directly off the file, via a 1fps contact sheet) for each narration beat's source footage range, plus which frame to freeze and hold to stretch that range to the beat's full duration. Keeps a pointer to the original live-performance version (10-DEMO-PLAN.md) for anyone who'd rather record fresh instead of editing freeze-frames. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… script A real ~3:00 recording now exists (demo-assets/stocksync-full-tour.mp4) covering every shipped feature in order: dark mode, sign-in, the two-counter offline/sell/reconnect/audit conflict demo, the same-field price conflict banner, and a Products/Checkout/Dashboard/Staff tour — all with a visible animated cursor and real data (real arithmetic, a real completed checkout order). Unlike the previous version, nothing here is freeze-frame-stretched; the full 3 minutes is real screen time. Replaces the earlier editing-guide version built around the shorter 43-second recording, which this supersedes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.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
1 participant
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.
No description provided.