I was on a call with a friend and we got talking about what we were building. She looked up my name on google and boom - My website came out tops. She hailed me from quality SEO work done on my site but she laughed sheepishly at the UI. I took it in good fate.

I cloned my Portfolio site that I had not touched since 2023 and started out with a redesign in view.

The site worked. It had my name, my projects, my blog. But it didn't feel like _now_. The layout was the same one I'd last shipped in January 2023 on Next.js 12. JavaScript files everywhere. 

A sidebar with my email and phone number taking up prime space on the home page. No dark mode. No real SEO strategy beyond whatever Next gave me for free.

I'm a frontend developer. My site is the first thing people see. That gap bothered me more than I expected.

So I gave myself one day to fix it.

## What the old site looked like

If you want to see it yourself, the previous version is still live at **[v1.winpeed.com](https://v1.winpeed.com)**. I froze the January 10, 2023 commit (`b7b7bcf` — the last update before this redesign) and deployed it to its own subdomain. Not a mockup. The actual site as it was.

Here's how it looked like before:

![Old website](//videos.ctfassets.net/ffkp02jwjz54/5W2kleyGnKJFSFvB5KC0q3/744d68786cc03663d3409ca56c95904f/Old_website.mp4)

The old home page was simple: profile photo on the left, intro copy on the right, contact details in a permanent sidebar. Projects and Resume buttons. It did the job when I first built it.

But a few things kept nagging me:

- **The aside ate the layout.** Email, phone, social links — all visible before anyone read a single word about what I do.
- **Everything was JavaScript.** No types, no confidence when refactoring, lots of `.js` files I was hesitant to touch.
- **It felt frozen in time.** Next.js 12, older dependencies, a stack I wouldn't start with today.
- **No dark mode.** I work at night. My site didn't.

![Home page for old website](//images.ctfassets.net/ffkp02jwjz54/2IvtzuI9n7zyVfmb9q8uB4/07030ca6aba1ced266bdef24a520f929/Screenshot_2026-07-10_at_15.29.21.png)

_The old site: functional, but the sidebar dominated the home page._

## The constraint: one day

I wasn't doing a six-week redesign project. Due to my busy work schedule, I had a day (maybe two) to ship something I could be proud about.😄

That meant ruthless scope. No new CMS. No blog migration. No fancy animation reel. Keep Contentful for posts, keep Netlify for deploy, keep the pages that already worked.

The goal was simple: **make the site feel 2026, typed, and intentional.**

## What I changed

### TypeScript, end to end

The biggest structural shift was moving the entire codebase from JavaScript to TypeScript. Components, containers, style files, API routes, config - all of it.

This wasn't about being trendy. I was tired of guessing prop shapes and breaking things silently. Typed Contentful entries, typed styled-component props, typed page props (small wins you can say)

I didn't convert everything to strict mode perfection in one pass. I typed what I touched and kept moving.

### A new home page

The old layout leaned on `AsideContainer` — contact info as a permanent column. I removed that from the home page entirely and rebuilt around two sections:

1. **A hero** with gradient heading, orb background, deferred profile column, and a tech marquee loaded below the fold.
2. **A bento grid** — About, Projects, Blog, Contact as cards with clear entry points.

![v2 Home page light](//images.ctfassets.net/ffkp02jwjz54/5gQz1FpyEhoqNhn7FeOwxj/37e73c486752d2e6487169b8ed8229a8/Screenshot_2026-07-11_at_08.00.32.png)

It sounds like a small change. On screen, it feels completely different. The home page is about _where to go_, not _how to reach me_. Contact details moved to inner pages via a shared `PageShell` component.

### Dark mode

I added a `ThemeProvider` with `localStorage` persistence and `prefers-color-scheme` as the default. Toggle in the header. CSS variables in `globals.css` handle the rest.

I'd wanted this for a while. It took less time than I thought once I committed to CSS variables instead of duplicating styled-component themes everywhere.

![v2 new site dark mode](//images.ctfassets.net/ffkp02jwjz54/5iYzMGbungxSjKzThTl8bd/999f7fbd3c45ec3c25d4ce95a71db29e/Screenshot_2026-07-11_at_08.02.52.png)

### Route skeletons

This was a quality-of-life fix I didn't know I needed until I shipped it.

On route change, instead of a blank flash, the app renders a skeleton that matches the destination — home, about, projects, blog, contact. A small `useRouteSkeleton` hook listens to Next.js router events and swaps in the right placeholder.

It makes the site feel faster even when it isn't. Perception is everything.

### Consistent page shell

Every inner page — About, Projects, Blog, Contact — now uses the same `PageShell` wrapper. Title, subtitle, social strip, content. Before, each page felt like its own island.

The blog subtitle changed too: _"Personal reflections, work lessons, and notes on building for the web."_ That matches how I actually want to write — part journal, part work and development lessons.

### SEO that isn't an afterthought

I added a reusable `SEO` component with canonical URLs, Open Graph tags, Twitter cards, and JSON-LD structured data. Person and WebSite schema on the home page. BlogPosting schema on articles.

I also fixed sitemap generation, proper `robots.txt`, a web manifest, skip-to-content link, and Lighthouse CI in the pipeline.

For a portfolio, discoverability is part of the product. I treated it that way.

### Stack upgrades

| Before          | After                     |
| --------------- | ------------------------- |
| Next.js 12      | Next.js 15                |
| JavaScript      | TypeScript                |
| Framer Motion 6 | Framer Motion 11          |
| Contentful v9   | Contentful v11            |
| No lint hooks   | ESLint + Husky pre-commit |

## What I deliberately didn't do

- **No backend rewrite.** Contact form logic stayed minimal.
- **No design system from scratch.** styled-components, same as before — just cleaner.
- **No new blog platform.** Contentful still works. I updated my writing workflow instead.
- **No pixel-perfect Figma first.** I took advantage of my design system I already spent time working on in Claude design.

Knowing what to skip was as important as knowing what to ship.

## The result

By the end of the day, I had a site I wanted to share.

Dark mode works. Navigation feels smooth. Pages share a visual language. The codebase is typed. SEO is intentional. The home page actually guides visitors instead of dumping contact info on them.

This was my high point in the whole process - __The Old blog page vs New blog page__

![Blog page for old website](//images.ctfassets.net/ffkp02jwjz54/5YXqqtb4NVT0u7STWUGNTd/8b689d8c1f8790ccb3068d18d241724a/Screenshot_2026-07-10_at_15.29.57.png)

![Dark mode - blog page](//images.ctfassets.net/ffkp02jwjz54/4fQNcn0FMOlMlYfpUMuZdF/6b812d143dde080c265a6443d18fdb4f/Screenshot_2026-07-10_at_20.59.01.png)

Browse the old version at **[v1.winpeed.com](https://v1.winpeed.com)** and the new one at **[winpeed.com](https://winpeed.com)**. The difference is easier to feel than to describe.

## Lighthouse Performance: Before vs. After

One of my primary goals during this redesign wasn't just to create a better-looking website. It was to build a faster, more accessible, and SEO-friendly experience.

To measure the impact, I ran Google Lighthouse audits before making any changes and compared them with the results after the redesign.

### 📱 Mobile — Before

The mobile audit revealed several opportunities for improvement, particularly around performance, accessibility, and render-blocking resources.

![Mobile Lighthouse Before](//images.ctfassets.net/ffkp02jwjz54/4BDDmo9FnsoGqqQMJezi90/7c0a7fbaf47fc4b8e650e9a1fe71e3d6/Screenshot_2026-07-11_at_08.27.50.png)

### 💻 Desktop — Before

Desktop performance was stronger than mobile, but there were still optimizations that could improve the overall user experience.

![Desktop Lighthouse Before](//images.ctfassets.net/ffkp02jwjz54/5t2c107mfDoBFMTAr9PJrZ/040f62b7392c4f7d16c7e2e3f66a1080/Screenshot_2026-07-11_at_08.28.00.png)

## Key Issues Identified

Some of the most significant issues Lighthouse highlighted included:

- Large and unoptimized images
- Render-blocking CSS and JavaScript
- Unused JavaScript
- Accessibility improvements (labels, contrast, semantics)

## What I Improved

During the redesign, I focused on addressing these issues by:

- Optimizing and compressing images
- Lazy loading non-critical assets
- Reducing JavaScript bundle size
- Optimizing fonts
- Eliminating unnecessary re-renders

### Mobile — After

The improvements resulted in significantly better Lighthouse scores and a noticeably faster experience on mobile devices.

![Mobile Lighthouse After](//images.ctfassets.net/ffkp02jwjz54/1QlCI5xCnxjxCIYXxs7XxP/cbcd09c49fc61073fc2c42ab880d2f1b/Screenshot_2026-07-11_at_08.51.49.png)

### Desktop — After

Desktop performance also saw measurable improvements across all Lighthouse categories.

![Desktop Lighthouse After](//images.ctfassets.net/ffkp02jwjz54/5LCJUtGhQAlzWajLdkINmw/46de9b81989462fb34de20912f374b60/Screenshot_2026-07-11_at_08.51.59.png)

## Results

#### Mobile

| Category | Before | After |
|----------|--------:|-------:|
| Performance | 70 | 97 |
| Accessibility | 100 | 96 |
| Best Practices | 100 | 100 |
| SEO | 100 | 100 |

#### Desktop

| Category | Before | After |
|----------|--------:|-------:|
| Performance | 68 | 100 |
| Accessibility | 95 | 96 |
| Best Practices | 100 | 100 |
| SEO | 100 | 100 |

### Note
Lighthouse scores are just one measure of quality. However beyod that, they provide a useful benchmark for tracking improvements. 

More importantly, these optimizations translated into a faster, smoother, and more accessible experience for real users.

## What I'd do differently if I were to do this again.

**Screenshot before you deploy.** I almost shipped without capturing the old site properly. If you're writing a rebuild post, freeze the exact commit you mean (not just "an old deploy"), tag it, deploy it to a subdomain, and screenshot it. After this, ensure you verify the live archive matches that commit before you publish.

**Migrate in layers.** I tried to do too much at once early in the day. Typing one route at a time would've been calmer. However, big shout to cursor AI. It did most of the heavy lifting for me and bailed me out when I ran into major issues.

## If you're thinking about your own rebuild

You don't need a week off. You need a clear scope and a version of the site you're willing to archive.

Tag your last commit. Deploy it to a subdomain. Screenshot everything. Make use of AI tools such as Cursor AI, OpenAI, or Claude AI to speed up your development workflow.

Ship the new thing and keep it fresh.

Your portfolio is a living project. Mine was overdue for a day of honest work.

_Old site: [v1.winpeed.com](https://v1.winpeed.com) · New site: [winpeed.com](https://winpeed.com)

I rebuilt my portfolio from JavaScript to TypeScript, shipped dark mode, route skeletons, and proper SEO — in one focused day. Browse the old site at https://v1.winpeed.com/

Hero Image for I redesigned my portfolio in one day — here's what actually changed

I redesigned my portfolio in one day — here's what actually changed

## Why _document.tsx?

Next.js lets you customise the outer HTML shell — the `<html>` and `<body>` tags that wrap every page. Font `<link>` tags belong in that shell, not repeated inside individual components.

The file lives at `pages/_document.tsx`. Official docs: [Custom Document](https://nextjs.org/docs/pages/building-your-application/routing/custom-document).

> **Note:** `_document.tsx` only runs on the server. It doesn't re-render on client-side navigation. That's fine for fonts — you load them once and they apply everywhere.

## Step 1 — Get your link tags from Google Fonts

1. Go to [Google Fonts](https://fonts.google.com/)
2. Select your font (I used **Inter** for body copy)
3. Pick the weights you need — I went with 300 through 800
4. Click **Get font** → **Get embed code**
5. Copy the `<link>` tags Google gives you

You'll get something like this:

```html
<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link
 href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700;800&display=swap"
 rel="stylesheet"
/>
```
Paste those into `_document.tsx` — inside `<Head>`, not `<body>`.

## Step 2 — Create `pages/_document.tsx`

```tsx
import Document, { Html, Head, Main, NextScript } from "next/document";
export default function MyDocument() {
 return (
 <Html lang="en">
 <Head>
 <link rel="preconnect" href="https://fonts.googleapis.com" />
 <link
 rel="preconnect"
 href="https://fonts.gstatic.com"
 crossOrigin="anonymous"
 />
 <link
 href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700;800&display=swap"
 rel="stylesheet"
 />
 </Head>
 <body>
 <Main />
 <NextScript />
 </body>
 </Html>
 );
}
```

A few things worth noting:

### Put `<link>` tags in `<Head>`, not `<body>`

Font links are document metadata! They belong in `<Head>`. I saw some tutorials that dropped them in the body. It might work in some browsers, but it's not correct and can cause inconsistent loading.

### `crossOrigin` — not `crossOrigin="true"`

Google's embed snippet uses `crossorigin` on the preconnect to `fonts.gstatic.com`. In React/JSX, write it as:

```tsx
crossOrigin="anonymous"
```

Not ~~`crossOrigin="true"`~~ ! 

The HTML spec expects `"anonymous"` or `"use-credentials"`. This matters for CORS when the browser fetches font files from Google's CDN.

### `preconnect` — please don't skip it

The two `preconnect` links tell the browser to open connections to Google's font servers early. Small detail, real difference in how fast your fonts show up. Keep both.

### `display=swap` in the URL

Notice `&display=swap` at the end of the Google Fonts URL. That tells the browser to show fallback text immediately and swap in the font when it loads. Stops invisible text while fonts download.

## Step 3 — Use the font in your CSS

Loading the font isn't enough. You have to reference it.

In `styles/globals.css`:

```css
body {
 font-family: "Inter", ui-sans-serif, system-ui, sans-serif;
}
```

Or for a heading font like Merriweather, add a second `<link>` in `<Head>` and use:

```css
 h1, h2, h3 {
 font-family: "Merriweather", serif;
 }
```

Always include a fallback stack after your custom font. If Google Fonts fails to load, your site still looks fine.

## Adding a second font

Same process. Go to Google Fonts, select **Merriweather** (or whatever you want), copy the new `<link>`, add it to `<Head>`:

```html
 <link
 href="https://fonts.googleapis.com/css2?family=Merriweather:wght@300;400;700;900&display=swap"
 rel="stylesheet"
 />
```

You can also combine families in one URL if you prefer fewer requests:

```html
 ?family=Inter:wght@300;400;500;600;700;800&family=Merriweather:wght@300;400;700;900
```

## What I use on winpeed.com now

When I rebuilt [my portfolio](https://www.winpeed.com) on **Next.js 15**, I switched to **`next/font/google`**. Next.js self-hosts the font files at build time — no external requests to Google at runtime, no layout shift from late-loading stylesheets.

`utils/fonts.ts`:

```tsx
 import { Inter, Merriweather } from "next/font/google";

 export const inter = Inter({
 subsets: ["latin"],
 weight: ["300", "400", "500", "600", "700", "800"],
 variable: "--font-inter",
 display: "swap",
 });

 export const merriweather = Merriweather({
 subsets: ["latin"],
 weight: ["300", "400", "700", "900"],
 variable: "--font-merriweather",
 display: "swap",
 });
```

`pages/_app.tsx`:

```tsx
 import { inter, merriweather } from "../utils/fonts";

 function MyApp({ Component, pageProps }: AppProps) {
 return (
<div className={`${inter.variable} ${merriweather.variable} ${inter.className}`}>
 <Component {...pageProps} />
</div>
 );
 }
```

`styles/globals.css`:

```css
 body {
 font-family: var(--font-inter), ui-sans-serif, system-ui, sans-serif;
 }
```

Headings in styled-components:

```css
 font-family: var(--font-merriweather), serif;
```

No `<link>` tags needed. No `_document.tsx` font setup. The CSS variables (`--font-inter`, `--font-merriweather`) work anywhere in your styles.

My `_document.tsx` today handles other things — favicons, theme flash prevention, styled-components SSR — not fonts.

## Which approach should you use?

| | `_document` + `<link>` | `next/font/google` |
|---|------------------------|---------------------|
| **Setup** | Copy tags from Google Fonts | Import from `next/font/google` |
| **Works on** | Pages Router | App Router and Pages Router |
| **Font hosting** | Loaded from Google CDN | Self-hosted by Next.js |
| **Privacy / GDPR** | External request to Google | No runtime Google request |
| **Best for** | Quick setup, older Next projects | New Next.js projects (12.2+) |

If you're starting fresh on Next.js 12.2 or later, I'd go `next/font`. If you already have a `_document.tsx` with fonts working, no pressure to migrate.

## Common mistakes I ran into

**Fonts not applying** — I added the `<link>` but forgot `font-family` in CSS. The font loads but nothing uses it.

**Wrong `crossOrigin`** — `crossOrigin="true"` doesn't do what you think. Use `"anonymous"`.

**Links in `<body>`** — Move them to `<Head>`.

**Loading too many weights** — Every weight is more bytes. I only load what I actually use in the design. This is very important

Typography is one of those details people feel before they can name it. [My portfolio](https://www.winpeed.com) looked more intentional the day I stopped accepting whatever font the browser defaulted to.

---

*Referenced Docs: [Next.js Custom Document](https://nextjs.org/docs/pages/building-your-application/routing/custom-document) · [Next.js Font Optimization](https://nextjs.org/docs/pages/building-your-application/optimizing/fonts)*
```

How to load Inter and custom Google Fonts in Next.js using _document.tsx plus the next/font approach I use on winpeed.com today.

google font next 

Adding Google Fonts to a Next.js app — the _document way and what I use now

2022 seems to have begun on a good note, career-wise.

I don't say that lightly. The past year and a half had tested me in ways I didn't always know how to talk about. Applications sent into silence. Skills built in the margins of a full-time job. Doubt showing up on ordinary Tuesday evenings. So when things finally clicked, it didn't feel like luck. It felt like timing — the kind you can't manufacture on your own.

After 2+ years at Nigeria's largest bank, I'll be going back to the initial plan.

Yes! I'll be working as a frontend developer at a German startup company, **Mainteny**.

I'm grateful to God for this beautiful opportunity. I am once again reminded that God makes all things beautiful in His own time. This testimony really warms my heart, especially considering the hurdles I've gone through to get to this point.

## The road here

100+ different applications to several remote companies since May 2021 — when I decided to take this career path seriously again after signing up on Scrimba.

I'll say that's one of the best decisions I've taken. God's direction towards that path has been the best thing for me.

It wasn't glamorous. Some weeks I heard nothing back. Some interviews ended politely and I sat with the quiet afterward, wondering if I was delusional for trying. I kept building anyway — small projects, course exercises, anything that made me feel like a developer and not just someone who wanted to be one. 

Scrimba gave me structure when I needed it. My portfolio gave me something to point to when words weren't enough.

When I remember that I was already preparing for CompTIA+, CompTIA Network+, and even CCNA sometime back in January 2021, I burst into laughter.

My life was guided and redirected, and this I owe to God. The networking certifications weren't wasted though. I see them as part of my life's progress. 

But the door that actually opened wasn't the one I was studying for at the time. I used to find that frustrating. Looking back, I find it kind of funny.

## My 10X year

On my birthday last year, I declared my new year as my **10X year**.

I didn't mean it as a hustle-culture slogan. I meant it as a declaration of trust — that whatever God had for me in that season would be bigger than what I could sketch out on my own. I prayed for work that matched the direction I'd been running toward. 

True to God's faithfulness, this new role is everything I've prayed for and trusted God for.

Salary. ✅
Perks. ✅  
Remote work. ✅

I read that list back and I still smile. Not because everything is perfect. 

I know life isn't that simple but because this time, the alignment is REAL! 

Frontend. Remote. A startup building something that matters. A team and culture I can actually see myself growing inside. That's not a small thing when you've spent months wondering if anyone on the other end of an application was really seeing you.

## What I'm carrying forward

The bank years weren't a waste at all. I learned discipline there. How to show up. How to work with people. How to keep my head down and deliver when the task isn't exciting. That stays with me.

I'm back to building for the web. Yeah, the thing I kept coming back to even when the path looked unclear. Mainteny is where that road leads for now, and I'm stepping into it with gratitude and intent.

To anyone in the middle of their own 100 applications: I don't have a formula. I have a testimony. Keep building. Keep sending. Keep trusting that your season isn't cancelled because the reply hasn't come yet.

## Moving Forward

From this point on, it's cheers to much more. The path of the righteous is as a shining light, shining brighter and brighter unto a perfect day.

I'm ready for this next chapter. Grateful for the last one. And honest about how long it took to get here.

Cheers to greater things.

Somewhere around application number 60, I stopped counting out loud and started counting in prayer.

Not because I'd given up but because May 2021 to early 2022 had taught me that this road wasn't going to be short.

Hero Header Moving on to greater things - Next Career Steps

Moving on to greater things - Next Career Steps

Hey babe, 

Can you read this? 

It will be a month tomorrow 10th February 2022 with your heavenly Father, a month without you on earth. 

<video style="width:100%" controls>
 <source src="https://res.cloudinary.com/praiseobende/video/upload/v1644485401/Oiza_Martha_Obende_One_Month_nwesdi.mp4" type="video/mp4">
</video>
*__Video Credit: Uncle Yemi Obende__* 

I miss you. Your family misses you; and your friends too. 

I am not mourning you but I grieve your absence. I grieve all the earthly things you ought to do and the ones we were meant to do together. 

I'm assured you are with your maker, basking in His presence, in your incorruptible body free of every sickness and pain. 

![Aunty Oiza Tomb Stone](//images.ctfassets.net/ffkp02jwjz54/8xrbyz99ejBf73AZRq3WY/b73433ed70fa283df360960b7a722d68/Aunty_Oiza_Tomb_Stone.jpeg) 

Losing you hurts me, every single day I am aware of your absence, it can't be the same without you. I miss you so much. 

![Aunty Oremeyi at the grave](//images.ctfassets.net/ffkp02jwjz54/2ryFtzrSFkZkLHb5qq24m3/1016ee2e63c446daf26c001ef71eee61/Aunty_Oremeyi_at_the_grave.jpeg)

 

![Aunty Oremeyi 2](//images.ctfassets.net/ffkp02jwjz54/4N6Q1yT0t7MFpri36DtoiD/8d060d836e09d7629dce58e66a48f30c/Aunty_Oremeyi_2.JPG)

 

![Aunty Oremeyi 3](//images.ctfassets.net/ffkp02jwjz54/5jEEeBpQ5aR5H5QBHhzD1S/19493b7f1132ede2aa5c169bc886a1aa/Aunty_Oremeyi_3.jpeg)

 

The Awesome4 miss you. 

![Awesome4](//images.ctfassets.net/ffkp02jwjz54/69ZopscGZRxgMq5IYXbNRz/48257c393ddccba552c2a5eca36f00c0/Awesome4.jpeg)

 

![Awesome4-2](//images.ctfassets.net/ffkp02jwjz54/zcn8iuA0tIISdwhIhypV1/4344ed2a0ca44d173ca199a5c483622a/Awesome4-2.JPG)

 

Baba Nono misses you. 

![Baba Nono](//images.ctfassets.net/ffkp02jwjz54/2AYBgpFXLQ9K83Pd56awdS/89535dcbcf938a758003a11bf652d902/Baba_Nono.JPG)

 

Dele, Efi and Onofu miss you. 

![Dele](//images.ctfassets.net/ffkp02jwjz54/7aZLWdMzmUTurN3TqvuXd2/950d6ec4f04fb3bfad9a2e41cbe8be94/Dele.JPG)

 

![Efi](//images.ctfassets.net/ffkp02jwjz54/3BHRLb7O1sljshDB2lhJAK/af690e2026203329ba25e8c9fbd02c47/Efi.JPG)

 

![Dele 2](//images.ctfassets.net/ffkp02jwjz54/14ZVd2v3sy4tcogJOM8FZD/55c89f4758f24cebde6f8a12e69d8cc7/Dele_2.JPG)

 

![Onofu](//images.ctfassets.net/ffkp02jwjz54/4EstqP4UtViTgBR3UZfhT0/3b0bf939041611497e50a9579917cb27/Onofu.JPG)

 

We shall be fine. Through the love of God our savior, all will be well. 

![Obendes](//images.ctfassets.net/ffkp02jwjz54/2Ih5FOjCRWUpggqCBzMKVu/5d0c626ad68403673d510d6061324100/Obendes.JPG)

 

I pray for the fortitude to bear this loss. 

![Burial](//images.ctfassets.net/ffkp02jwjz54/1BRNjrCn7NUizn5dWrKQWz/d1f8fc9bb1960893c94da691c952b34f/Burial.JPG)

 

You will always be in my heart. 

![Oremeyi final](//images.ctfassets.net/ffkp02jwjz54/3W7wg6Mypglnb2TjNEBMXf/f24e7d812ce5a9cbcaade909186f0608/Oremeyi_final.JPG)

 

Oizaoshomoshi Martha Obende ❤️️ 
10 January 2022. 

__Oremeyi E. Obende (Sister-in-law)__

Losing you hurts me - every single day I am aware of your absence, it can't be the same without you. I miss you so much.

blog-hero-blessed-assurance

Blessed Assurance - A letter to Oizaoshomoshi Martha Obende

Loss is an interesting thing, and as I type this, I still feel a hole in my heart. The past three weeks have truly been something. 

I've been happy and sad, then happy and sad again. Sometimes, the sadness felt suffocating and like I couldn't breathe through the fact that I had lost you. 

Recently, I began to understand the different responses to grief. There are those that cry it out, eat the sadness away, and there are some that bury themselves into their work and the things around them so as to not think about what happened. 

In the first nine days, I tried my hardest not to think about it until I was alone. And the thing is, the thought of you just resurfaces once in a while. I think of you, and it doesn't hurt, but then I think of you another time, and then it feels like my heart is in pain. It's not, fret not. 

Before you passed and we would talk, you'd tell me, *__"Nono play with your cousins,"__* and I would. I always did. Now, they're not my cousins anymore but my siblings. 

![Onoyimi and Siblings](//images.ctfassets.net/ffkp02jwjz54/7MXcY2CH5GfXGBGT9n717o/ef8654d261eae8f8cf44425839dd7976/Onoyimi_and_Siblings.jpeg)

It was only today that I realized how much I was truly grateful for you. You were the first person who asked the real reason why I wanted to study what I wanted to do. strangely enough, I didn't lie about the reason, and I told you one of the reasons. 

I haven't told a lot of people why, but I told you, and that just made me know how much I trusted you. 

15 years. You knew me for over 15 years, and you loved me for that long. 

That's a long time. How did you do it? 

Today, I felt like I was shaking. yesterday I knew that when I see you for the last time I'd cry. I did, and I haven't stopped crying yet - not physically, but my heart still cries. 

As they said people should throw sand to you I didn't want to do it but i had to. shovels aren't heavy, even with sand, and I say this from experience because I know what it means to hold a shovel but holding it then felt so heavy, and I had to muster up strength to hold still. 

![Aunty Oiza Tomb Stone](//images.ctfassets.net/ffkp02jwjz54/8xrbyz99ejBf73AZRq3WY/b73433ed70fa283df360960b7a722d68/Aunty_Oiza_Tomb_Stone.jpeg)

Kudos to you for holding on for long. People spoke really highly of you, and deep down in me, I wanted to be like you. I wanted faith in God that was as strong as yours, and I wanted to be as strong as you. 

I'm glad that right now, you're free from pain, and you're resting happily. The fact that you're with your Father makes me very assured. 

Someone said today that things will be fine, and I'll learn how to deal with it. So I'll do it. I'll take everything one day at a time, even though I know that I'll miss you a lot. 

Till then, Adieu!! 
__Onoyimi Danielle Obende__

Recently, I began to understand the different responses to grief. There are those that cry it out, eat the sadness away, and there are some that bury themselves into their work and the things around them so as to not think about what happened. 

blog-hero-loss-grief-hope

Loss, Grief, Hope - Getting through the pains of bereavement

__Monday, January 10, 2022__ - the day I received one of the most devastating news ever in my life. My father informed the clan about the passing of my beloved aunt cum mother. Only words that could come forth at that point was 'Oh no😩😭" 

Why you aunty Oiza? Why now? You told me you were getting better. You told me so. What happened? So many questions requiring answers. I choose to write this in some much pains as my foremost way of honouring one __STRONG and 'FAITH-FULL'__ woman I know. Aunty mi, you were strong! You were full of faith!! You fought well!!! 

![oiza](//images.ctfassets.net/ffkp02jwjz54/TTjcxuePfb2B3VfVpPxI3/2abe92a371596c7db77fa8d40ea3e834/oiza.jpg)
 

Aunty Oiza, I did not meet you at home yesterday. They said you were no more. How possible? How?? Aunty mi, you were an embodiment of love. You were accomodating. You held back no love. You were the second mother I had this past few years. You made the house a home indeed. 

Aunty Oiza, You were an addition to the Obende's. This is a big blow to me. This is a big blow to us. We prayed, we trusted God. It's hard convincing myself that this is not a loss from God's perspective. I know God knows all about this and his plans and purposes supersedes our desires and wishes. 

The plan was not for you to leave us this early. You left your two beautiful children - Efi and Hephzibah with the husband of your youth. The thoughts and memories of the unending love you showed these gifts brings tears to my eyes. 

Why so early aunty? I know I may never have answers to these questions, we can only try our best to ensure that these gifts become all that you ever wanted them to become. 

![family](//images.ctfassets.net/ffkp02jwjz54/78qqB5IoHVG4ammpACNhtk/77287eda12900d61f4ff97be546bfb57/family.jpg)

 
In much distress and pains, you yet believed God. I woke up most mornings seeing you in your prayer posture on the couch. When everything seemed frail, you exhibited strength. You were faith in action. 

I try to hold back my tears but then I'm comforted by Apostle Paul's writings in 1 Thessalonians 4:13 - __"But I would not have you to be ignorant, brethren, concerning them which are asleep, that ye sorrow not, even as others which have no hope."__ 

The hope I have is you are with your Lord and your Saviour. 

Thank you for blessing my life with your presence. Thank you for being a blessing to me. I cannot forget you my dearest Aunt and Mom. For all you have done for me, I say __THANK YOU__. 

You have run your own race aunty Oiza, may God give everyone of us you've left behind the grace, courage and strength to run ours well. I will miss you Aunty. I love you dearly Oiza Martha Obende. 

Keep resting with your Lord and Saviour till we meet to part no more on the resurrection morning. 

![oiza marth](//images.ctfassets.net/ffkp02jwjz54/2eoJ82AkSQXqRWR6d8vRuz/8e464fed22eb15e38ab64f2217c05595/oiza_marth.jpg)

## One Year Update (10-01-2023)

We gathered today at Ikeja to celebrate the one-year memorial of my beloved aunt. Another roller-coaster of emotions. Indeed, the memory of the righteous is blessed.

[Memorial Picture](//images.ctfassets.net/ffkp02jwjz54/TheLCDxsYCiggl0BFnVTF/826a6b5d52f22c42b04a1920d399013d/WhatsApp_Image_2023-01-10_at_6.11.42_PM.jpeg)

At the memorial service, the formal introduction of the Othiba Foundation Trust in memory of my beloved aunt was done also. Aunty Oiza was a giver to a fault. Hence, this foundation seeks to give back to the society. The Foundation will put five(5) children/students every year through school and pay their tuition. Also, awards will be given to students in the schools attended by her children at every prize-giving day.

These will be continued in her honour.

You can donate to the foundation using this account detail:

Account Number: 9301400228
Bank: Stanbic IBTC
Account Name: Bamidele Onaivi Obende.

*__Proverbs 10:7a (KJV) - The memory of the just is blessed...__*

Monday, January 10, 2022 - the day I received one of the most devastating news ever in my life. My father informed the clan about the passing of my beloved aunt cum mother. Only words that could come forth at that point was ''Oh no😩😭"

Blog.

I redesigned my portfolio in one day — here's what actually changed

Adding Google Fonts to a Next.js app — the _document way and what I use now

Moving on to greater things - Next Career Steps

Blessed Assurance - A letter to Oizaoshomoshi Martha Obende

Loss, Grief, Hope - Getting through the pains of bereavement

Oiza Martha Obende : One Strong and Faith-FULL woman I know