Video Controls Plus Documentation Index | Full User Guide

The Video Controls Plus documentation index is the long-form sibling of the /docs hub. Both pages list every guide and tutorial; /documentation is the SEO-friendly alias preserved from the project's pre-2024 information architecture and remains as the canonical landing for inbound links and search results that already index it. Either route reaches the same set of guides — getting started, speed control, A-B looping, audio boost, video filters, screenshots, notes, cloud sync, and the keyboard-shortcut reference.

Use cases

Inbound links from old blog posts and bookmarks

Pre-2024 references point to /documentation. The page is preserved so those references continue to resolve — search engines and human visitors both land on a real page instead of a 404.

Skimming the full set of guides as a checklist

New users sometimes prefer a single index page that lists every guide with a one-line summary. /documentation provides that flat view; /docs is the same content with richer category headers.

Linking to the full documentation in support replies

When a support reply needs to point at "the documentation," the canonical link is /documentation; it shows the whole picture and lets the user pick the right guide.

How it works

  1. Browse by category. Getting started, core features (speed/loop/boost), advanced features (filters/screenshots/notes), reference (shortcuts/troubleshooting).
  2. Pick a guide. Each entry has a one-line summary and an estimated read time. Most guides are 5–10 minutes.
  3. Try the steps. Every guide is paired with a YouTube tab open in another window — read and try in real time.

Examples

  • A new user lands here from a blog post. Old-route URL still resolves; user reads getting-started, then jumps to speed-control, hitting their first three goals in 15 minutes.
  • A returning user looks for a specific reference. Uses Ctrl+F to find "audio normalization" in the index, lands on the audio-boost guide, gets the answer in two minutes.

Frequently asked questions

Is /documentation the same as /docs?

Yes — same content, alternate URL. /docs is the active canonical; /documentation is the legacy alias preserved for old inbound links.

Should I bookmark /documentation or /docs?

Either works. /docs is shorter and matches the active in-app links; /documentation is what older bookmarks already point at.

Where are the developer docs?

In the public GitHub repository. The website documentation is user-facing only.

Are the guides regularly updated?

Yes — every major version bump triggers a doc review. Each guide has a "verified in vX.Y" label so you can spot stale content.

Can I contribute to the docs?

Yes. Each guide has an "Edit this page" link to the source on GitHub. Pull requests are merged on the same cadence as code changes.

Are translations available?

Currently English only. A community translation flow is on the roadmap; volunteer translators are welcome.

Tips

  • Bookmark either /documentation or /docs — both stay live indefinitely.
  • For specific tasks, search the page rather than scrolling — Ctrl+F over the index is faster.
  • The keyboard-shortcut cheat sheet at /keyboard-shortcuts is the most-printed page; bookmark separately if you want a printed copy.

Limitations

  • No translations yet — English only.
  • Developer-facing topics (manifest internals, content-script architecture) are not on this page; they live in the GitHub repository.
  • Some screenshots may show a default theme; if you have heavily customized your appearance, the visuals will differ.

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