SquidSpirit
171410e115
### Description #### Overview This PR improves the website's SEO by: 1. Moving title and meta description tags from app.html to individual page components 2. Adding dynamic meta descriptions based on page content 3. Implementing structured data for blog posts using JSON-LD 4. Optimizing meta descriptions for better search engine visibility #### Changes - **app.html**: Removed static title and meta description tags - **HomePage.svelte**: Added descriptive title parameter to generateTitle function - **Terminal.svelte**: Dynamically generates meta description from terminal lines - **PostContentPage.svelte**: Added meta description and structured data for blog posts - **PostOverallPage.svelte**: Added descriptive meta description for blog listing page - **StructuredData.svelte**: Created new component to generate JSON-LD structured data for blog posts #### Benefits - Improved SEO through better metadata management - Enhanced search engine visibility with structured data - More accurate and dynamic meta descriptions - Better control over page-specific metadata > [!NOTE] > Since sitemap auto generating is a little more complex, it will be solved in #117 in the future. ### Package Changes _No response_ ### Screenshots _No response_ ### Reference Resolves #48 ### Checklist - [x] A milestone is set - [x] The related issuse has been linked to this branch Reviewed-on: #116 Co-authored-by: SquidSpirit <squid@squidspirit.com> Co-committed-by: SquidSpirit <squid@squidspirit.com>
Blog
Development
- Frontend: SvelteKit with Tailwind CSS
- Backend: Rust actix-web
Despite SvelteKit being a full-stack framework, I still decided to adopt a separate front-end and back-end architecture for this blog project. I believe that this separation makes the project cleaner, reduces coupling, and aligns with modern development practices. Furthermore, I wanted to practice developing a purely back-end API.
As for the more detailed development approach, I plan to use Clean Architecture for the overall structure. Of course, such a small project may not necessarily require such complex design patterns, but I want to give myself an opportunity to practice them.
These will allow me to become more proficient in these modern development practices and leave a lot of flexibility and room for adjustments in the future.
For more information about the development process, you can check out the project board. As for the details of the architecture and convention, you can find them in the wiki.
License
This project uses a combination of the MIT License and a custom license. Based on the MIT License, anyone is permitted to use the code. However, before deploying the code, they must first replace any information belonging to "me" or any content that could identify "me," such as logos, names, and "about me" sections.