Updating /docs/VERSION from a Fineract backend clone
docs/VERSION (e.g. docs/1.16.0-SNAPSHOT) holds the rendered Fineract API
documentation built from the apache/fineract
backend. To refresh it:
In your clone of apache/fineract, generate the docs:
./gradlew asciidoctor
Make sure the clone’s working tree is clean (git status) – the commit hash
is recorded so the copied doc can be traced back to the exact source commit.
Install Graphviz (dot), plus vl2vg and vg2svg (npm install -g vega-cli vega-lite), first. Without them the build still succeeds but leaves
diagrams out: PlantUML draws a “Cannot find Graphviz” error image in place of
each of its diagrams. fineract-site docs refuses such a page, and
fineract-site build fails on any already in docs/
(scripts/check_doc_diagrams.py). After installing Graphviz, delete
fineract-doc/build before rebuilding, as generated diagrams are cached.
Run the docs command in the site tool image, mounting both repos:
The version can also be set via FINERACT_DOC_VERSION, and the backend
mount path via FINERACT_REPO_DIR (default /fineract).
This copies fineract-doc/build/docs/html/en/index.html from the backend clone
into docs/VERSION/index.html, then rewrites the Google Fonts and Font Awesome
CDN links to point at the site’s local css/ stylesheets (per Apache project
website requirements). Versions ending in -SNAPSHOT are overwritten; released
versions are not, unless you pass --replace-release to republish one from the
same release tag (e.g. to fix a broken build).
It also suggests a commit message. Use it like so:
git commit -F DOCS-LOG-MESSAGE
After updating docs, update .htaccess.
Verifying ASF project website compliance
Apache Whimsy periodically checks that the public homepage follows ASF conventions.
Output of these checks is displayed here.
Contributor Guide
See CONTRIBUTING.md for CI/CD details and branch/PR workflow.
fineract-site
Apache Fineract website source repository for https://fineract.apache.org, a Hugo-generated static website.
Prerequisites
Guide to this repository
site-src/(OK to edit)docs/→/docs/css/→/css/js/→/js/images/→/images/font/→/font/.htaccess→/.htaccessdoap_Fineract.rdf→/doap_Fineract.rdf.build/site(do not edit)Issue tracker
Issues are in GitHub as of July 20, 2026. Older ones are in JIRA.
Local Build and Checks (Docker)
Windows PowerShell equivalent (no UID/GID mapping):
Updating
/docs/VERSIONfrom a Fineract backend clonedocs/VERSION(e.g.docs/1.16.0-SNAPSHOT) holds the rendered Fineract API documentation built from the apache/fineract backend. To refresh it:In your clone of
apache/fineract, generate the docs:Make sure the clone’s working tree is clean (
git status) – the commit hash is recorded so the copied doc can be traced back to the exact source commit.Install Graphviz (
dot), plusvl2vgandvg2svg(npm install -g vega-cli vega-lite), first. Without them the build still succeeds but leaves diagrams out: PlantUML draws a “Cannot find Graphviz” error image in place of each of its diagrams.fineract-site docsrefuses such a page, andfineract-site buildfails on any already indocs/(scripts/check_doc_diagrams.py). After installing Graphviz, deletefineract-doc/buildbefore rebuilding, as generated diagrams are cached.Run the
docscommand in the site tool image, mounting both repos:The version can also be set via
FINERACT_DOC_VERSION, and the backend mount path viaFINERACT_REPO_DIR(default/fineract).This copies
fineract-doc/build/docs/html/en/index.htmlfrom the backend clone intodocs/VERSION/index.html, then rewrites the Google Fonts and Font Awesome CDN links to point at the site’s localcss/stylesheets (per Apache project website requirements). Versions ending in-SNAPSHOTare overwritten; released versions are not, unless you pass--replace-releaseto republish one from the same release tag (e.g. to fix a broken build).It also suggests a commit message. Use it like so:
After updating docs, update
.htaccess.Verifying ASF project website compliance
Apache Whimsy periodically checks that the public homepage follows ASF conventions. Output of these checks is displayed here.
Contributor Guide
See
CONTRIBUTING.mdfor CI/CD details and branch/PR workflow.