Selected work / Founder-built digital product / Ongoing

I didn't just design a website.

I designed a brand, planned a product, built a complex WordPress experience, untangled the data behind it and developed the marketing strategy to help people find it.

NightScanner is the project. This is the story of the thinking, creativity, technical work and persistence behind it.

Creative direction & designUX & product thinkingWordPress developmentSEO & content strategyData & systems

One project. Many disciplines.Scroll for the work ↓

01 / The brief I gave myself

✳

A real idea is easy. Making it work? Different story.

I wanted to tackle a very specific problem: the amount of searching, comparing and second-guessing involved in choosing somewhere to go out.

But I wasn't interested in simply drawing a homepage and calling it a concept. I wanted to work through the entire problem — from the first screen someone sees to the information underneath every listing.

That meant stepping between roles constantly: researcher, brand designer, UX designer, WordPress builder, content strategist, SEO, data wrangler and the person trying to figure out why a result was showing twice.

This is a founder-led collaborative venture, not a paid client case study. I'm showing it here because it offers a particularly honest look at how I approach ambitious digital work.

RESEARCH ✳ DESIGN ✳ BUILD ✳ TEST ✳ REWORK ✳ REPEAT ✳RESEARCH ✳ DESIGN ✳ BUILD ✳ TEST ✳ REWORK ✳ REPEAT ✳

02 / Creative direction

First, I gave it something to say.

A directory could have looked like a spreadsheet wearing a nice shirt. I wanted more personality than that — something clear and useful, but also lively enough to feel like the beginning of a night out.

My work covered the creative direction of the identity and interface: the brand personality, content hierarchy, typography, colour choices, recurring design patterns, visual treatments and the way the product speaks to people.

The difficult bit was restraint. It needed energy without turning discovery into a visual obstacle course. The design has to help someone make a decision, not compete with the decision.

The work I want to demonstrate here isn't just that I can make things look good. It's that I can establish a visual system and use it to solve a practical problem across a growing website.

Illustrative design-study mock-up
Interface direction
Less looking.
More doing.
What are you in the mood for? ⌕
Tonight
↗
Near you
↗
Deals
↗
Events
↗

The creative decisions behind a usable brand

01 / Brand

Personality

A clear, approachable tone with enough playfulness to be memorable.

02 / UI

Hierarchy

Make the next useful action obvious, especially on a small screen.

03 / System

Consistency

Reusable components instead of inventing a new layout for every page.

04 / Content

Clarity

Plain-language categories, concise labels and genuinely helpful details.

03 / UX & product strategy

Pretty doesn't help if people can't find anything.

Before obsessing over individual pages, I mapped what visitors would actually be trying to do. Sometimes they know the venue. Sometimes they know the suburb. Sometimes all they know is that it's Friday and they want something fun.

Those are different journeys. I worked through the site architecture, discovery paths, navigation, event categories, filtering, search controls, mobile behaviour and the information needed to make a confident choice.

I also looked beyond the public-facing journey. Venue owners need a straightforward way to keep information current. That creates a second experience to design, with different tasks and friction points.

My design questions became: What does this person need to know now? What's getting in their way? And can the same system handle the next hundred pages without becoming a maintenance nightmare?

Three user needs. Three different pathways.

“What can we do tonight?”

Lead with date, category, availability of information and relevant event results.

“What's around this area?”

Lead with location, venues, nearby events and useful local context.

“I run a venue.”

Lead with corrections, submissions, claiming a listing and straightforward next steps.

Journey illustrations show design reasoning, not verified usability test results.

↗

Information architecture

Connecting categories, venues, individual events, dates and suburbs without making users learn the underlying system.

◉

Responsive decisions

Thinking about filters, search, cards, readability and tap targets when the desktop space disappears.

✳

Reusable UX patterns

Designing a common experience for repeated page types, rather than dozens of bespoke one-offs.

04 / Hands-on development

Then I had to make the whole thing behave.

NightScanner involves far more than a standard brochure website. I'm working across WordPress, Divi, GeoDirectory, event systems, data imports, page templates, styling, plugins, relationships between records and the awkward little edge cases that only show up when real content arrives.

I’ve worked on the structures behind venue pages, event pages, category discovery and recurring listings. I’ve also had to think about imports, record relationships and the accuracy of the results visitors actually see.

It means switching between design thinking and debugging: something can be technically valid in an event record, yet display incorrectly in the category search results. That's not a copywriting problem. It's a systems problem.

What I enjoy is the connection between the two: understanding enough of the technical layer to protect the user experience, and enough of the user experience to know which technical problems matter most.

Conceptual architecture diagram
Behind a result card
What the visitor sees

A clear event, location and date
↑
Event record

Category · time · recurrence
Venue record

Place · address · details
Templates

Display · navigation · mobile
Data checks

Duplicates · accuracy · updates
An explanatory diagram, not a literal database schema.

Where creativity meets technical judgment

01

Template design

Build one scalable pattern for related pages instead of repeating design decisions dozens of times.

02

CMS architecture

Structure venue, event, date and category information to support both publishing and discovery.

03

Data imports

Work with venue identifiers, structured CSV files and event data rather than relying on manual entry for every record.

04

Debugging

Investigate front-end duplication and recurring-date display issues without assuming the underlying event needs deleting.

05

Maintainability

Choose practical workflows, reuse functioning tools and keep unnecessary complexity under control.

A recurring thought during the build

Good design isn't just how a page looks. It's what happens when someone tries to use it.

05 / Data & operational design

The unglamorous work that makes it useful.

This might be the least photogenic chapter in the case study. It's also one of the most valuable.

Directory websites only work when their information is good enough to trust. I've spent time researching events and venues, preparing structured records, working through category systems and figuring out how to manage things that repeat weekly or change at short notice.

