Feature/CDP-162-LandingLayout

[leeunduck]

🚀 Pull Request

📝 PR 유형

• 기능 추가 (Feature)
• 버그 수정 (Bug Fix)
• 코드 개선 (Refactoring)
• 문서 작업 (Docs)
• 환경 설정 (Configuration)
• 최종 점검 (Release Check)

---

🔍 변경 사항

header와 footer 컴포넌트를 생성하고 layout에 넣었음

---

📸 스크린샷

---

🚧 관련 이슈

---

🛠️ 최종 배포 점검 리스트

• 주요 기능 동작 확인
• 빌드/배포 환경 점검
• 문서/설정 검토

---

✅ 최종 배포 점검 결과

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
custom-daily-planner	Ready	Preview	Comment	Nov 3, 2025 2:41pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Fix logo path casing in navbar

The new logo asset was added as public/images/Logo.png (capital L) but the navbar still references src="/images/logo.png". On case-sensitive deployments (Linux builds and Vercel), this mismatch will return a 404 so the brand logo will not render in the header. Update the reference to match the file’s casing or rename the asset to keep the path consistent.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Fix logo path casing in footer

The footer renders the same logo using src="/images/logo.png", but the only image committed is public/images/Logo.png. Because Next.js serves files case-sensitively in production, the footer’s logo will fail to load and display as a broken image. Align the string casing or rename the asset so the served file matches the requested path.

Useful? React with 👍 / 👎.