Working on it

Choose how people identify themselves and when their identity is verified.

The committed settings that make the kit yours, and the flags that decide which optional features exist.

One class, three channels, and the user decides which of them reach them.

The committed list of owners, what it unlocks beyond the admin role, and how the seeder treats them.

The super-administrator page at /admin/dev, every tool on it, and how to add yours.

What ships under /admin, who gets in, and how to add a screen of your own.

The keys, flags and webhook that make subscriptions exist, and what appears once they do.

Build a plan in the admin panel, price it per country and interval, and follow what a subscriber can do with it.

From a fresh clone to the application open in your browser, signed in as admin.

How the language of a page is chosen, how strings are written and translated, and how to add a language.

Ask for the password or PIN again, force a password change, act as a user, block an account.

How the one-time codes travel, who sends them, and the fields that ask for them.

Make the site installable, generate its icons, and let a browser receive push notifications.

The commands you run every day, the tests, the checks before a push and where things live.

The providers config/ai.php knows, the two features that use them, and how to call one yourself.

The mail transports the kit knows, the keys each one reads, and the two providers that can carry a text message.

Declare a capability in code, price it in the admin panel, and let people switch it on, buy it or receive it with their plan.

Every variable read from .env, its default, and which ones to set before the first boot.

A four-digit code people set once and type before sensitive actions.

Every date is stored in UTC and shown in the person's timezone, without code on your side.

What the kit records on its own — model changes, every email and SMS, every webhook — and where to read it.

Take a single payment for something that is neither a plan nor an add-on, and confirm it before you deliver.

Where the country of a visitor comes from, where it is kept, and what reads it.

The base model, the custom casts, defaults, enums, macros, helpers, categories and stubs you build your own features on.

What a signed-in person can change about themselves under /account, and what each screen needs from you to work.

What each chart on /admin counts, where its numbers come from, how to add one, and how visitor tracking feeds Facebook.

Where uploaded files go, why S3 is the default, and how a Livewire upload is stored through the media library.

Let a new subscriber try a paid plan before paying, and accept Stripe promotion codes at checkout.

Where each route file is loaded, what runs on every request, and how pages, sidebars and the loading overlay fit together.

Where errors are written, how often they are reported, how to get them in Slack, and the tools that find slow pages and N+1 queries.

Give every user a link, record who arrives through it, and credit a reward when they register and when they pay.

Declare what a plan can switch on and how much of something it allows, set the numbers per plan, and enforce them in your own code.

The billing cycles you offer, the currency each price and each report uses, the daily rate sync behind the revenue chart, and the switches that turn the package off.

Create a meter in the admin panel, spend a unit with one line of code, and let people buy packages in advance or pay for what they used when the cycle closes.