Browser Policy Manager (BPM) is approaching its 1.0.0 release as an open-source tool for preparing, validating, and exporting Firefox Enterprise policy profiles. The project allows administrators to work with policies not only as raw policies.json files but also through a profile library, step-by-step editor, settings catalog, comparison tools, and source editor.
Version 0.9.5 adds support for four current Firefox schema channels: Release 153, ESR 153.0, ESR 140.13, and ESR 115.38. For older supported ESR releases, BPM can suggest migration to ESR 153.0, generate a preview of changes, and apply the transformation only after explicit confirmation. Profiles remain unchanged if a plan is outdated, blocked, or fails validation.
Why dedicated documentation matters
Official Mozilla documentation covers policy syntax and semantics, yet daily administration raises different questions: which schema channel to select for a given browser fleet, where to locate a setting inside BPM, when to use the step-by-step editor versus full JSON, how to validate imported files, and how to map profiles to CIS recommendations without treating automation as verified benchmark compliance. The new documentation portal addresses these needs directly within the product.
The portal contains four families of guides available in six interface languages: English, Russian, German, Simplified Chinese, French, and Spanish. These include a user guide covering the profile library, comparison features, editors, import/export, and error recovery; a Firefox policies reference explaining differences between Release and ESR channels; a CIS settings guide with mappings, presets, merge order, and automation boundaries; and an administrator and DevOps guide covering source builds on Linux and Windows via WSL, API integration, and current production limitations.
Technical implementation
Documentation sources are written in DITA to support reusable structure, stable topic identifiers, multiple locales, and strict link checking. After validation of content, terminology, links, and completeness, a static artifact is generated that includes a manifest and UI target map. BPM serves this artifact at /help/ without pulling DITA tooling or Java into the runtime. Context-sensitive links open in a new tab, preserving the state of any active profile editor.
Search relies on pre-built static indexes per locale. Ranking prioritizes exact matches on policy identifiers and headings over fuzzy text matches, with limited tolerance for typos. Normalization rules, aliases, and test queries are maintained separately for each language to handle declension, CJK segmentation, and technical identifiers correctly.
Future RAG plans and localization quality
No RAG or generated answers are active in 0.9.5. Planned local assistant features will require verified source fragments, atomic updates after hash and coverage checks, and explicit refusal when no suitable evidence exists in the requested locale. The model will not be trained on documentation or user dialogs.
Localization goes beyond simple translation. Every language maintains its own topics, navigation maps, search strings, alt text, and screenshots. A matrix of 36 verified localized images supports key scenarios. The 0.9.5 documentation review passed 1,001 selected contracts covering locale completeness, terminology consistency, visible English text, links, navigation, search, screenshots, and interface connections.
Source code for Browser Policy Manager is available on GitHub. The official Mozilla Firefox administrator reference remains the authoritative source for policy syntax and behavior.
