Your account

Your theme on your own machine

Edit your theme as ordinary files, run it against your own events, and send it back when it is ready.

What you can do here

Sign your machine in to Tito

Approve the command line from a browser you are already signed in to, once per machine.

4 steps

Start a theme project

Scaffold a folder for your theme and fill it with what your account has today.

4 steps

Run your theme on your own machine

Run your theme on your laptop against your own events, and see every save on the next reload.

4 steps

Share a preview before anything goes live

Send a colleague a link to the theme running on your laptop, without publishing anything.

3 steps

Send your theme back up to Tito

Publish the folder you've been working in, which goes live immediately and touches only your theme.

3 steps

This is developer work.

The Customize studio changes the colors, images and wording on every screen people see, against a live preview and with nothing to install. Start there.

Rebuilding the pages themselves is done in your own editor, with your own version history, and a way to see the result before anybody else does.

That's what titogo is for: a command you run in a terminal that brings your theme down as a folder of files, runs your site on your own machine, and sends your work back up when you're happy with it. The files are the same ones you can edit one at a time in Custom themes, on the theme's own page.

go.tito.io/acme/admin/looks

The loop

titogo init starts a folder for your theme, and a git repository to keep its history in.
titogo login signs this machine in. Once per machine, and it works out which account from the folder.
titogo pull brings a theme down into that folder, along with your events, ticket types and colors.
titogo local runs your site on your own machine, off those files. Save a file, reload the page, see the change. It also gives you a link you can send somebody.
titogo push sends the folder back up, live straight away.

One folder holds one theme.

If your account has several custom themes, each one gets its own folder. titogo pull -look "Summer series" starts a folder off on that theme, by name or by the id in its address. A folder stays on that theme from then on, and prints its name every time you pull or push. Without -look you get your account default.

A fresh pull plus local already renders your real site.

It comes up in your own colors with an empty views/ folder. Theme files are overrides, so write a file for the page you want to change.

Getting the command

Download it from your downloads page, signed in as yourself. Pick the file for your machine, where Apple silicon is the usual one for a Mac bought since 2020. Rename it to titogo, put it somewhere on your path, and make it executable with chmod +x titogo. titogo version tells you which one you have.

Good to know

Your bookers' data stays in your account.

A pull brings configuration: events, ticket types, fields, audiences, custom pages, theme files and your colors. Orders, attendees, email addresses, answers anyone gave you, keys and secrets all stay where they are. The folder is something you can safely hand to a designer.

A push replaces that theme entirely.

Anything the theme has that isn't in your folder goes with the push, and your other themes aren't changed. Tito refuses a push that would overwrite work somebody else did in the meantime, and tells you what it would have destroyed. See Send your theme back up to Tito.

Whoever does the work needs enough access to manage your account's settings. Somebody who can only work the door signs in and is turned away by titogo pull.