feat(docs): interactive render-blocking demo on Find render-blocking resources - #92
Open
nucliweb wants to merge 1 commit into
Open
feat(docs): interactive render-blocking demo on Find render-blocking resources#92nucliweb wants to merge 1 commit into
nucliweb wants to merge 1 commit into
Conversation
…resources Add an interactive render-blocking-timeline demo (self-contained page under public/demos/ following the documented embed contract) that lets the reader compare a render-blocking setup against an optimized one and step through when First Contentful Paint can happen in each. Embed it in Loading/Find-render-blocking-resources in place of the mermaid sequenceDiagram, which rendered too wide to fit the viewport and could not convey the temporal behaviour it described. The resource-type table and the optimization decision-tree flowchart stay as-is.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What
Replaces the mermaid
sequenceDiagram("Render-blocking timeline") onLoading/Find-render-blocking-resourceswith an interactiverender-blocking-timelinedemo. The reader switches between a render-blocking and an optimized setup and steps through when First Contentful Paint can happen in each.public/demos/render-blocking-timeline.html, following the embed contract inpublic/demos/README.md(postsdemoHeight, syncs theme, no external dependencies).flowcharton the page are kept as-is.Why
The
sequenceDiagramrendered too wide to fit the viewport and, being static, could not convey the temporal behaviour it described (blocking resources delaying first paint). Second demo in the "convert temporal mermaid diagrams to interactive demos" initiative, after Script-Loading.Before: the static mermaid it replaces
sequenceDiagram participant Browser participant HTML as HTML Parser participant CSS as CSS File participant JS as JavaScript participant Render as Renderer Browser->>HTML: Start parsing HTML HTML->>CSS: Discover <link rel="stylesheet"> Note over HTML: PAUSE parsing CSS->>CSS: Download CSS CSS->>CSS: Parse CSS CSS-->>HTML: CSS ready Note over HTML: RESUME parsing HTML->>JS: Discover <script> (no defer/async) Note over HTML: PAUSE parsing JS->>JS: Download JS JS->>JS: Execute JS JS-->>HTML: Script complete Note over HTML: RESUME parsing HTML->>Render: Parsing complete Note over Render: Can start rendering Render->>Render: Layout + Paint Render-->>Browser: First Contentful Paint (FCP) Note over Browser,Render: User sees contentAfter: the interactive demo
Verification (runtime,
next dev+ productionnext build)demoHeight: 454 to 465px, above the 400px minimum; full width without horizontal overflow on desktop.next buildpasses; MDX compiles and theDemoimport resolves.Not included
llms.txt/llms-full.txtare not regenerated here (deferred to the counts/artifacts phase).