A website can tell people what you do.

But I wanted mine to tell people why I do it, how I think, and what I value.

When I started working on this website, I knew I wanted a professional portfolio that represented my experience in website management, digital strategy, content, and technology.

But I eventually realized that simply listing my skills and projects wasn’t enough.

I wanted the website itself to demonstrate the way I approach digital work.

So I started with the smallest visual element: the logo.

Starting with the logo

The logo became the foundation of the visual identity.

I wanted something simple enough to be remembered but personal enough to feel like mine. I didn’t want a complicated symbol that needed a long explanation. I wanted something that could work across my website, portfolio, documents, and other digital spaces.

The goal was simplicity.

But simplicity isn’t always simple to achieve.

A logo can look good on its own and still feel wrong when placed beside the rest of a website. So I kept looking at it together with the typography, spacing, colours, and overall layout.

Eventually, I realized that the logo didn’t need to tell my entire story by itself.

It simply needed to belong to the story.

The three upward strokes represent purpose, people, and progress. They are also inspired by the letters M and F, creating a subtle connection to my name and making the mark personally meaningful to me. The upward movement reflects growth and forward direction, while the green accent represents life, renewal, and possibility.

Together, the mark represents my belief that digital work should be more than functional. It should have purpose, serve people, and create meaningful progress.

And that became the approach I took with the entire website.

Finding the right green

Colour was another decision I didn’t want to make casually.

I eventually settled on #429A39 as the green used throughout the website.

For me, green represents growth, progress, and something alive and continually developing.

But I also wanted it to feel grounded.

I didn’t want the website to look overly flashy or overly corporate. I wanted the colour to provide energy while allowing the content and message to remain the focus.

That is why I use the green intentionally rather than covering the entire website with it.

It appears where I want the eye to notice something, whether that is a word, a heading, an important detail, or a call to action.

I also wanted the green in the logo and the green used throughout the website to feel like they belonged to the same system.

The logo shouldn’t feel like it came from one brand while the website came from another.

They needed to speak the same visual language.

Why I chose a black background

The black background was also a deliberate choice.

I wanted the website to feel focused, confident, and contemporary, while giving the content enough space to stand on its own.

Black creates a strong visual foundation for the green #429A39. Instead of competing with the accent colour, it allows the green to stand out when it needs to.

It also creates contrast.

The typography becomes easier to distinguish, important words have more visual weight, and elements can breathe without the page feeling visually crowded.

But there was another reason I chose black.

I wanted the website to feel different from the typical professional portfolio.

A lot of portfolio websites rely heavily on white backgrounds, light colours, and conventional layouts. There is nothing wrong with that approach, but it didn’t feel like the right expression of how I wanted to present my work.

The darker foundation gives the website a stronger sense of identity while allowing the content, green accents, and typography to create the visual hierarchy.

It also reflects something about how I think about digital work.

Not everything needs to compete for attention.

Sometimes, the best design decision is to create enough space for the important things to be noticed.

For me, the black background isn’t there simply to make the website look modern.

It is there to create focus, contrast, and clarity.

And that is ultimately what I want the design to do: support the message rather than become the message.

Typography: making the words feel like the brand

Typography was another part of the process.

I spent time looking at fonts because the words on a website are not separate from its design.

They are part of the design.

The same sentence can feel completely different depending on the typeface, weight, spacing, and size.

I wanted the typography to feel modern and professional without becoming cold.

I wanted it to have personality without becoming distracting.

Most importantly, I wanted it to remain readable.

Design should support communication, not compete with it.

Then came the words

Once I had the visual direction, I started thinking more carefully about what I actually wanted to say.

This was probably one of the most important parts of building the website.

I didn’t want the homepage to simply say:

“I am a website manager. Here are my skills. Here are my services.”

There are many websites that can say that.

I wanted mine to communicate something more meaningful.

Eventually, three words became the foundation:

Purpose. People. Progress.

These three words describe how I want to approach digital work.

Purpose

I believe a website should have a reason behind it.

Every page should serve a purpose.

Every piece of content should have a reason for being there.

Every design decision should contribute to the experience.

A website shouldn’t exist simply because a business needs to “have a website.”

It should help people understand, discover, connect, decide, or act.

People

Technology is important.

Design is important.

SEO is important.

Performance is important.

But behind all of these things are people.

Someone is reading the page.

Someone is searching for an answer.

Someone is trying to understand a service.

Someone is deciding whether they can trust a business.

That person is the reason the website exists.

So I don’t want to build websites only from a technical or visual perspective.

I want to think about the experience from the person’s side.

Progress

And then there is progress.

A website shouldn’t be treated as something that is built once and forgotten.

It needs to evolve.

Content changes.

Businesses change.

Technology changes.

Search behaviour changes.

People’s expectations change.

There is always something that can be improved.

That is why website management, to me, isn’t simply keeping a website online.

It is about helping it move forward.

Speed matters. But so does quality.

This is something I have learned through experience.

I understand the pressure to get a website done quickly.

There are deadlines.

