Skip to content
BrooKo.UK // skills map

Skills & Learning

A clearer breakdown of what I can do now, what I’ve learnt by building, and what I’m currently improving.

Jump to: What I can do What I’ve learnt Currently learning Toolbox

What I can do now

Not just a tag list — this is the practical work I can actually put together.
Ask about a job
frontend

Websites & UI polish

I can build clean, responsive pages with a consistent design system, tidy navigation, reusable headers/footers, themed error pages, and spacing that feels intentional instead of crowded.

  • HTML5, modern CSS, Grid/Flexbox, Bootstrap, and mobile cleanup.
  • Dark/terminal Overnet-style interfaces with the neon green accent I like now.
  • Cleaner layouts for home pages, about pages, dashboards, and small business sites.
HTML5 • CSS • Bootstrap • Responsive UI
backend

PHP apps & database systems

I’m comfortable building the foundations of database-backed apps: installers, login flows, roles, permissions, settings screens, and admin areas that can grow without turning into one giant file.

  • PHP 8.3/8.4-ready structure with shared includes and cleaner routing.
  • MariaDB/MySQL with PDO, prepared statements, password hashing, and CSRF checks.
  • Updater packages that can change files and database tables in a controlled way.
PHP • MariaDB • PDO • Installers • Updaters
infrastructure

Homelab, hosting & access

I can plan and troubleshoot practical self-hosted setups: services in Proxmox, DNS that makes sense, reverse proxy routing, certificates, VPN access, and storage paths that are easier to maintain.

  • Proxmox VMs/LXCs, Linux basics, TrueNAS shares, SMB/NFS, and service separation.
  • Nginx Proxy Manager, Cloudflare DNS, Pi-hole local DNS, and HTTPS routing.
  • Log reading, permission fixes, route testing, and safer public write-ups.
Proxmox • NPM • Cloudflare • Pi-hole • TrueNAS

What I’ve learnt by building

The lessons that keep showing up across my sites, apps, and GGLABS work.

Structure first, then style

A good-looking site still breaks down if the folders, routes, includes, and shared files are messy. I’ve learnt to set the structure early so future updates are easier.

  • Keep public pages, admin areas, APIs, installers, and assets separated.
  • Use clean routes instead of awkward query-string navigation.
  • Centralise shared headers, footers, CSS, and error pages.

Permissions need proper planning

Roles and permissions have to match the real workflow. A System Administrator should see app settings, while managers, drivers, porters, clients, and normal users should only see what they need.

  • Plan users, roles, permissions, settings, and ownership before building screens.
  • Separate admin dashboards from management or workload dashboards.
  • Make access checks consistent instead of hiding links only in the UI.

Troubleshooting has an order

The fastest fix usually comes from testing the simplest thing first: direct service, logs, permissions, DNS, proxy, then browser cache. Guessing wastes time.

  • Check the backend directly before blaming Nginx Proxy Manager.
  • Read logs and test file paths instead of only looking at the browser error.
  • Document the working route once it’s fixed so it can be repeated.

UI has to stay readable

The theme matters, but readability matters more. I’ve learnt to avoid oversized layouts, scrollers inside scrollers, noisy green effects, and navs that try to show everything at once.

  • Use clear hierarchy, sensible spacing, and readable card sizes.
  • Keep nav simple first, then add submenus only where they help.
  • Use the Overnet look as a clean shell, not a messy glow layer.

Currently learning

The active focus list — mainly things I’m learning by building, breaking, fixing, and simplifying.
01

Overnet Web Manager

A custom web control manager for the admin side of the network: sites, domain folders, settings, file editing, updates, users, and System Administrator permissions.

Admin UI • File editor • Roles • Updates
02

Better PHP architecture

Cleaner controllers, shared helpers, API endpoints, JSON responses, frontend feedback, and a safer updater flow that can change both code and schema without wrecking an install.

Controllers • APIs • JSON • Migrations
03

Self-hosted services & media

Home Assistant integrations, Jellyfin/custom media frontend ideas, practical dashboards, and self-hosted radio/audio streaming concepts.

Home Assistant • Jellyfin • Dashboards • Streaming
04

Packaging, docs & handoff

Release zips, version bumps, changelogs, roadmaps, install blocks, and AI handoff notes so each project can be continued without starting from scratch.

Versioning • Changelogs • Docs • Installer blocks

Toolbox

A compact reference, kept readable instead of turning the whole page into badges.

Web

HTML5, CSS Grid/Flexbox, Bootstrap, JavaScript, ES modules, Fetch API, JSON APIs, PWA basics, service workers.

Backend

PHP 8.3/8.4 readiness, MariaDB/MySQL, PDO, prepared statements, password hashing, CSRF protection, installers.

Systems

Windows 11 daily, Linux Mint experience, Debian/Ubuntu, Proxmox, LXCs/VMs, TrueNAS, SMB/NFS, NPM, Cloudflare, Pi-hole, WireGuard.

Design

Dark UI, terminal aesthetic, neon green accent, readable hierarchy, consistent spacing, reusable components.

Learning style

Build it, break it, fix it, simplify it, then document it so it can be repeated.
Let’s talk Back to top