Website production • Responsive design • SEO foundations

I build websites that make sense to real people.

I like the point where design, content, code, and everyday problem solving meet. Give me a blank page, a tangled site, or something half-built—I’ll learn what it needs to do and work toward the most useful next version.

See the websites How I work

Not an agency machine. A hands-on builder who asks questions, checks the details, and keeps learning.

HOW I THINK ABOUT A BUILDSTRUCTURE • CONTENT • CODE • TEST

The work, not the pitch

Here are the websites.

These are working demonstrations—not placeholder dashboards. Open them, resize them, follow the navigation, and inspect how the pages are put together.

01 / LIVE DEMO

Green Knack Lawn Co.

A complete local-service website built around a simple human truth: the customer would rather enjoy the weekend than spend it behind a lawnmower.

Multi-page service architecture
Tampa location content and local SEO structure
Responsive navigation, video, forms, and calls to action
Service-area pages, metadata, schema, sitemap, and accessibility

Why it matters for this role: It shows that I can take a business idea from structure and messaging through front-end production, search foundations, mobile behavior, and final QA.

Explore live website ↗

Green Knack Lawn Co.

Homepage messageYour weekend shouldn’t start with a lawnmower.

02 / LIVE DEMO

TrueFlow Plumbing Co.

A direct, conversion-focused plumbing website designed to help someone with a stressful problem understand the service and find the next step quickly.

Clear service hierarchy and emergency-oriented messaging
Purposeful imagery and high-contrast conversion paths
Responsive layouts and practical page structure
Search-friendly titles, content, image handling, and markup

Why it matters for this role: It demonstrates a different brand voice and visual system while keeping the same production discipline underneath.

Explore live website ↗

TrueFlow Plumbing Co.

Homepage messagePlumbing problems, solved fast.

03 / PROJECT

Multi-Service Commercial Website

A large service offering organized into a maintainable page system instead of forcing every capability into one oversized page.

Service-page architecture and connected navigation
Responsive layouts and reusable content patterns
Internal linking and focused calls to action
Anonymized where client privacy matters

Why it matters for this role: This is the kind of careful page production, content organization, and website maintenance I would bring to an existing WordPress and Elementor system.

View project ↗

Commercial service website

How I approach the work

Useful over impressive.

I’m not interested in making something complicated just so it looks clever. A small thing that works is more valuable than an elaborate system nobody wants to use.

My career started in operations and leadership, where schedules, communication, quality, customer expectations, and day-to-day execution all connect. That experience still shapes how I build websites: understand the real problem, use the right tool, explain things plainly, and leave the process stronger than I found it.

Learn the problem first.

Listen, understand the context, and know what actually needs to improve before reaching for a tool.

Use the right tool—not the trendiest one.

The stack should make the work clearer, faster, or easier to maintain.

Make complicated things easier.

Good structure and plain communication help customers, teams, and projects move with less friction.

Keep learning honestly.

If I know the answer, I’ll explain it plainly. If I don’t, I’ll say so and figure out whether I can solve it responsibly.

The practical workflow

How a website gets from idea to useful.

01Understand
Business, audience, content, current problems, and the next useful action.
02Structure
Pages, navigation, hierarchy, search topics, and visitor paths.
03Build
Responsive components, content, forms, metadata, and integrations.
04Test
Desktop, tablet, mobile, links, forms, accessibility, and performance.
05Improve
Watch what happens, fix what gets in the way, and document the lesson.

Tampa local search

A location page does not work alone.

A strong Tampa page should help a real person understand whether the business serves their area and why it is relevant. Behind that page, the business profile, contact information, reviews, local content, citations, and internal links should reinforce the same story.

This is the thinking behind the Green Knack location structure—and the kind of connected website work I would bring to a multi-location firm.

Illustrative workflow only. This does not represent Cantrell Schuette’s analytics or current SEO architecture.

TAMPALOCATION
PAGEclear local intent

01Business profileaccurate categories, hours, services

02NAP consistencysame name, address, phone

03Reviewstrust and lived experience

04Local contentuseful Tampa-specific context

05Citationsconsistent business references

06Internal linksconnected services and topics

Before publish

Building the page is only half the job.

I check the work where people will actually use it. Not only in a desktop browser at the size that happened to look best while I was designing.

PAGE REVIEW

Content reads like a person wrote it
Navigation and calls to action work
Layout holds at real screen sizes
Images are useful, sized, and described
Headings and metadata make sense
Forms, focus states, and keyboard paths work
No broken links, overflow, or console errors

Why this role

I want to do the work, not stand near it.

This role caught my attention because the center of it is practical website work: building and updating pages, keeping content accurate, checking the details, and helping the larger digital system stay organized.

I’ve worked in roles where the useful person is the one who notices what needs doing, learns the system, communicates clearly, and follows the work through. That is how I approach websites, too.

I would come in ready to learn Cantrell Schuette’s standards and Elementor system first—then become someone the Marketing Manager can trust to move website work forward without creating more work behind it.

— Leon Smallwood

WHAT I’D BRING

Hands-on website production
Responsive front-end judgment
WordPress and Elementor experience
SEO foundations built into the page
Clear writing and proofreading
Careful QA and follow-through
Operations experience with real people and deadlines

The next step

Let’s talk about the websites.

I’d welcome the chance to walk through the builds, explain the decisions, and learn more about how Cantrell Schuette’s website work moves from request to publish.

Email Leon ↗Visit Lost A Digit Digital

LEON SMALLWOODhello@lostadigitdigital.com 813-596-0944 LinkedIn ↗Tampa, Florida