How ridwanridu/ibbl-kartikpur works
Purpose and delivery model
This repository is a static informational website for the Islami Bank Bangladesh PLC Kartikpur Bazar Agent Banking outlet. It presents agent-banking services and contact information; it has no indicated backend, authentication, transaction processing, or API layer. Deployment is static hosting, primarily GitHub Pages.
Paths: index.html, README.md
Primary entry and navigation
index.html is the main browser entry point and likely landing page for outlet information. Navigation is implemented as separate HTML documents rather than a client-side router, keeping page boundaries URL- and browser-native.
Paths: index.html, agent.html, branches.html
Outlet and service presentation
The core UI is static HTML/CSS/JavaScript rendered directly by the browser. Its principal responsibility is making service descriptions, location/address, and emergency contact channels accessible across desktop and mobile layouts.
Paths: index.html, agent.html
Agent directory data boundary
agents.json is the repository’s structured data asset. It likely separates agent/outlet records from page markup, allowing JavaScript in the HTML pages to load or display directory information without a server database. Any changes to agent records should preserve this JSON-to-browser consumption contract.
Paths: agents.json, agent.html, branches.html
Branch and agent discovery views
The repository distinguishes the local outlet landing experience from directory-style views: agent.html is the agent-facing/listing page, while branches.html provides branch-related discovery. These pages form the main information-navigation flow from general banking context to specific service locations.
Paths: index.html, agent.html, branches.html
Client runtime and platform boundary
The runtime is a standard web browser using HTML5, CSS3, and JavaScript embedded or referenced from the static documents. The browser fetches same-origin static assets such as agents.json; therefore hosting must serve the JSON with browser-accessible paths. GitHub Pages is the stated hosting platform.
Paths: index.html, agents.json, README.md
Installability metadata
site.webmanifest supplies web-app metadata for compatible browsers, creating an installability/PWA-adjacent boundary without evidence of service-worker-based offline behavior in the available tree.
Paths: site.webmanifest, index.html
Main entry points: index.html Outlet landing page · agent.html Agent directory page · branches.html Branch discovery page · agents.json Agent records
Components 9
Static website
Browser-served informational pages and assets.
- Outlet landing page · Primary entry for outlet services and contacts.
index.html - Agent directory page · Agent-facing listing and discovery view.
agent.html - Branch discovery page · Branch-related location discovery view.
branches.html - Agent records · Structured directory data consumed in the browser.
agents.json - Client presentation · Static responsive service, location, and contact UI.
- Web app manifest · Installability metadata without indicated offline runtime.
site.webmanifest
Hosting
Static deployment boundary.
- GitHub Pages · Primary static hosting platform.
Other components
- Web browser · Renders pages and fetches same-origin assets.
- Project documentation · Documents the static site and GitHub Pages delivery.
README.md
Connections 12
- Web browser → GitHub Pages: requests site
- GitHub Pages → Outlet landing page: serves
- GitHub Pages → Agent directory page: serves
- GitHub Pages → Branch discovery page: serves
- Outlet landing page → Agent directory page: navigates to
- Outlet landing page → Branch discovery page: navigates to
- Agent directory page → Agent records: loads
- Branch discovery page → Agent records: uses for discovery
- Outlet landing page → Client presentation: renders
- Agent directory page → Client presentation: renders
- Outlet landing page → Web app manifest: declares
- Project documentation → GitHub Pages: documents deployment