thefunnyday/doubleyou

Purpose and runtime

DoubleYou is an archived Nuxt 3 microblogging application: authenticated users publish short posts with images and interact through a social feed. It runs as a Nuxt client/server application locally or in production, with Supabase providing the database, authentication, and likely realtime/storage-backed features. Global styling is SCSS.

Key entry points: app.vue, nuxt.config.ts, and pages/index.vue.

Application shell and shared UI

app.vue establishes the Nuxt application shell. Shared layout-level UI is split into reusable header, navigation, loading, modal, and image-viewing components:

• components/Header.vue

• components/Menu/left.vue

• components/Menu/right.vue

• components/Loading.vue

• components/ModalPopup.vue

• components/ViewImage.vue

Responsive navigation has a dedicated mobile variant at components/Menu/mobile.vue.

Route-driven feature surfaces

Nuxt file routes define the primary product surfaces:

• Main feed: pages/index.vue

• Individual post view: pages/post/[postId].vue

• Public profile view: pages/user/[userNickname].vue

• Authentication: pages/login.vue

• Account preferences and user-list views: pages/settings.vue, pages/userlists.vue

• Informational and monetization pages: pages/about.vue, pages/premium.vue

Dynamic route parameters form the boundary between browser navigation and resource-specific post/profile retrieval.

Authentication boundary

Supabase Auth is the identity provider. middleware/auth.ts is the route-access control point, protecting pages that require a session and redirecting unauthenticated users as appropriate. The auth UI is isolated in components/Auth/Page.vue, while pages/login.vue exposes it as a route-level entry point.

Control flow is: route navigation → auth middleware/session check → page rendering → Supabase-authenticated data operations.

Social content flow

The feed and post-detail routes are the core content pipeline. Users create/read microblog posts from the feed, navigate to records by postId, and access authors by nickname. README-declared likes, comments, image attachments, and realtime feed behavior are UI/data concerns centered on:

• pages/index.vue

• pages/post/[postId].vue

• pages/user/[userNickname].vue

• components/ViewImage.vue

Supabase is the external persistence and realtime boundary; browser UI should not own authoritative post, interaction, or identity state.

Administrative and secondary flows

An administrative surface exists at pages/admin/index.vue, separate from normal user routes and likely requiring stronger authorization than baseline authentication. Additional standalone pages include pages/test.vue and pages/about.vue; they are not core feed-path entry points.

Client presentation and assets

Global visual rules live in assets/styles/global.scss. Client-only theme behavior is initialized through plugins/theme.client.js, making theme state/browser APIs explicitly client-bound. Static media is served from public, notably public/about-video.mp4 and premium assets under public/premium.