fix: Remove outdated aliases from the document to simplify the content

Author: TBXark

content/docs/concepts/architecture-and-repo.md

@@ -1,9 +1,6 @@
 ---
 title: Architecture & Repository Strategy
 weight: 25
-aliases:
-  - /docs/concepts/microservice-architecture/
-  - /docs/concepts/code-repository-types/
 ---
 
 Start monolith-first with clean boundaries, then split when needed. Use a single Go module with Makefile-driven code generation to keep contracts and runtime consistent.

content/docs/concepts/project-structure.md

@@ -1,9 +1,6 @@
 ---
 title: Project Structure
 weight: 21
-aliases:
-  - /docs/concepts/project-code-structure/
-  - /docs/concepts/project-layout/
 ---
 
 Sphere follows a pragmatic project structure that keeps code generation, server code, and business logic cleanly separated while staying fast to iterate on. The structure is based on the [sphere-layout](https://github.com/go-sphere/sphere-layout) template and follows Go community best practices.

content/docs/concepts/protocol-and-codegen.md

@@ -1,9 +1,6 @@
 ---
 title: Protocol & Codegen
 weight: 23
-aliases:
-  - /docs/concepts/protobuf-protocol/
-  - /docs/concepts/code-generation-engine/
 ---
 
 Sphere follows a "protocol-first" approach where you define your APIs once in Protobuf and generate everything else from those definitions. This ensures consistency across your entire stack and reduces boilerplate code.

content/docs/getting-started/_index.md

@@ -1,8 +1,6 @@
 ---
 title: Getting Started
 weight: 10
-aliases:
-  - /docs/start/
 ---
 
 Kick off your first Sphere project.

content/docs/getting-started/quickstart.md

@@ -1,12 +1,6 @@
 ---
 title: Quick Start
 weight: 11
-aliases:
-  - /docs/start/getting-started/
-  - /docs/start/getting-started
-  - /docs/getting-started/quickstart
-  - /docs/getting-started/introduction
-  - /docs/getting-started/creating-your-first-project
 ---
 
 Sphere is a pragmatic Go backend toolkit centered on a clean monolithic template and a small toolchain that automates schema, API contracts, server stubs, Swagger, and even TypeScript clients.

content/docs/getting-started/workflow.md

@@ -1,9 +1,6 @@
 ---
 title: Development Workflow
 weight: 12
-aliases:
-  - /docs/start/workflow/
-  - /docs/start/workflow
 ---
 
 A typical day-to-day development cycle with Sphere follows this pattern:

content/docs/guides/logging.md

@@ -65,7 +65,7 @@ func main() {
 To add structured context to your logs, you can use `log.With` to create a new logger instance with predefined fields.
 
 ```go
-logger := log.With(log.String("service", "UserService"), log.String("traceId", "xyz-123"))
+logger := log.With(log.WithAttrs(map[string]any{"module": "api"}))
 
 logger.Info("User lookup successful")
 // Output will include {"service": "UserService", "traceId": "xyz-123", "message": "User lookup successful"}
@@ -104,8 +104,10 @@ Use structured logging in your HTTP handlers to track requests:
 ```go
 func (s *UserService) CreateUser(c *gin.Context) {
     logger := log.With(
-        log.String("handler", "CreateUser"),
-        log.String("requestId", c.GetHeader("X-Request-ID")),
+        log.WithAttrs(map[string]any{
+            "service": "UserService",
+            "traceId": c.GetString("traceId"), // assuming traceId is set in context
+        })
     )
 
     logger.Info("Creating user request received")
@@ -140,7 +142,12 @@ Add contextual logging to your business logic:
 
 ```go
 func (b *UserBiz) CreateUser(ctx context.Context, req *CreateUserRequest) (*User, error) {
-    logger := log.With(log.String("method", "CreateUser"))
+    logger := log.With(
+        log.WithAttrs(map[string]any{
+            "module": "business",
+            "function": "CreateUser",
+        }),
+    )
 
     logger.Debug("Validating user input", log.String("email", req.Email))
 
@@ -355,12 +362,12 @@ Always include relevant context in your logs:
 
 ```go
 func (s *Service) ProcessOrder(ctx context.Context, orderID string) error {
-    logger := log.With(
-        log.String("orderID", orderID),
-        log.String("userID", getUserIDFromContext(ctx)),
-    )
 
-    logger.Info("Processing order")
+    logger.Info("Processing order", 
+        log.String("orderId", orderID),
+        log.String("userId", getUserIDFromContext(ctx))
+        log.String("traceId", getTraceIDFromContext(ctx))
+    )
     // ... processing logic
 }
 ```