Visit the site

March 2024 ~ June 2024 (3.5 months)

This is a personal project I undertook to practice Next.js. It is a renewal of the Archon V1 project, which was originally written in vanilla JavaScript.

• Reimplemented the entire application, including the design, content hierarchy, category-based articles, bookmarks, and article recommendations, with several other improvements.
• Navigation Improvement: Improved the behavior of the main menu and topic menu.
• Top Messages: Displayed top messages based on user events, such as adding or removing bookmarks, or clicking the link copy button.
• Newsletter Subscription Confirmation: Upon entering information in the newsletter form, a confirmation email is sent to the user.
• Improved Article Recommendation Logic: The trending article list is shown based on the actual number of clicks by users, which reflects the most clicked articles in the past 3 months.
• Responsive Design: Improved the design to be more mobile-friendly.

• Utilized SSR (Server-Side Rendering) with Next.js and focused on distinguishing CSR (Client-Side Rendering) components. Set the revalidate option to 5 minutes for data fetching to provide the latest data to new users requesting the page within that timeframe.
• Considered how to separate and structure UI components during refactoring. Created feature-based components within the app folder and shared components outside of it. In the shared components folder, components were categorized into atoms, molecules, and organisms.
• While borrowing the design theme from Archon V1, I made slight changes to styling, such as the navigation bar, and focused on responsive design.
• Implemented a toaster feature to display messages on the top. Managed adding and removing multiple messages with zustand, allowing one component to manage them. Although it may not be 100% stable, I was able to learn more data structures and React component operations.
• Used Next.js server actions and react-hook-form together for the subscription form and implemented email sending with nodemailer.
• Handled error and loading in the Next.js way.

1. Main Screen

   archon-main2.webm

2. Responsive Design (Tablet, Mobile)

   archon-responsive.webm

3. Newsletter Subscription

   archon-newsletter.webm

4. Topic-Based Article List

   archon-insights.webm

5. Bookmark

   archon-bookmark.webm

6. Random Article Recommendation

   archon-inspirations.webm

7. Author List Pagination

   archon-arthors.webm

8. Link Sharing

   archon-link.webm

• Framework: Next.js
• Styling: TailwindCSS
• Type Checking: zod
• Global State Management: zustand
• Remote State Management: tanstack/react-query
• Etc: react-hook-form, nodemailer

• Same as Archon-cms. GitHub Repository
• Library: Express, Node.js
• Database: MariaDB
• Logging: Pino, Pino-http
• Security: Express-rate-limit, Xss, Helmet, Hpp, Bcrypt, etc.
• API Testing: Postman
• Image Service: Cloudinary

• Source Code: GitHub
• Build Tool: Vite
• Package Management: pnpm
• Etc: VSCode, Eslint, Prettier

• Image Hosting: Cloudinary
• Backend Hosting & Deployment: Oracle Cloud, Docker, Nginx (connected to a personal sub domain)
• Frontend Hosting & Deployment: Oracle Cloud, Docker, Docker Hub, Nginx (connected to a personal sub domain)

• Server components are suffixed with Loader to indicate that the component loads data asynchronously.
• Created basic components such as List and Box (div) for readability.

• A component is a UI piece that includes its own data, logic, and appearance. Components are reusable, can be nested, and can exchange data.
• Considered the following four principles for creating components:
  1. Logical separation of content/layout:
     • Does the component include unrelated content or layout?
  2. Reusability:
     • Can any part of the component be reused?
     • Do you want or need to reuse it?
  3. Responsibility/Complexity:
     • Is the component doing too much?
     • Does the component depend on too many props?
     • Does the component have too much state or effects?
     • Is the code, especially JSX, too complex or confusing?
  4. Coding Style:
     • Do you prefer smaller functions/components?

• Attempted to define and categorize components according to atomic design. Focused on components at the levels of Atoms, Molecules, and Organisms.
  1. Subatomic particles - Tokens of the design system (defined through TailwindCSS)
  2. Atoms - Smallest indivisible units
  3. Molecules - Components with a single function (SRP) such as rows or items
  4. Organisms - Components with multiple functions such as lists or cards
  5. Templates, Pages - Next.js's page.tsx and layout.tsx (thus omitted in this project)

• This project was tough due to the separation between server components and client components in Next.js. Even though I broke down the components, separating them between server and client made the overall structure feel less intuitive because of the deep tree structure. I kept constantly asking "What happens when a server component contains a client component and vice versa?"
• Ultimately, I concluded that Next.js is better suited for projects that requires SEO due to its high complexity. It also made me realize that a solid understanding of React is essential.
• I encountered issues with APIs not working as expected, which required further adjustments. Creating dummy content and debugging the admin site felt like an endless task, so I decided to wrap up the project as it was.
• Without a separate mobile plan in Figma for the Archon project, I think I missed a sense of scale when implementing mobile design. As a result, the hierarchy of text and margin sizes might feel a bit misaligned. After the iterative process of building, checking on mobile, redesigning, and debugging, which was highly inefficient, my belief that design and planning must come first solidified.
• Generated dummy content using ChatGPT 4o and Gemini was extremely useful.

• I want to explore Next.js's image optimization features further.
• I plan to implement skeleton UI for smoother loading.
• I aim to incorporate more mobile or tablet-specific motions for interactions.