Develop: update images and add feature game section

CHANGELOG.md

@@ -46,6 +46,12 @@ Created Repo from template
 - Landing Page Redesign
 - CrossWord page update
 
+## [3.4.0] - June 27 2026
+
+- Redesign Pages
+- Added Featured and Category section
+- Added a keyboard game.
+
 ### [Unreleased]
 
 Here we write upgrading notes for brands. It's a team effort to make them as straightforward as possible.

docs/architecture.md

@@ -1,28 +1,27 @@
-# Architecture Principles
-
-## Separation of Concerns
-
-Keep business logic, presentation, and data access separated.
-
-## Single Source of Truth
-
-Avoid duplicating ownership of the same data.
-
-## Predictability
-
-Prefer explicit flows over hidden side effects.
-
-## Backward Compatibility
-
-Consider impact on existing users and integrations before making breaking changes.
-
-## Security First
-
-Validate all external input.
-
-Never trust client-provided data.
-
-## Reuse Existing Patterns
-
-Before introducing a new pattern, evaluate whether an existing project pattern already solves the problem.
-
+# Architecture Principles
+
+## Separation of Concerns
+
+Keep business logic, presentation, and data access separated.
+
+## Single Source of Truth
+
+Avoid duplicating ownership of the same data.
+
+## Predictability
+
+Prefer explicit flows over hidden side effects.
+
+## Backward Compatibility
+
+Consider impact on existing users and integrations before making breaking changes.
+
+## Security First
+
+Validate all external input.
+
+Never trust client-provided data.
+
+## Reuse Existing Patterns
+
+Before introducing a new pattern, evaluate whether an existing project pattern already solves the problem.

docs/coding-guidelines.md

@@ -1,72 +1,72 @@
-# Coding Guidelines
-
-## Naming
-
-- Use meaningful and descriptive names.
-- Avoid abbreviations unless commonly understood.
-- Functions should describe actions.
-- Variables should describe data.
-
-## Functions
-
-- Keep functions focused on a single responsibility.
-- Prefer small, composable functions.
-- Avoid deeply nested conditions.
-- Reuse existing utilities where possible.
-
-## Comments
-
-- Explain why, not what.
-- Remove outdated comments.
-- Avoid commenting obvious code.
-
-## Error Handling
-
-- Handle errors explicitly.
-- Provide actionable error messages.
-- Never silently ignore failures.
-
-## Dependencies
-
-- Introduce new dependencies only when justified.
-- Prefer platform-native solutions when practical.
-
-## Code Reviews
-
-- Optimize for readability.
-- Avoid unnecessary complexity.
-- Follow existing project conventions.
-
-## Development Environment
-
-### Use the Workspace File
-
-Always open the project using the provided VS Code workspace file (`*.code-workspace`).
-
-Benefits:
-
-- Consistent settings
-- Recommended extensions
-- Shared tasks and debugging configuration
-- Reduced environment-related issues
-
-Open the workspace:
-
-```bash
-code project.code-workspace
-```
-
-### Recommended Extensions
-
-Install all workspace-recommended extensions.
-
-These help maintain:
-
-- Formatting consistency
-- Linting standards
-- Import organization
-- Code quality checks
-
-### Workspace Files
-
-Do not commit personal workspace modifications unless they benefit the entire team.
+# Coding Guidelines
+
+## Naming
+
+- Use meaningful and descriptive names.
+- Avoid abbreviations unless commonly understood.
+- Functions should describe actions.
+- Variables should describe data.
+
+## Functions
+
+- Keep functions focused on a single responsibility.
+- Prefer small, composable functions.
+- Avoid deeply nested conditions.
+- Reuse existing utilities where possible.
+
+## Comments
+
+- Explain why, not what.
+- Remove outdated comments.
+- Avoid commenting obvious code.
+
+## Error Handling
+
+- Handle errors explicitly.
+- Provide actionable error messages.
+- Never silently ignore failures.
+
+## Dependencies
+
+- Introduce new dependencies only when justified.
+- Prefer platform-native solutions when practical.
+
+## Code Reviews
+
+- Optimize for readability.
+- Avoid unnecessary complexity.
+- Follow existing project conventions.
+
+## Development Environment
+
+### Use the Workspace File
+
+Always open the project using the provided VS Code workspace file (`*.code-workspace`).
+
+Benefits:
+
+- Consistent settings
+- Recommended extensions
+- Shared tasks and debugging configuration
+- Reduced environment-related issues
+
+Open the workspace:
+
+```bash
+code project.code-workspace
+```
+
+### Recommended Extensions
+
+Install all workspace-recommended extensions.
+
+These help maintain:
+
+- Formatting consistency
+- Linting standards
+- Import organization
+- Code quality checks
+
+### Workspace Files
+
+Do not commit personal workspace modifications unless they benefit the entire team.