docs: the add-on is published on addons.mozilla.org Installation now leads with the store listing on both language pages, since a signed add-on survives a restart and updates itself, and the temporary-add-on route is demoted to a development step. The publishing pages describe the automated upload: a v* tag signs and uploads the package to the pinned add-on id, skipping the upload when AMO already has that version, and the two API secrets that switch it on.
Add a full Persian mirror of the wiki Nine Persian pages, one for every English page, not a summary: خانه، نصب، راهنمای تنظیمات، رفع مشکل، سوالات متداول، مشارکت، معماری، نگهداری سلکتورها، انتشار و ریلیز. Most users of a Bale extension read Persian, so the Persian pages carry the same detail as the English ones rather than pointing at them. Both installation pages now walk through downloading a release package and loading it unpacked, step by step, including the trap that Chrome reads an unpacked extension from its folder on every start. Every page carries a language switch at the top and the sidebar lists both languages.
Installation: add the prebuilt release packages as an install route
Add the project wiki Nine pages split by audience: Installation, Settings Reference, Troubleshooting and FAQ for people using the extension; Contributing, Architecture, Selector Maintenance and Publishing and Releases for people working on it. Sidebar and footer for navigation.
Initial Home page