WEBVTT

1
00:00:00.480 --> 00:00:03.750
This is your client's site, and they run it on their own.

2
00:00:03.830 --> 00:00:06.960
Every page, every class, every event:

3
00:00:07.040 --> 00:00:11.490
they manage it all in the CMS, and the layout never breaks.

4
00:00:11.570 --> 00:00:15.510
And right beside them, an AI assistant that knows their back office,

5
00:00:15.590 --> 00:00:18.140
and exactly how their site works.

6
00:00:18.630 --> 00:00:20.710
So how did we get here?

7
00:00:20.790 --> 00:00:22.380
Let's rewind.

8
00:00:25.880 --> 00:00:29.120
First, use your favourite agent, like Claude Code,

9
00:00:29.200 --> 00:00:30.720
to build your prototype.

10
00:00:30.800 --> 00:00:33.440
The design is exactly the way you want,

11
00:00:33.520 --> 00:00:36.190
but the content is hard-coded.

12
00:00:36.980 --> 00:00:39.260
Next, a one-time setup:

13
00:00:39.340 --> 00:00:42.260
the Quilium MCP, the CLI,

14
00:00:42.340 --> 00:00:45.340
and most importantly, the Quilium skills,

15
00:00:45.420 --> 00:00:47.770
the method your agent follows.

16
00:00:49.980 --> 00:00:53.020
One prompt, and the agent creates the site,

17
00:00:53.100 --> 00:00:56.300
reads your prototype and proposes an architecture.

18
00:00:56.380 --> 00:00:57.600
You approve.

19
00:00:57.680 --> 00:01:00.240
It defines the data structure in YAML,

20
00:01:00.320 --> 00:01:03.500
then turns your HTML into templates.

21
00:01:03.580 --> 00:01:06.060
Now it fills everything in:

22
00:01:06.140 --> 00:01:10.000
images, collections, pages, and their content.

23
00:01:10.080 --> 00:01:14.040
Plus a content kit: every block on one page,

24
00:01:14.120 --> 00:01:16.790
for your client to reuse anywhere.

25
00:01:16.880 --> 00:01:18.470
The site is ready.

26
00:01:19.780 --> 00:01:24.020
Here's the preview: your design, down to the pixel.

27
00:01:24.100 --> 00:01:27.770
Except everything is now managed in the CMS.

28
00:01:28.780 --> 00:01:30.700
Now your client takes over,

29
00:01:30.780 --> 00:01:34.050
with an assistant built right into the CMS.

30
00:01:34.280 --> 00:01:36.460
Full for the next two hours?

31
00:01:36.540 --> 00:01:39.850
One sentence, and the whole site says so.

32
00:01:41.180 --> 00:01:44.060
An event? They drop in the flyer.

33
00:01:44.140 --> 00:01:46.140
The assistant creates the event,

34
00:01:46.220 --> 00:01:48.700
then builds its page from the content kit,

35
00:01:48.780 --> 00:01:51.570
with a sign-up form and its emails.

36
00:01:54.480 --> 00:01:58.270
One more sentence: the event leads the home page,

37
00:01:58.350 --> 00:02:00.020
and it's published.

38
00:02:01.270 --> 00:02:04.340
A visitor signs up: they get their confirmation,

39
00:02:04.420 --> 00:02:07.390
and their request lands in the back office.

40
00:02:08.180 --> 00:02:10.380
And that's just some examples:

41
00:02:10.460 --> 00:02:13.770
whatever they need next is one sentence away.

42
00:02:14.380 --> 00:02:17.660
Your prototype, your agent, and Quilium.

43
00:02:17.740 --> 00:02:21.570
Everything's ready for you, at quilium.io.

44
00:02:22.480 --> 00:02:25.990
Start for free, and go live when you're ready.
