Building the Search: My Week 2 Progress on Bloom After

Published: (March 13, 2026 at 03:07 PM EDT)
3 min read
Source: Dev.to

Source: Dev.to

Cover image for Building the Search: My Week 2 Progress on Bloom After

What I Built This Week

1. The Clinic & Hospital Finder

The most technical part of the week. I built the search directory so mothers can find a clinic easily without scrolling forever.

  • Interactive Map – Used Leaflet.js to create a map with clinic pins and added a “Use My Location” button that leverages browser geolocation to sort the list by proximity.
  • Advanced Filters – Implemented filtering by cost (Free/Subsidised vs. Private), doctor type, and delivery mode (online vs. in‑person).
  • Slide‑out Details – Clicking a clinic opens a panel with phone number, address, and a form to leave a review.

2. Building the Resource Hub

A huge part of the week was spent getting the content library ready. I built the main pages from scratch.

  • Main Library – Created the Articles and Resources pages, ensuring the logic allows easy addition of new content without breaking the code.
  • Technical Layouts – Updated renderers.js to handle our specific data structures, added support for infographics, and set up a side‑by‑side comparison view for the “Myth vs. Fact” section.

Technical Tools & Setup

We needed a way to host images and keep the site live without managing our own servers.

  • Cloudinary – Stores and serves images efficiently.
  • MongoDB – Holds clinic data.
  • Render – Hosts the backend, providing a stable environment for our API.

Challenges I Faced

  • Map rendering bug – The map initially displayed a blank grey box because it loaded before the page was ready. Fixed by forcing a size check after page load.
  • “Load More” button – It didn’t hide when the list was exhausted. Resolved with a global CSS rule that forces the hidden state.
  • Render deployment – Automatic deployments weren’t triggering on push, requiring manual deployment triggers. Working on a more reliable CI/CD setup.

What I Learned

  • Maps and Math – Implemented the Haversine formula to calculate distances between points on the map.
  • Cleaner Code – Moved inline styles from JavaScript to dedicated CSS files, improving readability and maintainability.
  • Collaboration – Coordinating cloud tools and MongoDB with the backend lead highlighted the speed gains from frontend‑backend sync.

Team Shoutouts

Building this isn’t a one‑person job. A massive thank you to the amazing people working alongside me:

  • Chijioke Uzodinma (Backend Lead) – Read his Week 2 article here.
  • Nanji Lakan (Product Lead) – Read her Week 2 article here.
  • Agugua Genevieve (Design Lead) – Read her Week 2 article here.
  • Prisca Onyemaechi (Lead Maintainer) – Read her Week 2 article here.
  • Adejola Esther (Frontend Engineer) – Read her Week 2 article here.

Live Site & Repository

  • Visit our live site:
  • GitHub repository:
0 views
Back to Blog

Related posts

Read more »

Intro About Java Script

Introduction In today’s class I learned a short introduction to JavaScript, so I’ll share some facts about JavaScript in this blog. What Is JavaScript? JavaScr...

GPU Flight — System Architecture

GPU Flight Architecture Overview The previous post covered thread divergence at the SASS level. Before diving into other optimization strategies, it helps to r...

2026 WeCoded Challenge (Glass Ceiling)

!Cover image for 2026 WeCoded Challenge Glass Ceilinghttps://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2F...