The reference is a flat catalog: you find the tag you want, read the attribute list, and copy the sample markup. Two practices make it useful day-to-day instead of just a reference dump.
- Bookmark the apex namespace index
Most Visualforce work uses apex tags. The top-level apex namespace index page groups all of them on one scrollable page, which is faster than clicking through the categorized navigation.
- Use browser find rather than the docs navigation
The reference has a categorized sidebar but no full-text search across attributes. Browser find (Ctrl+F or Cmd+F) across the namespace index page is usually faster when you remember a partial tag name.
- Cross-check the Lightning Experience flag
Open the tag detail page and look for the Lightning Experience and Salesforce Mobile compatibility indicators. If either is red, the tag will silently degrade in those contexts; you will get a different rendering or no rendering at all.
- Compare the sample markup to your context
The sample shows minimum-viable usage. For real production patterns, look at how Salesforce-internal pages use the tag (View Source on any standard Salesforce VF page in Classic) or check Trailhead modules that exercise the tag in context.
- Switch to the Component Library for new builds
If you are starting a new screen rather than maintaining an existing Visualforce page, do not use the Visualforce reference. Use the Lightning Component Library and build with LWC or Aura. Salesforce stopped investing in Visualforce tags around 2018.
Companion long-form guide that explains controllers, expressions, and the Visualforce page lifecycle.
The newer, interactive reference at developer.salesforce.com/docs/component-library for LWC and Aura.
Same component metadata, surfaced as you type inside the Salesforce Developer Console page editor.
- The reference shows the tag list for one release at a time. If your org is on a Sandbox preview or trial, switch the version selector at the top of the docs to match.
- Sample markup is intentionally minimal and almost never demonstrates the controller binding you need. Treat it as a hint, not a template.
- Tags marked unavailable in Lightning Experience silently render as plain text or not at all in LEX. Always check the flag before assuming a tag works.
- Custom Visualforce components built by your team or by managed packages are not in this reference. Look at the .component metadata in Setup or in the package documentation.
- Visualforce has been in maintenance mode since around 2018. New development should use LWC; the reference will not get new tags.