NAYAN’S ENGINEERING JOURNAL
Notes worth keeping.
Ideas worth sharing.
My collection of practical guides on React, Angular, JavaScript, frontend design, performance, technical SEO and reliable delivery. Explore a topic, follow an example, and check the details.
103 GUIDES IN THE JOURNAL / 12 ON THIS PAGE
Engineering articles
A Frontend Release Checklist That Checks the Actual User Journey
Review content, navigation, responsiveness, metadata and the deployed artifact without confusing a green build with a finished release.
A Technical SEO Page Audit You Can Repeat Before Every Release
Inspect the response, visible content, metadata, links and indexing signals with a small, repeatable page-level audit.
Accessible Dialog Focus: Open, Close and Return Predictably
Plan focus behavior for modal dialogs using native HTML capabilities and a clear dismissal path.
Accessible Form Labels: Clear Names for Every Field
Connect visible labels to inputs, preserve useful hints, and avoid forms that depend on placeholders.
Accessible SVG Icons: Decorative Shapes and Meaningful Controls
Give icon-only actions a clear name and prevent decorative SVGs from adding repetitive screen reader output.
Add a Skip Link That Actually Reaches the Main Content
Let keyboard users bypass repeated navigation with a visible, reliable link to the page’s main content.
Add Parallax Depth Without Taking Over the Reader’s Scroll
Keep ordinary scrolling intact while giving decorative layers a restrained sense of depth.
Angular Signals: Keep Source State and Derived Values Separate
Use writable signals and computed values to express small, understandable reactive relationships.
Article Structured Data Should Describe What Readers Can Verify
Connect article titles, authors, publication dates and images to visible editorial facts instead of filling fields with guesses.
Build a Simple FAQ Accordion with Details and Summary
Use native disclosure elements for compact supporting content without hiding the page’s main answer.
Build Accessible React Components from Native HTML
Preserve labels, keyboard behavior and predictable IDs as interfaces become reusable components.
Build an Accessible Heading Structure Before Styling Your Page
Plan headings as a readable outline, then style their appearance independently from their document level.
Put a useful idea to work.
Try the browser utilities in my developer toolkit.