Skip to content
casen swartz.let’s talk

Less chasing.More creating.

One connected place for your website, feedback, project work, and business records. Keep everyday updates in your hands and bigger changes moving.

One home.
Your own address.

A place on the web with your name on it. The planned address is simple: our domain, followed by your business name.

Illustrative addresses. Public hosting is being prepared.
devtoolshome.com/fieldwork-gardens
Fieldwork Gardens

A little room to grow.

Thoughtful gardens. Everyday joy.

An example of your public website

A preview only. This doesn’t create or reserve a site.

Your workspace, messages, and drafts stay behind sign-in.
Make it yours
A little structure
See the possibilities
A conversation
An idea
A next step

From a small edit to the next big idea.

See how a project moves through DevTools. Every change has a place, from the first draft to the final invoice.

Your next update. Your call.

Change a headline, swap a photo, add a page, or reuse a collection across your website. The design stays consistent while you take care of the content.

Save a draft and open a private preview before anyone else sees it. Compare the changes, then publish a captured version when it is ready.

Plan ahead with a scheduled release, or restore an earlier version to draft. A scheduled release takes effect on the next website or workspace read after its due time.

DevTools · Illustrative example
Content & releasesFieldwork studio
Homepage headlineA fresh welcome
Image & alternative textThe new collection
About page introductionMade for everyday life
Saved draftPrivate previewPublished release

Your public website changes only when a release is published.

Your content stays a draft until someone with publishing access releases it.

Don’t just read about it. Take the controls.

Try editing the headline, save your draft, then publish the example. Use the sidebar to explore more of the workspace.

Interactive example · No account needed

Your content

Up to date

Small edits. On your terms.

26/100 · This is example content.

Change the headline to start the workflow.

devtoolshome.com/fieldwork
fieldwork.Published example

Good things, made by hand.

Thoughtful work for everyday spaces.

Made with care.
Built to be useful.
  1. 1
    Edit

    Make a change in the editor.

  2. 2
    Save draft

    Check the saved preview.

  3. 3
    Publish example

    Update the published version.

Saved draft

Good things, made by hand.

Published example

Good things, made by hand.

Start by changing the headline.

A simplified, interactive tour of real DevTools workflows. All records are fictional; changes stay in this page and reset when you leave.

Small details. The whole picture.

Explore the complete toolkit, from a single image to a scheduled release, a pinned request, or a customer invoice. Open a category or expand the full guide.

01

Content

Add and edit text, images, links, notices, and supported listings. Change a headline or description without editing code. The website’s custom design determines how each piece appears.

02

Pages & collections

Manage page paths, navigation order, visibility, and search titles and descriptions. Group reusable content in collections and connect it to one or more pages.

03

Media library

Upload PNG, JPG, and WebP images, add alternative text, and reuse them across your website. Draft uploads stay private until a published piece of content uses them.

04

Drafts, previews & releases

Save without changing the public website. Preview your saved draft, compare public changes, then publish a release or schedule a captured version. Restore an earlier release to draft before publishing it again. Scheduled releases apply on the next website or workspace read after their due time.

05

Website settings

Keep your website name and description together. Settings follow the same draft and release process as your content, so saved changes do not immediately become public.

What you can see and do depends on your assigned role.

Connected where it counts. Private where it matters.

Your website team and your designer work from their own spaces. Conversations, requests, and agreed work connect them—without turning your customer records into shared project files.

Your workspace

  • Website contentEveryday updates, at your pace
  • Feedback & decisionsYour perspective, in context
  • Customer records & invoicesFor permitted business roles
Our shared projectConversations · Requests · Agreed work

My workspace

  • Assigned websitesBuild, maintain, and improve
  • Conversations & estimatesA clear next step, together
  • Work & billingMy side of the business

Your customer finances and my agency finances stay separate. Shared work does not mean shared access to everything.

The right tools. For the right people.

Choose a role to see how responsibilities are divided. These are individual role examples; a person with more than one membership may have combined access.

An assigned designer can work on the website without access to your customer finances.

Owner access

Prepare content & images Included
Publish a website release Included
Chat & leave review feedback Included
Approve a client review Included
Manage customer finances Included
Accept a shared estimate Included
Manage client team access Included

The details, without the mystery.

Straight answers about how DevTools works today and what comes next.

Is this a drag-and-drop website builder?

No. I build the layout and connect the editable parts to DevTools. You manage the content in those parts. New layouts and larger structural changes are work we plan together.

Does saving make a change public?

No. Saving updates your draft. A preview shows that saved draft, and publishing makes a captured version public. Restoring a previous release also returns it to draft first. The example above lets you try that separation.

Can my team use it?

Yes, through the implemented role and invitation system. Access depends on each person’s role. Editors cannot publish or access customer finances; publishers can publish; business staff can manage customer records. Account setup and invitation delivery are currently managed steps.

What is ready today?

DevTools is a working local application with connected website editing, collaboration, project tracking, and private business records. Stripe is connected in sandbox mode. Public hosting, live payments, and external email, SMS, or push notifications are not live. Production onboarding, recurring billing, and tax setup still need their own configuration and validation.

Can I try it without an account?

You can use the interactive example on this page. It follows the product’s workflows using fictional records, and changes last only while this page is open. A real workspace requires sign-in and access to an assigned website.

Your website could work like this.

Talk about your project

Make an update. Make it yours.

Add pages, text, images, and listings. Save a draft, preview the changes, then choose when to publish. Everyday updates stay in your hands.

Keep the conversation connected.

Message me privately from your workspace. Our conversations stay alongside your website, so questions and decisions have a place to live.

Point to it. We’ll work through it.

Pin feedback to the page, request changes, and follow their progress. Review estimates and scope before we move ahead with bigger ideas.

A clearer view of the business side.

Keep invoices, deposits, payment records, and receipts organized. Your customer payments and the invoices for my work each have their own place. Stripe checkout is being connected in test mode; online collection is not live yet.