Progress & Gamification

Reading Progress Rail (Sidebar with Read Time)

A small floating side rail that sits fixed in the bottom-right corner of the viewport (hidden on mobile). Shows a thin vertical progress bar, the percent read, and the estimated reading time. Ideal for long-form articles, editorial pages, and docs.

Live preview

Loading preview

No extra dependencies. React 18+ and Tailwind CSS v3+ assumed. Save as ReadingProgressRail.tsx.

Or rebuild it with a prompt

Paste the prompt into the tool you already use. Each version is written specifically for that tool, matched to the same design constraints so the output stays consistent.

Build components/ReadingProgressRail.tsx as a client component. Fixed bottom-6 right-6 z-40, hidden below sm breakpoint, flex-col with rounded-full white/85 backdrop-blur border. Inside: a 1px wide 128px tall vertical rail (bg-[#F0F0F0]) with an inner div transforming scaleY from origin-top based on scroll progress. Below: percent (semibold black tabular-nums) + read time (9px muted). Uses rAF + lerp (0.15). Props: readMinutes. Single default export.

How to use it

  1. Drop once at the root of your article layout or blog post template.
  2. Pass the estimated read time in minutes so the rail can display it.
  3. Hidden on mobile by design. Desktop-first, matches editorial reading patterns.

Other components you might like

Related prompts for progress & gamification

Frequently asked questions

How do I use this component in my project?+

Copy the source file from the "Copy code" button and save it into your components folder. Add any listed dependencies (React 18 or later and Tailwind CSS v3 or later are always required, plus framer-motion or gradflow if the component lists them). Import and render the component wherever you want it. Every prop is optional and defaulted.

Can I customise the design and copy?+

Yes. Every component takes props for its content (headline, subtitle, image URL, CTA, and so on) and uses Tailwind classes throughout, so you can restyle without touching the logic. For deeper design changes, paste the prompt into Claude Code, Cursor, Lovable, Replit, or Codex and describe your brand tokens, spacing, or motion tweaks.

Are the components free for commercial use?+

Yes. Everything on this page is free to copy, adapt, and ship in commercial projects. No attribution required. If you post a public showcase we always appreciate a link back.

Which AI coding tool works best for these components?+

All five prompts produce the same design. Claude Code and Codex are best when you want the component slotted into a project with existing conventions. Cursor is ideal for editing inside your IDE with the file open. Lovable and Replit spin up a fresh preview fastest, useful for a quick play.

Do these work with Next.js, Vite, and Remix?+

Yes. The source files are plain React 18 client components. They run on any framework that supports React 18 and Tailwind CSS v3. If a component needs the "use client" directive (all of them do here, since they use hooks), keep the directive at the top of the file when you paste.