Overall template structure

Templates are collected under a single folder, called TATTLER_TEMPLATE_BASE.

Get used to where it is, because you’ll spend the bulk of your time inside it over the next few weeks 😉

Scopes

The TATTLER_TEMPLATE_BASE folder contains one sub-folder for each scope.

And each scope-folder contains events for that scope. If scopes confuse you, define them later, together with your developer.

You can start by wrapping all events into one single scope – say “myWebApp” – so your TATTLER_TEMPLATE_BASE folder structure would look like this:

templates_base/
├── mywebapp/                       <-- a scope
└── my_booking_sys/                 <-- another scope

Events

Events are folders within a scope. So once you create folders – under your scope “myWebApp” – for the events your fantasy product manager, your TATTLER_TEMPLATE_BASE would look like this:

templates_base/
└── mywebapp/                       <-- a scope
    ├── reservation_confirmed/      <- an event
    └── password_changed/           <- another event

Vectors

Each event may require being sent over email and SMS.

Your product manager told you which event needs to be sent with which vector:

• reservation_confirmed: email only.

• password_changed: email and SMS.

We’ll now proceed to build those.