SquidSpirit e3cc981344
All checks were successful
Frontend CI / build (push) Successful in 1m3s
BLOG-241 Remove unused SearchBar component and refine FilteringDialog styling (#249)
### Description

#### Description/Summary

This pull request streamlines our frontend UI architecture by removing the deprecated `SearchBar.svelte` component, pointing toward a consolidation of search input handling. To maintain a consistent and polished user experience, the keyword input within `FilteringDialog.svelte` has been updated with refined padding and placeholder typography. Additionally, a root `.gitignore` file has been initialized to establish standard exclusions for environment configurations and OS-specific artifacts, preventing accidental commits of sensitive or unnecessary files.

#### Key Changes

* **`.gitignore`:** Added root ignore file to exclude `.env` configurations and macOS `.DS_Store` artifacts from version control.
* **`FilteringDialog.svelte`:** Enhanced the `Input` component by injecting utility classes (`px-4 py-2 text-sm placeholder:text-gray-500`) for improved spatial alignment, sizing, and placeholder legibility.
* **`SearchBar.svelte`:** Deleted the component entirely, including its localized debounce logic, state management, and DOM elements, to reduce technical debt and component duplication.

### Package Changes

_No response_

### Screenshots

![截圖 2026-03-11 14.55.28.png](/attachments/7524c9fc-d082-417d-9b64-93fc46fc8752)

### Reference

Resolves #241.

### Checklist

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

Reviewed-on: #249
Co-authored-by: SquidSpirit <squid@squidspirit.com>
Co-committed-by: SquidSpirit <squid@squidspirit.com>
2026-03-11 14:58:57 +08:00
2025-10-15 13:11:25 +08:00

Blog

Description

  • 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.

Build & Development Setup

Prerequisites

  • Node.js (LTS version recommended)
  • pnpm - Package manager for frontend
  • Rust - For backend development
  • Podman (Optional) - For containerized deployment

Pre-commit Setup

This project uses pre-commit hooks to ensure code quality. To set up pre-commit:

  1. Install pre-commit:

    pip install pre-commit
    
  2. Install the git hook scripts:

    pre-commit install
    

The pre-commit configuration will automatically run:

  • Backend Rust code checking and formatting
  • Frontend linting and formatting
  • SQL schema preparation

Backend Setup

For detailed backend development setup, see backend/README.md.

Quick start:

  1. Install sqlx CLI: cargo install sqlx-cli
  2. Run database migrations: sqlx migrate run
  3. Prepare SQL schema: cargo sqlx prepare --workspace
  4. Run the server: RUST_LOG=debug cargo run

Frontend Setup

For detailed frontend development setup, see frontend/README.md.

Quick start:

  1. Navigate to frontend directory: cd frontend
  2. Install dependencies: pnpm install
  3. Start development server: pnpm dev
  4. Build for production: pnpm build

Full Project Setup

To set up the entire project:

  1. Clone the repository
  2. Set up pre-commit hooks (see above)
  3. Set up backend (see backend/README.md)
  4. Set up frontend (see frontend/README.md)
  5. Start both servers for full-stack development

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 5.4 MiB
v0.6.2 Latest
2026-01-31 22:40:09 +08:00
Languages
Rust 36.2%
Svelte 34.1%
TypeScript 24.2%
Python 2.4%
CSS 1.4%
Other 1.7%