WFieldwork Studio
WordPress plugin concept · Interactive demo
Simulation · no live CDN connectionAll changes stay in this page.
EdgePress FREE

A simpler path to the edge.

Connect your site. Choose what stays out of cache. Check the rules before you save.

Example WordPress site
fieldwork.test
An invented site for this prototype
Demo disconnected
01 / Configure

Cache exclusions

Demo defaults

Keep sensitive pages out of the path cache model. Start with the example store rules, then add your own.

One path per line. Literal paths or one trailing * only, such as /private/*. Case sensitive. No regex, query strings or encoded paths. Maximum 50 rules.

This demonstrates path matching only. Cookie, login, request method and WooCommerce session safeguards still need integration validation.

Connect the demo profile to review and save.

02 / Check

Try a few paths

LOCAL CHECK

Results use your current editor rules. “No path exclusion” means no rule matched, not proof the CDN will cache the response.

Use https://fieldwork.test with a plain path. No query string, fragment, credentials or other host.

Free / first scope

CDN connection + exclusions

The narrow experience shown here. Live onboarding, DNS and TLS need a test customer walkthrough.

Optional / unverified

Image transformation

Keep separate until EdgePrizm confirms the available API and where transformation runs.

Pro / later

Security, WAF and bots

Outside this Free prototype. Product availability and API coverage need their own validation.

Engineering evidence & what unlocks a live demo

A documented route, with one critical check

The published API documents a gateway and runtime discovery of rewrite options in a customer shortname and DeliveryTemplate context. The schema for the exact exclusion option still needs authenticated discovery.

  1. Discover options. Request the approved template with the customer shortname.
    GET /apigw/v1/config/option/deliveryTemplate/{deliveryTemplateName}?shortname={shortname}&size=all
  2. Read the existing delivery. Preserve a complete baseline. The documented delivery PUT is a full replacement, so submitting only one changed field is unsafe.
  3. Map and validate the exclusion option. The vendor’s actual regex dialect, escaping, limits and precedence are unverified. This prototype deliberately uses a small local path grammar.
  4. Write, then read back. Check the saved record, job completion where applicable, edge propagation and actual HTTP cache behavior on an approved test site. API readback alone does not prove edge behavior.

Ask EdgePrizm for this development package

  • A least-privilege development client_id and client_secret, scoped to a test customer. Store credentials on the server, never in the browser or this artifact.
  • The customer shortname, delivery UUID, exact DeliveryTemplate and permitted read/write scope.
  • An approved disposable WordPress test site, origin and onboarding instructions for DNS ownership, TLS and rollback.
  • A working exclusion-option example, allowed syntax, limits, activation timing and a successful update/readback example.
  • Confirmation of the image transformation endpoint and entitlement, if it belongs in the first release.

What this demo proves: the small UI can be built and its interaction tested now. It does not prove authenticated API access, complete onboarding or safe cache behavior.

Official API documentation ↗