Welcome, Ali! Thanks for your excellent comms here and in FINERACT-2484 <https://issues.apache.org/jira/browse/FINERACT-2484>. Some of this will be redundant/review as I attempt to bring a few things together for the mailing list.
Please wait until the existing Hugo patch <https://github.com/apache/fineract-site/pull/53> is resolved before starting new work on the project website, including a11y (accessibility). I agree with Aira's comments earlier in this thread as far as what to work on next. The high-level priorities for the fineract.apache.org project website are 1. *compliance* (see below) 2. *maintainability* (improving with in-progress migration to Hugo) 3. *speed* (no issues here. It is plenty fast, we just need to keep it that way) For compliance, we should 1. keep the ASF website checks <https://whimsy.apache.org/site/project/fineract> green 2. use valid HTML/CSS/JS markup & code 3. set and maintain a11y standards For valid markup & code, I think HTMLHint <https://htmlhint.com> will help us keep our HTML valid enough, CSS is OK but we should reduce/simplify/cull it a bit, and I think we can cull ALL our JS code. Credit to Aira for introducing me to HTMLHint. For a11y, I'm hoping Axe <https://github.com/dequelabs/axe-core> open source tooling will keep us compliant enough. Credit to Aira for introducing me to Axe. If anyone has experience with the tools I mentioned or strong opinions about anything above, please speak up. I'm not sure about SonarQube. When it comes to our project website, I'd say just ignore it. I didn't turn it on, I don't know why it recently starting scanning apache/fineract-site PRs <https://issues.apache.org/jira/browse/INFRA-22420>, and I don't find it particularly helpful. If it is FOSS and can be made to be helpful, I'm open to suggestions! See also: reference guide for Apache project web sites <https://infra.apache.org/project-site.html> Best, -Adam
