fix: cyrillic fonts, dev certs, page head, and ru-text typography (#67)
🤖 PR generated for branch `fix/cyrillic-fonts-dev-certs-and-page-head`.
### Changes Summary
- **Fonts**: Add Cyrillic glyph subsets for Lato, EB Garamond, and Fira
Code.
- **Dev**: Support remote Root CA and encrypted dev CA key in
`.env.dev`.
- **UI & Kits**: Add size variant to `Breadcrumbs` component and enlarge
`PageHead` breadcrumbs with tuned collapse scroll threshold.
- **ESLint**: Add `no-hanging-particles` i18n & markdown typography rule
with auto-fixer.
- **Content & i18n**: Apply `ru-text` editorial and typography polish
(em dashes, number ranges, «ё» restoration, non-breaking spaces) across
`services/www` and `services/docs`.
This commit is contained in:
1 parent
c6487dc258
commit
b3638f4d63
111 files changed
+2350
-1512
No files matched your search
@@ -3,38 +3,38 @@ title: Architecture & Philosophy
|
||||
weight: 1
|
||||
---
|
||||
|
||||
**Goal:** Understand the core design principles that drive Quetza's modularity.
|
||||
**Goal:** Understand the core design principles that drive Quetza's modularity.
|
||||
|
||||
## Design Philosophies
|
||||
|
||||
### Convention Over Configuration
|
||||
|
||||
Quetza minimizes boilerplate by relying on strict folder structures.
|
||||
Quetza minimizes boilerplate by relying on strict folder structures.
|
||||
|
||||
- **No central registry:** The filesystem _is_ the registry.
|
||||
- **Result:** You don't update a config file to add a module; you just create the folder.
|
||||
- **No central registry:** The filesystem _is_ the registry.
|
||||
- **Result:** You don't update a config file to add a module; you just create the folder.
|
||||
|
||||
### Composition Over Inheritance
|
||||
|
||||
Modules are composed of capabilities, not inherited from a base class.
|
||||
Modules are composed of capabilities, not inherited from a base class.
|
||||
|
||||
- **Flexibility:** Modules can use any internal architecture (Functional, OOP) as long as they export the required interfaces.
|
||||
- **Flexibility:** Modules can use any internal architecture (Functional, OOP) as long as they export the required interfaces.
|
||||
|
||||
### Isolation Over Integration
|
||||
|
||||
Modules cannot directly invoke each other.
|
||||
|
||||
- **Why:** Prevents tight coupling.
|
||||
- **Benefit:** You can delete any module without breaking the rest of the bot.
|
||||
- **Benefit:** You can delete any module without breaking the rest of the bot.
|
||||
|
||||
## Core Entities
|
||||
|
||||
| Entity | Role | Lifecycle |
|
||||
| :------------- | :----------------------------- | :---------------------------- |
|
||||
| **Client** | Service Locator & Orchestrator | Singleton. Runs the show. |
|
||||
| **Module** | Namespace for features | Loaded at startup. |
|
||||
| **Client** | Service Locator & Orchestrator | Singleton. Runs the show. |
|
||||
| **Module** | Namespace for features | Loaded at startup. |
|
||||
| **Command** | User Interaction Endpoint | Stateless. Request/Response. |
|
||||
| **Event** | Reactive Observer | Subscribed at startup. |
|
||||
| **Event** | Reactive Observer | Subscribed at startup. |
|
||||
| **Controller** | State Manager | Persists across interactions. |
|
||||
|
||||
---
|
||||
|
||||
Reference in new issue
Block a user