SSG = for static pages at fixed urls , /about etc (basically pre-rendering to static html in /dist )

SSR = spa pages where metadata injected based on space

for ease of maintenance and additional seo, other static pages may be served from kinopio-client

Requires a vite update to support ?

replace vite.config w nuxt.config

What’s the relationship bw both. To upgrade vue do I need to upgrade nuxt? And vice versa?

+data → +config? → +head? → +layout? → +page

/pages/+config.js

sublayouts wrapped in parent folder layout

<Layout>      ⟸ pages/+Layout.js
  <Layout>    ⟸ pages/(marketing)/+Layout.js
    <Page />

/pages/+Layout.vue

use folder config to enable ssr in marketing pages

/pages/index/.. replaces vue router

Nuxt is a bit more magical and has auto module importing tho

Nuxt replacing vue in package.json means that vue upgrades limited to nuxt support?

/pages/index/+Page.vue

/pages/+onCreateApp.js ??

+data?, fetch seo meta (replaces netlify edge function file)

space urls work like prod

move /add page/view to standalone

/temp static page

native apps always skip / marketing page

remove cookie on sign out

no cookie User:

cookie User:

Mixed Navigation:

Just +head for static pages

+Data and +head flow for spa pages

/pages/about Vike Router (Primary)

/pages/+Head.vue

or /layouts/LayoutDefault.vue basically App.vue

space.vue to pages/[...space].vue , acts like a router, setting globalstore vars and then navigateTo('/')

package.json nuxt replaces vue and vue-router

not owned by vercel, so less enshittification risk

it’s documentation is the most barebones

good if i was only doing one static page, but i think it’s very likely the marketing page would have subpages . i really don’t like how it requires putting routing logic in vite.config

/about , about/features , about/work

less breaking releases

folder based routing has some clarity advantages over file based

less architecture changes

for seo purposes, need to serve static marketing site to new users