Trailrunner 19
AvailableOff-road · 19 ft
Engineering Lab
Explore the system. Change the state.
Working sandboxes for frontend, backend, WordPress, APIs, automation, and evidence retrieval. Change an input and inspect what happens next.
Representative Demonstration. Interactive Demonstration
Sandbox records are fictional and stay in your browser. The API and retrieval explorers read this portfolio’s public records. No demonstration sends email, SMS, or WhatsApp messages.
01 / Frontend · WordPress · Performance
Structured inventory with useful filtering.
A representative content-driven interface based on repository evidence for inventory, model data, filters, and responsive presentation.
Inventory interaction
Local demo
Inventory explorer
Find the right model.
A small, focused interaction can turn a large content set into a useful sales surface.
models match
No models match. Try another category or search.
Horizon Family 22
On requestFamily · 22 ft
Summit Touring 21
AvailableTouring · 21 ft
Canyon Weekender 17
ReservedCompact · 17 ft
Selected model
Trailrunner 19 specifications
- Layout
- Rear lounge
- Sleeps
- 4 people
- Best for
- Remote touring
Horizon Family 22 specifications
- Layout
- Family bunk
- Sleeps
- 6 people
- Best for
- Long weekends
Summit Touring 21 specifications
- Layout
- Island bed
- Sleeps
- 4 people
- Best for
- Road touring
Canyon Weekender 17 specifications
- Layout
- Compact lounge
- Sleeps
- 2 people
- Best for
- Short escapes
Try the quote wizard · Progressive form state
Interactive quote wizard
Turn a model choice into a next step.
Choose a model
When would you like to explore it?
Demo request complete.
Selected model · selected use · selected timing
This result stays in the demonstration only. No enquiry was sent or stored.
How it works · Filtering and derived state
Search, category, and availability combine to filter the same structured data. Sorting changes the presentation order; the match count is derived from the active filters. The quote wizard carries the selected model into a separate form flow. Technology: Blade, Alpine.js, and JavaScript. Four fictional records keep the interaction inspectable. No request is submitted.
More interface experiments · Maps and inbox review
Location interaction capability
Make a distributed network easier to explore.
An interactive map with real OpenStreetMap tiles, generalized public regions, marker selection, and contextual detail.
The locations are broad public regions used to demonstrate the interaction. They do not identify clients, private addresses, or project ownership.
Location interaction
Generalized regions
The map loads when this panel is in view.
Selected region
3 locationsMetro Manila
AvailableA generalized public region used to demonstrate marker selection and contextual detail. It does not identify a client or private address.
Geelong
AvailableA generalized public region used to demonstrate a second map state without attributing work to a specific location.
Perth
AvailableA generalized public region used to demonstrate a third map state while keeping client and project locations private.
Map tiles are provided by OpenStreetMap. Markers represent generalized public regions for this isolated demonstration only.
Business application capability
A calmer view of operational data.
This representative dashboard preview reflects the kinds of structured records, tabs, summaries, and role-aware administration used in business applications.
Operations interaction
Local demo
Operations dashboard
Good morning, Demo Admin.
People
248
Leave to review
12
Reports
08
People workspace
Local demonstration records, filters, and controlled actions show the surface without exposing real personnel data.
Integration capability
Keep conversations and delivery state visible.
A safe inbox interaction demonstrates channel-aware threads and an operational state change without making any external provider connection.
Messaging interaction
Local demo
Inbox
3 demonstration threadsEmail thread
Avery Morgan
Can we review the onboarding timeline?
Reviewed in this demo.
SMS thread
Jordan Lee
The revised proposal is ready for review.
Reviewed in this demo.
WhatsApp thread
Taylor Brooks
Thanks, I have received the document.
Reviewed in this demo.
No email, SMS, WhatsApp, Twilio, webhook, or production API service is connected to this demonstration.
02 / Backend · Business workflows
A decision changes the system.
Review fictional leave requests. Each permitted transition updates the record, filters, and report from the same state.
Select Start review to begin.
How it works · State transitions and derived reporting
Submitted → In review → Approved or Declined. A declined request can be reopened. Invalid transitions are rejected by a shared state function; totals are calculated from records rather than stored separately. This browser sandbox demonstrates workflow rules, not production authorization or payroll processing. Technology: JavaScript modules and immutable record updates. Related project: Enterprise HRIS.
03 / APIs · Automation
Make the delivery state visible.
Step through a message lifecycle. Introduce a failure, retry the same message, and inspect the transition history.
- 01Contact
- 02Message
- 03Queue
- 04Processing
- 05Delivery
- 06Status
Transition history
Pure browser simulation. No email, SMS, WhatsApp, webhook, or production service is called. No real message is sent or stored.
How it works · Failure boundaries and retries
A finite state machine advances one step at a time. Processing can fail; retry returns the existing message to the queue. Reset cancels any pending timer. The simulation demonstrates observable state, not a production queue or a delivery guarantee. Technology: JavaScript and local timers. Related project: Unified Messaging Portal.
04 / APIs · Public data
Inspect the real response.
Send a read-only request to this portfolio. The response uses an explicit list of public fields.
Ready. Choose an endpoint to begin.
No request sent yet.
How it works · A public serialization boundary
Laravel reads published content through Eloquent scopes, then returns only approved fields as JSON. Each endpoint is read-only and rate-limited. Missing or private project slugs return 404. The time shown is the actual browser round trip for this request, not a benchmark.
05 / AI engineering concepts · Retrieval
Show the evidence before the answer.
Inspect the retrieval stage of an evidence-grounded workflow. This working implementation uses local topic and keyword matching, with no language model.
- 01Query
- 02Topics
- 03Public records
- 04Matches
- 05Excerpts
- 06Source links
Ready to retrieve public evidence.
Run a query to see topics, matched terms, excerpts, and source links.
How it works · Grounding and the limits of matching
Queries are validated, normalized, and matched to capability synonyms. Public project, experience, and skill records are ranked by matching terms. Responses quote the record and link to the source. There are no generated claims, private documents, embeddings, agents, or provider calls in this mode. Keyword retrieval can miss semantic connections; an unmatched result is not proof that the experience does not exist. Use the visitor-friendly evidence explorer.
Quality / Interactive engineering examples
Make the edge cases visible.
These small experiments use fictional input and illustrative values. They do not submit a request or measure a client website.
06 / Validation simulation
Invalid is a useful state.
Try an empty name or malformed email, then correct the fields. All input stays in this demonstration.
07 / Performance model
Load less. Defer the rest.
Compare transfer cost in a fictional gallery of twelve equal-sized images. This is arithmetic, not a measured website score.
Deferring assets reduces initial transfer; it does not eliminate the cost if the visitor views everything. Loading the first visible image promptly avoids delaying the primary content.
08 / Accessibility experiment
A complete path by keyboard.
Use Tab to focus the controls and Enter or Space to activate them. Run a brief signal transition, then compare it with reduced motion.
Ready. The signal is at rest.
Need a workflow previewed?