fix /inbox route

test /group/invite

spacestore.changeSpace

how does /views/space.vue turn into something inside /plages

current router -> spaceStore.initializeSpace() -> windowhistoryhandler

when the new user comes to kinopio.club their browser should fetch static html of an about/marketing page (eg /about is a page that is accessed through the path , or from the root for new users)

Upsides - Separation of concerns: content pages and Kinopio client are completely independent of each other - Maximum freedom of choice for used tools

how does the current router change to use the nuxt router

todo look into nuxt

easier to update help sites bc they’re already in there

structure: /components/about rootpage , /components/help contains a bunch vue files

the old site gets moved to a ‘secret’ url, bc visits to it get redirected

reverse proxy will make a request to the help. site and serve to that /help

same seperate repos for help. site etc

Downsides - Mixed frameworks in same codebase - Multistep deployment pipeline

Downsides - Less flexibility in tool choice

Using Netlify proxy to keep codebases separate

Downsides - More custom Netlify configuration - More dependence on Netlify

Upsides - One codebase - Maximum reusability of components and styles - Simple deployment pipeline

Use Vite to generate static site instead of SPA

Upsides - Flexibility in choice of SSG

Static site generator (SSG) inside public folder

eventually , i’d like to be able to use this architecture to include a blog like site (https://www.are.na/editorial)

I haven’t look at it too much but i think astro might be a good static site generator:

Step 1, get it to work w just a static about page

step 2. Get it to work w Astro w a shared vue components (eg AboutMe.vue has no depencies)

After getting it to work, submit the site to google for reindexing

can use vue components from kinopio-client (e.g. Pricing.vue, signup signin, about, etc.)

can make the ergonomics match the app (eg pug and styl)

edge function uses cookie to know whether to show users the app , or send them the html of the static /about page

Use cookies to determine whether root url should redirect to an app. Cookie is just a bool showShowApp or something like that

have a static site generator inside the public folder of a vue app and sending users to static pages based on url?

maintaining seperate subsites like kinopio-help is also more of a pain bc it’s a whole seperate repo and I can’t reuse components or styles bw them

Right now when you go to kinopio.club you just get thrown into the app, which is really low friction. But also doesn’t let me do a great job of explaining the app and it’s ethos

while there’s lots of websites linking to kinopio, search engines don’t really know what kinopio is because they can’t parse SPAs because of this, kinopio has really bad SEO which makes it hard for people to find when searching for things like ‘mind-mapping’, etc.

the actual specific page contents/design i can do later

this is just about coming up with a nice architecture that doesn’t feel gross to add to kinopio-client

Basically I’d like to have something similar to are.na, where /arbitrary-page and /about are served right from the same site and don’t redirect you to a subdomain