8000 GitHub - No898/letmecook.cz: 🍳 Personal recipe diary & tech playground. Experimenting with Next.js, TypeScript, Tailwind, i18n, performance & accessibility.
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

🍳 Personal recipe diary & tech playground. Experimenting with Next.js, TypeScript, Tailwind, i18n, performance & accessibility.

License

Notifications You must be signed in to change notification settings

No898/letmecook.cz

Repository files navigation

Let Me Cook - Personal Recipe Diary & Tech Playground

A personal online recipe diary showcasing a collection of favorite recipes. This project serves a dual purpose: acting as a small, personal cookbook and as a playground for experimenting with new web technologies, libraries, and performance optimization techniques.

Live Site: letmecook.cz

About The Project

This application is primarily a digital space to document and share recipes I love to cook. It's designed to be a clean, user-friendly, and accessible interface for my personal collection.

Simultaneously, it functions as my personal tech playground. I use this project to test and implement new frontend libraries, explore different approaches to building web applications with Next.js, and continuously focus on optimizing performance and adhering to best practices.

Key Technologies

Core Features

  • Multi-language Support: Interface and recipes available in Czech, English, Vietnamese, and Traditional Chinese.
  • Accessibility (A11y): Continuous focus on accessibility, incorporating skip links, semantic HTML, ARIA attributes, and color contrast considerations.
  • Performance Optimization: Attention to performance metrics using tools like Vercel Analytics and Speed Insights.
  • Static Data Approach: Recipes are stored directly within the codebase (src/data/recipes/) as structured TypeScript objects.

Design Decision: Data Management

Given the project's primary function as a personal cookbook with a limited, stable set of recipes, and its secondary function as a tech playground, storing recipes directly in the codebase ("hardcoded") was the most practical choice. It avoids the overhead of setting up and maintaining a CMS or database, allowing focus to remain on frontend experimentation and implementation details, while still providing a functional way to handle recipe data for the application's scope.

Performance: Performance is actively monitored. You can check the current status using Google PageSpeed Insights.

Licensing

The source code of this application is licensed under the MIT License (see the LICENSE file).

The content, including recipe texts and images within the src/data/recipes/ and public/images/ directories, is Copyright (c) 2025 Tomáš Dinh - All Rights Reserved. You may not reproduce, distribute, or modify the content without explicit permission from the copyright holder.

About

🍳 Personal recipe diary & tech playground. Experimenting with Next.js, TypeScript, Tailwind, i18n, performance & accessibility.

Resources

License

Stars

Watchers

Forks

0