There are campaigns waiting to launch.

There are businesses waiting for their new website.

There are stakeholders asking when something will be ready.

Sometimes, fast is necessary.

I understand that.

But I have also seen what can happen when speed becomes the only measure of success.

When the mindset becomes “We just need to get it live,” quality can quietly become the thing that gets sacrificed.

Content gets rushed.

Pages don’t get reviewed properly.

Small usability problems are overlooked.

Mobile experiences aren’t given enough attention.

Images aren’t optimized.

SEO details are missed.

Links aren’t checked carefully.

Forms aren’t tested thoroughly.

And sometimes, decisions that should have been considered carefully are simply pushed through because there isn’t enough time.

The website goes live.

The deadline is met.

But the work isn’t necessarily finished.

That distinction matters to me.

Fast doesn’t have to be careless.

I don’t believe the answer is to take forever to build a website.

A good digital professional needs to understand deadlines, priorities, budgets, and business needs.

The goal isn’t slow versus fast.

The goal is efficient without sacrificing quality.

There is a difference.

Good planning can make a project faster.

Clear priorities can make decisions faster.

A well structured workflow can reduce unnecessary revisions.

Good communication can prevent problems before they happen.

And thoughtful systems can help teams move quickly without constantly cutting corners.

For me, the question isn’t:

“How quickly can we get this website live?”

It is:

“How quickly can we get this website right?”

Those are two very different questions.

Design gets reviewed. So does everything else.

This thinking eventually influenced one of the statements on my website:

Design gets reviewed. Copy gets reviewed. So do speed and visibility, every single build.

I included this because I don’t believe a website should be judged by only one thing.

A beautiful design matters.

Good writing matters.

Performance matters.

Search visibility matters.

Usability matters.

Technical quality matters.

The experience matters.

They all work together.

A website that looks beautiful but is difficult to use has a problem.

A website that loads quickly but communicates poorly has a problem.

A website with great content that nobody can find has a problem.

And a website that does everything technically right but doesn’t connect with people has a problem too.

Good digital work requires looking at the whole picture.

Built to be found.

This works on two levels.

The obvious meaning is discoverability.

A website needs to be found through search engines and other digital channels.

But being found is only the beginning.

Once someone finds a website, they need to understand it.

They need to find their way around it.

They need to find the information they came for.

They need to know what to do next.

So for me, “Built to be found” isn’t simply about SEO, AEO, or GEO. It reflects a broader approach to making a website discoverable, understandable, and useful across search engines, answer engines, and AI driven search experiences.

There is little value in being found if people cannot find what they need.

The website became part of the portfolio

At some point, I realized something important.

I wasn’t just building a portfolio to show my work.

I was building a website that would demonstrate my work.

The website itself became part of the portfolio.

The structure demonstrates how I think about information.

The content demonstrates how I communicate.

The typography demonstrates attention to detail.

The colours demonstrate consistency.

The navigation demonstrates usability.

The performance demonstrates technical care.

The overall experience demonstrates how I approach a digital presence.

Technology is also part of how I work today. I use modern tools, including AI, to help me explore ideas, research, refine content, and work through problems. These tools can help me move more efficiently, but they don’t replace the thinking behind the work.

I remain responsible for the decisions, the direction, the refinement, and the final result.

For me, using technology well means knowing when a tool can help and when human judgment matters most.

As I worked through the website, I found myself constantly refining the content, not because I wanted to keep changing things, but because I wanted every section to earn its place.

Some ideas stayed.

Others were simplified or removed.

That process reminded me that good digital work isn’t always about adding more.

Sometimes, it is about knowing what doesn’t need to be there.

In other words:

The website has to practice what I say I believe.

If I say websites should be clear, mine should be clear.

If I say websites should be purposeful, mine should have purpose.

If I say websites should be built for people, mine should be easy to understand and navigate.

If I say websites should continually improve, I should be willing to keep improving mine too.

More than a portfolio

This is why this website became more than a collection of my experience.

It became a reflection of how I work.

From the logo to the green #429A39.

From the black background to the typography and spacing.

From the homepage structure to the smallest piece of copy.

From Purpose. People. Progress. to Built to be found.

None of these things exist completely on their own.

They are pieces of the same idea.

I want to create digital experiences with intention.

I want to understand the people on the other side of the screen.

I want to use technology intelligently without losing the human judgment behind the work.

I want to build websites that are useful, clear, visible, and continually improving.

And I want the work to have a reason behind it.

The story is still being written

Perhaps the most honest part of this website is that it isn’t finished.

And I don’t mean that technically.

I mean that I am still learning, still refining, and still growing.

My approach to digital work will continue to evolve.

The website will probably change again.

The content will change.

The design may change.

New projects will be added.

Old ideas may be replaced by better ones.

And that’s okay.

Because progress doesn’t mean everything is perfect.

It means you keep moving forward.

So this website isn’t the final version of my story.

It is simply where the story is right now.

Purpose. People. Progress.

Built to be found.

And built to keep becoming better.