Portfolio route

Examples for broad programming work, with proof routes behind them.

Use this when a buyer asks for examples first. It starts with clear service buckets, then branches into artifacts, repos, demos, CV, and current public profiles.

start here
web + tools + automations
repos
code + checks + handoff
profiles
99Freelas + Workana

Start here

The clearest examples for normal buyers and technical reviewers.

The cards match the current marketplace positioning: broad programming capacity first, specific delivery examples second.

Web, WordPress and technical fixes portfolio card
web

Web, WordPress and technical fixes

Responsive layout, forms, CTAs, pages, JavaScript bugs, WordPress flow checks, and handoff notes.

Automation, data and dashboards portfolio card
automation

Automation, data and dashboards

Sheets, Excel, CSV, CRM exports, dedupe, validation, scripts, KPIs, and dashboard trust checks.

APIs, integrations and internal MVPs portfolio card
systems

APIs, integrations and internal MVPs

Forms, APIs, webhooks, CRM routing, Python/JavaScript scripts, error handling, and end-to-end tests.

Proof routes

Openable artifacts, demos, and profile checks.

These are useful when someone wants to inspect the work style beyond the cards.

PROOF

Proof library

Public artifacts, sanitized reports, repos, demos, and current profile surfaces in one route.

open proof library
CV

Public CV

Resume-style HTML route for quick review when a marketplace or buyer wants a direct professional summary.

open public CV
PDF

Public CV PDF

Downloadable PDF version for platforms that prefer a file over a browse-first route.

open PDF
DEMO

EXEMPLO-DASHBOARD-1

Neutral synthetic dashboard demo built to look like a normal business tool rather than a stylized portfolio mockup.

open demo
SYNC

Ecommerce mismatch check

Buyer-friendly proof for tracing why prices, products, paid orders or totals do not match from source to dashboard.

open artifact
API

API and webhook health check

Endpoint smoke pass, payload validation, retry behavior, idempotency checks, and rerunnable diagnostics.

open artifact
SHEETS

Google Sheets automation triage

Proof-of-process for Sheets and Apps Script workflows with imports, dedupe, reject rows, run logs, acceptance checks, and handoff.

open artifact
GH

GitHub profile

Public repo surface with technical kits, pinned proof repos, and the same positioning used across other profile lanes.

open GitHub profile
99

99Freelas profile

Current marketplace profile aligned around programming, websites, systems, data, automations, APIs, and concrete portfolio examples.

open 99Freelas profile
WK

Workana profile

Current marketplace profile aligned around broad programming execution, featured project covers, and technical handoff discipline.

open Workana profile

Selected repos

Public kits that map cleanly to common freelance asks.

These are the most useful GitHub surfaces when someone wants to inspect code shape, validation style, or handoff discipline.

QA

QA smoke report kit

Playwright smoke checks, console capture, overflow checks, screenshots, and Markdown report output.

open repo
API

API health check kit

Python endpoint checks with JSON plans, status/timing assertions, reports, fixture server, tests, and handoff notes.

open repo
CRM

CRM import QA kit

Python CSV audit for CRM/RevOps imports with required fields, duplicates, stage mapping, rejects, tests, and handoff notes.

open repo
DASH

Dashboard bugfix playbook

Dependency-free Node audit for dashboard snapshots with before/after fixtures, responsive checks, tests, and handoff notes.

open repo
FLOW

Workflow reliability check kit

Python CSV audit for workflow runs with retry, dedupe, error-code, slow-run, and handoff-ready reliability checks.

open repo
LEADS

Website lead recovery check kit

Python first-pass audit for business websites that checks lead-path basics, contact friction, CTA coverage, and produces handoff-ready reports.

open repo

Public profile surfaces

Current public surfaces, without legacy marketplace noise.

These links help when a buyer wants to verify consistency across the active public stack before starting with a scoped technical pass.

Use it

Prefer this route when a field is labeled portfolio.

It is clearer than sending a bare homepage link, and shorter than sending the full proof library when someone only wants the best entry points first.