First time wiring the Nuxt SDK, is this really all the setup?
Coming off a heavier client-side testing tool, I had blocked out a couple of days for the integration because that is what the last one took. Instead I ran the CLI init, added the provider, and had a slot resolving on the server almost immediately.
That felt too easy, so I want a sanity check from people who have run this in production. Did I skip something important, or is that genuinely the whole setup?
2 answers
That is genuinely it. The CLI init wires the SDK and generates the slot types, so you are left with a single command plus registering the provider. Content resolves server-side in Nuxt, which is why your slot showed up in the initial HTML instead of swapping in later.
The one check worth doing to confirm it is really live: open the Integration page on the dashboard and look for the green "Received traffic in the past 24 hours" indicator. Once that is green you know traffic is flowing and you did not miss a step.
Nothing missing. The one thing I would do next, not for setup but for peace of mind later, is pin your slot versions in the fetch (slot-id@2 instead of bare slot-id). An unpinned slot resolves to latest, so a future content publish can change what renders without a deploy. Pinning locks the schema until you decide to bump it. Otherwise you are done.
Pinning the versions now, good call. And honestly the whole setup was one command and a provider, and content was resolving server-side before I even finished my coffee. Nice change of pace from the last tool.