That creates a whole other set of design questions. What's the source of truth? How do we match an event to its venue? What happens when dates repeat? How do we correct an inaccurate listing without breaking the rest of the system?

The aim isn't to collect as many listings as possible and hope for the best. It's to make the information useful and the maintenance process sustainable.

I've also worked through the venue-owner side: what a correction request needs to capture, whether registration is necessary and how to make submissions simpler while the product is still young.

SOURCE

Research

Find credible information and distinguish a venue from an event.

STRUCTURE

Model

Organise fields, relationships, locations and recurring dates.

CHECK

Validate

Look for mismatches, duplicates, stale listings and display problems.

MAINTAIN

Improve

Develop a practical route for future corrections and submissions.

The difference

More listings are not automatically a better user experience.

The quality of the information — and how easily someone can act on it — is the product.

06 / SEO & content strategy

I thought about search before writing the pages.

My marketing background shaped the product from the start. I looked at competing discovery websites, real search behaviour, the relationship between suburbs and categories, and the kind of questions people ask when they don't yet know where they're going.

That thinking influences the information architecture: event categories, venue pages, location-led discovery, useful guides and the internal links between them.

I've worked on search-focused content topics and opportunities including live music, trivia, open mic nights, food specials and neighbourhood guides — topics tied to an actual decision someone is trying to make.

I'm also working through the technical side of SEO: how templates are indexed, whether pages have meaningful unique content, how titles and headings work across repeating page types and how to avoid scaling up thin or duplicate pages.

It's not SEO bolted onto a finished site. It's SEO helping inform how the site is structured in the first place.

My process

Search intent → useful page → clearer next action

“Trivia in Sydney tonight”

Needs a category, a location and relevant dates — not an essay about trivia.

“Cheap chicken wings near me”

Needs current deals and a credible way to check details.

“Live jazz on Sunday”

Needs a specific kind of event at a useful time, with a clear path to the venue.

These are illustrative intent examples, not claims that NightScanner ranks for these searches.

Research

See the market

Study comparable services and identify gaps worth solving, rather than copying their layouts.

Structure

Build for intent

Connect category, location, venue and event information in ways that support users and search engines.

Execution

Keep it useful

Create purposeful content, check indexability and improve the experience instead of chasing page count.

07 / Business thinking

I also had to ask, is this worth building?

It's easy to come up with a long list of clever features. It's harder to choose which ones are worth the time, the cost and the ongoing maintenance.

I've been part of shaping the commercial thinking behind the product, balancing the public discovery experience with the needs of venues that might eventually pay for visibility or promotional options.

That includes looking at competitor offerings, practical venue workflows, possible revenue opportunities and the sequencing of an MVP. It also means recognising when the sensible answer is a simple form and a manual workflow, not another elaborate system.

This is a useful skill to show prospective clients: I don't just ask what we could build. I ask what it needs to achieve, who will maintain it and whether it makes commercial sense.

A practical decision filter

01

Need
Does it solve a genuine user or business problem?

02

Effort
How much work will it take to build and maintain?

03

Timing
Does it matter now, or can it wait?

04

Evidence
What would tell us it's actually working?

08 / The honest picture

What's built. What's not. What I've learnt.

NightScanner is a live, evolving product, which makes it a useful — and imperfect — portfolio piece. Public venue and event pages, category discovery and editorial content exist. The site has a functioning technical and content foundation.

There are still issues being worked through, including duplicated event search results in some categories, event-data quality, reusable category and suburb systems, and lower-friction venue-owner flows. I wouldn't present those as finished.

But the unresolved parts matter to the story. A real project forces trade-offs. It tests your decisions in a way a static concept never can. You learn what needs a stronger system, what needs simpler design and what should never have been quite so complicated in the first place.

And yes, sometimes you find yourself investigating a bug for far longer than anyone expected. Glamorous? Not particularly. Valuable? Absolutely.

Built / in use

Present

  • Brand and visual direction
  • Public venue and event discovery experience
  • WordPress directory and event infrastructure
  • Category and content publishing
  • Research and SEO-led editorial work

Active improvement

In progress

  • Duplicate results and event recurrence handling
  • Data accuracy and scalable maintenance
  • Reusable category and suburb templates
  • Venue-owner submission and correction journeys
  • Technical SEO, performance and usability QA

What this work says about me

01

I can start from a blank page.

Research a problem, develop a concept and make a visual and strategic direction concrete.

02

I see design and development together.

Not just how a screen should look, but what has to happen behind it for the experience to work.

03

I think about discoverability early.

Search behaviour, useful content and structure inform the product rather than arriving at the end.

04

I'm comfortable with the complicated bits.

Imports, templates, records, plugins, bugs and the practical decisions that connect everything.

05

I care whether it makes business sense.

A good idea still needs sensible priorities, a maintainable workflow and a reason to exist.

The point of showing this

Not a product pitch.
A working example.

NightScanner is an independent venture I'm building collaboratively. It isn't an In Tandem client project and I'm not claiming sole credit for every contribution. My work spans creative direction, product and UX thinking, web implementation, SEO, research, content and problem-solving.

What I hope comes across is that I enjoy the whole puzzle: understanding a problem, finding a useful direction, creating something people can actually use and staying with it when the difficult parts emerge.

That's what I bring to my marketing and digital work. A mix of big-picture thinking and sleeves-rolled-up execution.

Portfolio concept prepared in October 2026. Interface diagrams are conceptual recreations, not screenshots of the live product. No traffic, revenue, customer growth or ranking results are claimed without supporting evidence.

In Tandem / The work behind the work

Big ideas.
Sleeves rolled up.

If you're looking for someone who can see the strategic picture, design the experience and get into the practical work of making it happen, that's where I do my best work.