Client project · Financial institutions

Bank of Africa United Kingdom

A corporate digital experience built for the bank’s teams and visitors.

Weblysoft designed and developed Bank of Africa UK’s corporate website and its content management experience, together with a digital assistant that helps visitors find approved institutional information.

Visit the live website(opens in a new tab)

Corporate homepage The public entry point: institutional identity, primary navigation and routes into services.
Client
Bank of Africa United Kingdom
Industry
Financial institutions
Weblysoft’s role
Digital experience design and software engineering
Project scope
Corporate website, content management, digital assistant
The challenge

A corporate website that works beyond the launch

The bank’s digital presence needed to present institutional information and corporate banking services, and to stay current after go-live. Weblysoft brought those needs together in a public website and a supporting content management experience.

  1. Corporate communication

    Present the institution, its corporate banking services, capital markets activity, geographic presence and news in one consistent site.

  2. Content ownership

    Let authorized members of the bank’s team maintain website content through an administrative environment rather than code changes.

  3. Information discovery

    Help visitors reach the right information through clear navigation and an on-site digital assistant.

What Weblysoft designed and built

Digital experience design

  • Information architecture and navigation
  • Interface and visual design
  • Responsive layouts

Website engineering

  • Public frontend implementation
  • Reusable page components
  • Interactive coverage map

Content management

  • Page editing in the CMS
  • Structured content blocks
  • Save draft, unpublish and publish controls

Digital assistance

  • Visitor-facing assistant interface
  • Knowledge-source administration screen
  • Document enable and reindex controls
Public website

Clear pages for services, the institution and its reach

The public experience organizes institutional information, corporate services and geographic presence into one consistent, responsive website. Select any screen to enlarge it.

Geographic coverage An interactive map that distinguishes the group’s office locations from its wider capital markets coverage.

Reading the coverage map

The map uses separate categories, so visitors can see where the group has offices and, distinctly, which markets its capital markets activity covers. An office presence and market coverage are not the same claim, and the page keeps them apart.

Category definitions follow the live website. Check it for the current list of countries.

Corporate services Service information presented through consistent, structured page sections.
Institutional overview Corporate information organized to explain the institution and its activities.
News and press Corporate announcements on a dedicated news page.
Content management

The website is public. The control is behind the scenes.

Behind the public website is a content management environment where authorized users open pages, edit structured content blocks, and save drafts or publish their changes.

CMS dashboard

The administrative entry point, with navigation to the site’s content areas. The same admin shell also exposes a separate assistant knowledge module.

Admin screens are reviewed, redacted copies. Opaque areas deliberately hide names, statuses, internal addresses and other identifying details.

Page management
Editors locate the page they need and open it in the editor.
Structured editing
Content is entered through configured blocks and fields, not free-form layout.
Draft, publish, unpublish
The editor provides Save draft, Unpublish and Save & Publish. We do not describe a multi-stage approval chain.
Signed-in access
The admin environment sits behind sign-in. These screens show the interface, not an audit of server-side permissions.

From content editing to the public website

The CMS editor and the public site both show the homepage: the same hero headline and Our Services and Contact Us labels, with minor wording differences on the live page. They are two static snapshots, not a before-and-after of a publish action.

Homepage in the CMS editor
Homepage on the public website

Showing the homepage in the CMS editor, with Save draft, Unpublish and Save & Publish controls. Status badges are redacted, so no publication state is implied.

Digital assistant

Digital assistance from approved knowledge

Visitors can ask the on-site assistant for general information about the bank. Behind it, a separate knowledge module in the admin environment controls which approved PDF documents it can draw on. It does not give financial advice or account services.

Visitor assistant The assistant panel open on the public website.
Knowledge administration PDF sources with approved, enabled and reindex controls. Document names and statuses are redacted.
  1. Approve sourcesAdministrators add PDF documents and mark them approved and enabled.
  2. ReindexA reindex control refreshes the knowledge the assistant can use.
  3. Visitor asksA visitor types a question in the assistant panel.
  4. General answer or directionThe assistant responds with general information or points to the relevant page.

This page does not call the production assistant. Screens show interfaces we built, not answer accuracy, the AI provider or current production state.

Engineering and delivery

How the parts relate, and what was delivered

A simplified logical overview of the experience. It explains relationships between components; it is not a runtime or infrastructure diagram.

Content path
  1. Authorized editorsSigned-in team
  2. CMS editingPages and content blocks
  3. Published public pagesCorporate website
Knowledge path
  1. Approved PDF documentsKnowledge module
  2. Knowledge processingEnable and reindex
  3. Assistant interfacePanel on the website
VisitorReads pages and asks questions
Logical overview only. Hosting, CMS version, AI provider and deployment mechanics are not shown and not claimed. The two paths share an admin shell; we do not state that the assistant queries the CMS directly.

Delivered, and shown on this page

  • Responsive corporate website with services, overview, coverage and news pages
  • Interactive coverage map separating office locations from capital markets coverage
  • CMS editing with structured content blocks and publish controls
  • Visitor assistant interface and a knowledge-source administration screen

What this case study does not claim

No traffic, conversion or support metrics, launch dates, support terms, certifications or security audits are stated, because we have not published records for them. Ask us and we will share what the engagement allows.

This engagement is separate from the anonymized financial-institution governance work described in our engagement records. Engagement records

Next step

Planning a similar corporate digital platform?

Tell us about your public site, the team that will maintain it and whether visitors need assistance. We will show you the relevant parts of this work.

Discuss your projectTell us what you need. We reply within one business day. Book a callPick a time to talk with the people who would do the work. Request a strategic reviewA 45-minute working session on an operational problem.