How wjadebead/stickareer works
1. This is a Create React App single-page application, not a multi-service backend system. The architecture is primarily client-side: React components, client-side routing, and static JSON-based data sources. The app is intended to be deployed as a static SPA, with public/_redirects indicating route fallback support.
2. The entry path is the usual CRA shell: src/index.js mounts src/App.js, which then composes the route structure and top-level app layout. Global styling is split between src/index.css, Tailwind (tailwind.config.js), and PostCSS (postcss.config.js).
3. The UI shell is organized around reusable layouts in src/components/AuthLayouts and common chrome in src/components/Navbar. This suggests two major presentation boundaries: authenticated/private flows and public/auth flows. DarkModeButton.jsx indicates theme state is handled at the UI layer rather than by a backend service.
4. Feature pages live under src/pages, with clear domain separation: Main, Login, Community, Hashtag, Information, Mypage, Resumes, and ErrorPage. Each folder is mostly self-contained, with its own page entry component and feature-specific subcomponents.
5. The application appears to be data-driven but front-end-only. Domain data is stored in public/data/.../*.json and mirrored by dummy service modules in src/api/.... This includes community posts, hashtag content, home page box data, information content, and mypage personal data.
6. The “API” layer is not a real network integration in the current repo. Files like src/api/HomePage/BoxDataService.js and the various *Dummy.js modules act as local data providers/adapters, likely returning mocked or imported JSON data to page components. That makes the main boundary one of “UI consuming local mock services,” not “UI calling a remote backend.”
7. State management is centralized in src/stores, with separate modules for login/auth and user data. src/stores/Login/auth.js and src/stores/user.js likely hold session-like and profile-like state that multiple feature areas consume, especially login, mypage, and any authenticated routes.
8. Community is one of the richer feature areas. It includes list and detail flows (Community/index.jsx, PostPage.jsx), a create flow (NewPost.jsx), and loading placeholders (postLoading.jsx). That implies a standard content lifecycle: fetch/mock load posts, render summaries, navigate to detail, and create new content.
9. Mypage is a nested subsystem with both dashboard-like cards and deeper subflows. Cards such as BookmarkCard, InterestCard, NotificationCard, PersonalCard, and PointCard make it a user-profile hub, while JoinPage, PersonalPage, and WithdrawalPage represent onboarding/profile-maintenance/account-closure flows.
10. Hashtag and Information are content presentation modules with lightweight structure. Hashtag has a card/grid pattern plus loading state, while Information has a simpler info display component. These are likely fed from local JSON content and rendered read-only.
11. Login is isolated under src/pages/Login and includes a KakaoLogin.jsx component, which is the only clearly identifiable external-auth touchpoint in the tree. That means authentication is probably a Kakao-based sign-in flow with local app state captured afterward in the auth/user stores.
12. Resumes is another standalone feature area (CreateResumes.jsx and page index), likely a form or editor flow. Together with Mypage and Login, it suggests the app supports user-centric workflows beyond content browsing, but still within the front-end boundary.
13. Supporting files show this is a standard React/PWA-ready static app: public/manifest.json, public/robots.txt, src/reportWebVitals.js, and src/setupTests.js. Dockerfile indicates containerized deployment is supported, but there is no evidence of server-side business logic in this repository.
Main entry points: App.js App · Mypage/index.jsx Mypage · Community/index.jsx Community · Login/index.jsx Login
Components 33
App shell
CRA entrypoint, router, layouts, and shared chrome.
- Entry · Bootstraps the React app and mounts the root tree.
src/index.js - App · Top-level composition for routes and app layout.
src/App.js - Auth layout · Authenticated/private flow wrapper.
src/components/AuthLayouts/AuthLayout.jsx - Public layout · Public/auth flow wrapper.
src/components/AuthLayouts/PublicLayout.jsx - Navbar · Shared top-level navigation chrome.
src/components/Navbar/Navbar.jsx - Theme button · Client-side dark mode toggle.
src/components/Navbar/DarkModeButton.jsx
Feature areas
Route-level pages and their main subflows.
- Main · Primary landing page and home content.
src/pages/Main/index.jsx - Login · Sign-in entry page for the app.
src/pages/Login/index.jsx - Kakao login · External sign-in touchpoint for Kakao authentication.
src/pages/Login/KakaoLogin.jsx - Community · Community feed and post lifecycle routes.
src/pages/Community/index.jsx - Post detail · Detailed post reading flow.
src/pages/Community/PostPage.jsx - New post · Create-post flow for community content.
src/pages/Community/NewPost.jsx - Hashtag · Hashtag browsing and card-based listing.
src/pages/Hashtag/index.jsx - Information · Static informational content display.
src/pages/Information/index.jsx - Mypage · User dashboard and account center.
src/pages/Mypage/index.jsx - Join page · Onboarding and interest selection flow.
src/pages/Mypage/pages/JoinPage/index.jsx - Personal page · Personal information maintenance flow.
src/pages/Mypage/pages/PersonalPage/index.jsx - Withdrawal · Account deletion or departure flow.
src/pages/Mypage/pages/WithdrawalPage/index.jsx - Resumes · Resume creation and editing feature.
src/pages/Resumes/index.jsx - Error page · Fallback route for missing or invalid paths.
src/pages/ErrorPage.jsx
Data and state
Local mock services and centralized client state.
- Community data · Mock/community data adapter backed by JSON.
src/api/Community/communityDummy.js - Post data · Mock post adapter for community detail content.
src/api/Community/postDummy.js - Hashtag data · Mock hashtag content adapter.
src/api/Hashtag/hashtagDummy.js - Box data · Home page data provider for boxed content.
src/api/HomePage/BoxDataService.js - Info data · Mock information content adapter.
src/api/Information/informationDummy.js - Profile data · Mock personal/profile data adapter.
src/api/Mypage/personalDataDummy.js - Auth store · Client auth/session state shared across flows.
src/stores/Login/auth.js - User store · Shared user/profile state for account features.
src/stores/user.js
Static app
Public assets and deployment support files.
- Redirects · Static SPA route fallback support.
public/_redirects - Manifest · App manifest for static/PWA deployment.
public/manifest.json - Global CSS · Base application styling entry.
src/index.css - Tailwind · Utility styling configuration.
tailwind.config.js - PostCSS · CSS processing pipeline configuration.
postcss.config.js
Connections 35
- Entry → App: mounts · Bootstraps the application root.
- App → Auth layout: uses · Wraps private/authenticated routes.
- App → Public layout: uses · Wraps public routes.
- App → Navbar: renders · Includes shared navigation chrome.
- Navbar → Theme button: contains · Theme toggle lives in the navbar.
- App → Main: routes to · Main landing route.
- App → Login: routes to · Public authentication route.
- App → Community: routes to · Community route.
- App → Hashtag: routes to · Hashtag route.
- App → Information: routes to · Information route.
- App → Mypage: routes to · User profile hub route.
- App → Resumes: routes to · Resume feature route.
- App → Error page: fallbacks to · Catch-all invalid route page.
- Login → Kakao login: uses · Delegates sign-in to Kakao flow.
- Login → Auth store: updates · Stores authentication state after login.
- Login → User store: updates · Persists user identity/profile state.
- Main → Box data: loads · Consumes home-page mock data.
- Community → Community data: loads · Reads community feed data.
- Community → Post data: loads · Reads post detail/mock data.
- Community → Post detail: navigates · Opens selected post details.
- Community → New post: navigates · Opens post creation flow.
- Hashtag → Hashtag data: loads · Consumes hashtag content data.
- Information → Info data: loads · Consumes informational content data.
- Mypage → Profile data: loads · Consumes profile-related mock data.
- Mypage → User store: reads · Uses shared user profile state.
- Mypage → Join page: navigates · Entry into onboarding subflow.
- Mypage → Personal page: navigates · Entry into profile-edit subflow.
- Mypage → Withdrawal: navigates · Entry into account-closure subflow.
- Auth layout → Auth store: depends on · Private layout depends on auth state.
- Public layout → Auth store: depends on · Public layout reacts to auth state.
- App → Global CSS: styles · Imports global CSS entry.
- App → Tailwind: styled by · Relies on Tailwind utility setup.
- App → PostCSS: processed by · CSS build pipeline configuration.
- App → Redirects: deploys with · Supports SPA route fallback on static hosting.
- App → Manifest: deploys with · Static app manifest support.