PP

Engine and showroom

PixelPiraterij World

Template routes, live demos, product proof and system notes under the PixelPiraterij umbrella.

Faster starts
with better
framing.

Templates inside PixelPiraterij World are here to shorten the road without flattening the result. They should feel like shaped starting systems, not like cheap escape hatches.

01

Grouped by who they help most.

The point is not to flood the world with skins. The point is to give each audience a cleaner route into something stronger.

Founders and launch sites

Sharper starting structures for products that need to look credible fast without collapsing into template sameness.

  • Launch-led layouts
  • Trust-first framing
  • Clear path back to custom work

Hospitality and premium service

Calmer starts that understand conversion, trust and atmosphere instead of brochure pressure.

  • Booking-aware flow
  • Premium restraint
  • Audience-specific copy rhythm

Culture and labels

Campaign and release routes that can hold identity without losing operational structure.

  • Editorial mood
  • Release-aware structure
  • Expandable into broader worlds

02

Current starters based on existing PixelPiraterij directions.

These are not fake examples. They are current routes that can become starter systems, because the audience logic and visual direction already exist.

Utility starterPixelPiraterij utility suiteBranded route panel

PixelPiraterij utility suite

A compact monetized starter for app-like offers where pricing, unlock logic and calm presentation already need to feel premium.

  • Paid starter logic
  • Compact offer framing
  • Good route for utility-first products
Hospitality starterLe RadelBranded route panel

Le Radel

An audience-shaped route for calmer hospitality brands that need trust and atmosphere before hard conversion pressure.

  • Booking-aware structure
  • Calm premium tone
  • Audience-led page rhythm
Cultural starterHermes RecordsBranded route panel

Hermes Records

A culture-facing release world that proves templates can still carry editorial identity and sharper visual authorship.

  • Release-first structure
  • Editorial presence
  • Expandable into broader worldbuilding
Software starterEvaQuantBranded route panel

EvaQuant

A product-facing direction showing that templates here can also grow toward dashboards, tools and operator logic.

  • System hierarchy
  • Dashboard-capable framing
  • Useful bridge into builder logic

03

What people can actually change inside this setup.

The builder should not be sold as magic. It should be shown as editable layers inside a strong starting system.

Brand layer

Swap logo, palette, type and tone so the starter becomes recognizably yours instead of staying a neutral shell.

  • Logo and marks
  • Palette and surface mood
  • Typography and tone direction

Page structure

Adjust section order, route emphasis and CTA logic without rebuilding the whole system from scratch.

  • Section sequencing
  • Hero and CTA emphasis
  • Audience-aware page rhythm

Content and media

Replace copy, visuals, screenshots and proof so the route starts selling a real business instead of a demo shell.

  • Copy and positioning
  • Visual proof
  • Offer and pricing blocks

Publish layer

Preview, check breakpoints and push live into a hosted route that can later expand into deeper studio or system work.

  • Responsive preview
  • Launch checks
  • Bridge into hosting and next steps

04

How someone builds and launches from here.

This is the route from current showcase to future builder: choose the right starter, configure it, preview it properly and publish it into a real surface.

Starter

Pick a route that already fits the audience and product category instead of beginning from a generic blank slate.

Config

Apply brand settings, page structure and offer logic inside a controlled setup that keeps the quality bar intact.

Preview

Review the route across breakpoints, tighten proof and adjust the conversion path before anything goes live.

Go live

Publish into a managed route that can later expand into deeper hosting, custom studio work or a larger product layer.

05

The builder should emerge from capability.

That is why this route still matters before the builder is fully mature. It shows the sequencing instead of overselling the fantasy.

Start

Pick the route first: template, app, docs or lab. The point is clarity before spectacle.

Frame

Use the route pages to understand what is public, what is active and what is still maturing.

Bridge

When a route needs heavier custom work or managed hosting, move back into pixelpiraterij.nl without losing context.

Expand

The world should grow out of visible capability, not out of promises that outrun the product.

If you need a stronger start, the template lane is where the world opens.

Use this side for route clarity and category fit. Move back into the flagship when the build needs custom authorship or managed depth.