feat(ui): Docker support, code quality tooling, and landing page foundation #179
Merged
Tinna23 merged 1 commit intoStellarCommons:mainfrom Mar 24, 2026
Merged
Conversation
|
@Thommyy7 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Tinna23
approved these changes
Mar 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Covers four issues across two concerns — developer experience tooling
and the landing page foundation. These are grouped together as they
are all non-blocking setup work that can land in a single clean PR.
Changes
UI #9 — Docker support
packages/ui/Dockerfile— multi-stage build: deps → builder → runnerusing Next.js standalone output
packages/ui/.dockerignore— excludes node_modules, .next, all .env filesUI #10 — ESLint, Prettier, TypeScript strict mode
.prettierrc— semi, singleQuote, trailingComma all, printWidth 100.prettierignore— excludes .next, out, node_moduleseslint.config.mjs— extends next/core-web-vitals, next/typescript,prettier (prevents ESLint/Prettier rule conflicts)
tsconfig.json— strict: true, noUncheckedIndexedAccess: true enabledpackage.json— format and format:check scripts already presentUI #11 — Landing page foundation
src/components/landing/Navbar.tsx— logo left, GitHub + Open Appbuttons right, transparent background over hero
src/app/page.tsx— landing page root at/, assembles all sectionswith dark background and subtle grid overlay
UI #12 — Hero section and AnimatedDemo
src/components/landing/HeroSection.tsx— headline, subheadline,CTA buttons, overflow-hidden on section to prevent mobile overflow
src/components/landing/AnimatedDemo.tsx— self-contained demowith no real API calls, animates: idle → typing → loading → result,
tab switch triggers exit/enter animation sequence
How to test
Closes
Closes #157
Closes #158
Closes #159
Closes #160