Skip to content

feat: document frontend tooling decisions and tradeoffs#26

Open
jkumari08 wants to merge 2 commits intomainfrom
feat/frontend-tooling-baseline
Open

feat: document frontend tooling decisions and tradeoffs#26
jkumari08 wants to merge 2 commits intomainfrom
feat/frontend-tooling-baseline

Conversation

@jkumari08
Copy link
Copy Markdown
Collaborator

Documents the frontend tooling choices for the project so future contributors understand what was picked and why. Adds docs/frontend-tooling.md covering Next.js 16, TypeScript, Tailwind CSS v4, ESLint + Prettier, and Turbopack — with tradeoffs and notes on when to revisit each decision. Links the doc from the README.

Closes #11

Scaffold Next.js 16 + TypeScript app with Tailwind CSS, ESLint, and Prettier.
Set up shared app shell (header with wallet placeholder, content area),
empty state and error boundary components, and project structure
(app, components, lib, styles). Add dev/build/lint/format/typecheck scripts.

Closes #1
Add docs/frontend-tooling.md explaining why Next.js, TypeScript, Tailwind,
ESLint + Prettier, and Turbopack were chosen, with notes on when to revisit.
Link the decision doc from README.

Closes #11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Establish a modern frontend tooling baseline for React development

1 participant