SquidSpirit d22f8cc292
All checks were successful
Frontend CI / build (push) Successful in 1m37s
BLOG-140 Label management (list and create) (#144)
### Description

- As the title.

### Package Changes

_No response_

### Screenshots

|Scenario|Screenshot|
|-|-|
|Label list|![截圖 2025-10-15 中午12.00.39.png](/attachments/e27ad38b-86ba-4791-9e33-3fbc1b77f3ad)|
|Create dialog|![截圖 2025-10-15 中午12.02.37.png](/attachments/aa3edda3-b97a-42b7-89dd-67fc9d2fe51e)|
|Input error|![截圖 2025-10-15 中午12.01.30.png](/attachments/daafb0f7-51e1-429d-883d-b1c867e009ad)|
|Name conflict|![截圖 2025-10-15 中午12.06.17.png](/attachments/1b866144-e37a-41ed-9011-f24b89d89368)|

### Reference

Reference #140.

### Checklist

- [x] A milestone is set
- [x] The related issuse has been linked to this branch

Reviewed-on: #144
Co-authored-by: SquidSpirit <squid@squidspirit.com>
Co-committed-by: SquidSpirit <squid@squidspirit.com>
2025-10-15 12:21:41 +08:00

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.

Description
📕 My personal blog
https://squidspirit.com/
Readme 3.6 MiB
Languages
Rust 46.6%
TypeScript 25.7%
Svelte 23.7%
CSS 1.9%
JavaScript 0.9%
Other 1.1%