Dotdeck

Dotdeck Overview

My previous approach to sharing dotfiles was a monolithic repo. Dotdeck trims that pain by focusing on standalone, copy-pastable “decks” you can browse, search, fork, and discuss without peeling through hundreds of commits.

Why Dotdeck?

• Finding a single snippet buried in a six-year-old thread is exhausting.
• Decks are intentionally scoped: title, tags, thumbnail, description, and code block(s).
• Built-in reactions and comments keep discussion near the snippet instead of scattered across forums.

Features (Snapshot)

• Full-text search with pagination for fast discovery.
• Authentication + JWT (register/login) and role-based access control (admin/mod/user).
• Like/dislike counts and threaded comments with optimistic updates.
• Image uploads (WebP, compressed via Sharp) for deck thumbnails.
• Admin panel for managing tags, decks, users, and audit logs.
• Dark/light themes powered by the Rose Pine palette.
• Fully documented OpenAPI 3.0 spec exposed via Swagger.

Tech Stack

Sample Deck Schema (WIP)

Deck {
id: string
title: string
tags: string[]
description: string
codeBlocks: Array<{ language: string; content: string }>
likes: number
dislikes: number
createdBy: UserId
createdAt: Date
}

Roadmap

• Hook up moderation tools for reporting abusive decks/comments.
• Finish audit log views in the admin dashboard.
• Publish the public SDK + CLI for pushing decks from local repos.

*** End Patch