Documentation — Video Controls Plus | Complete User Guide

The Video Controls Plus documentation hub is the central index for all user guides, tutorials, and reference material. Each guide is task-oriented — "how to set an A-B loop", "how to capture a screenshot on YouTube" — rather than feature-oriented, so you can find the answer to a specific question without reading a chapter you do not need. Most guides are 5–10 minute reads with one or two screenshots and a copy-paste section for the keyboard shortcuts they describe.

Use cases

Looking up a specific task

Use the in-page search or the table of contents to jump to a single guide — for example, "how do I export my notes" or "how do I clear an A-B loop". Each guide is self-contained.

Reading the full reference once

New users sometimes prefer to read the full set of guides end-to-end. The reading order at the top of /docs is the recommended sequence.

Citing a guide in a tutorial or blog post

Each guide has a stable URL and is versioned with the extension. Cite the URL plus the version label and your reference will not break with a future redesign.

Filing a documentation gap

If a topic is missing or outdated, /contact has a "documentation gap" inquiry type. The maintainer triages those weekly.

How it works

  1. Pick a starting point. "Getting started" is the recommended first guide. Power users can skip directly to the feature they care about.
  2. Read the guide. Most guides are 5–10 minutes. Each opens with the keyboard shortcut, then explains the why and edge cases.
  3. Try the steps. Every guide is written so each step can be followed in a real video tab. Open YouTube in another window and follow along.
  4. Bookmark the keyboard shortcut card. /keyboard-shortcuts is a one-page cheat sheet you can keep open while you learn.

Examples

  • A new user reads "Getting Started". Five-minute read; covers install, first speed adjustment, first A-B loop, and where to find advanced settings.
  • An advanced user looks up "Audio normalization". Three-minute read; covers Alt+N to normalize, the cap differences across services, and how to set a per-site default boost.

Frequently asked questions

Where should I start?

Read /docs/getting-started first. After that, the recommended order is speed-control → ab-loop → audio-boost → filters → screenshots → notes.

Are the guides versioned?

Yes. Each guide labels the extension version it was written against. Older versions of the guide are not preserved publicly; the newest version always wins.

Are videos embedded?

Some. Where a screen recording adds clarity, the guide embeds a 30–60 second clip. The text is always sufficient on its own.

Are translations available?

Currently English only. A translation contribution flow is on the roadmap; community PRs adding language files are welcome.

Can I print a guide?

Yes. Ctrl+P (Cmd+P on Mac) produces a clean printable layout. The cheat sheet at /keyboard-shortcuts is the most commonly printed page.

How is the documentation kept current?

Each guide is reviewed on every major version bump. Inline "verified in vX.Y" labels show when the guide was last reviewed.

Tips

  • Skip the chapters you do not need; the docs are not designed to be read cover-to-cover.
  • Bookmark /keyboard-shortcuts and /faq — those two pages cover 80% of repeat lookups.
  • Every guide has an "Edit this page" link at the bottom that links to the source on GitHub for documentation contributions.

Limitations

  • No translations yet.
  • Some advanced developer-facing topics (manifest internals, content-script architecture) are documented in the GitHub repository, not on the public site.
  • The guides assume a default configuration; if you have heavily customized your bindings, the screenshots may not match.

Last updated 2026-05-06 by Ahsan Mahmood, maintainer.