From 71b5d43e89cf1a5bdaae1292a0f7f64e4d0b6102 Mon Sep 17 00:00:00 2001 From: kbe Date: Sat, 23 Aug 2025 20:43:41 +0200 Subject: [PATCH] Add old theme rules --- docs/branch-naming.txt | 142 ---------------------------------------- docs/theme-rules.md.old | 103 +++++++++++++++++++++++++++++ 2 files changed, 103 insertions(+), 142 deletions(-) delete mode 100644 docs/branch-naming.txt create mode 100644 docs/theme-rules.md.old diff --git a/docs/branch-naming.txt b/docs/branch-naming.txt deleted file mode 100644 index c8e1367..0000000 --- a/docs/branch-naming.txt +++ /dev/null @@ -1,142 +0,0 @@ -Cette conversation a été générée avec Duck.ai (https://duck.ai) à l'aide du modèle Mistral Small 3 d'Mistral AI. Les chats IA peuvent afficher des informations inexactes ou offensantes (voir https://duckduckgo.com/duckai/privacy-terms pour en savoir plus). - -==================== - -Message 1 sur 2 de l'utilisateur - 16/08/2025, 08:06:58: -In a git Ruby on Rails web project, how to name branches? - -Mistral Small 3: -Naming branches in a Git Ruby on Rails web project (or any Git project) is an important aspect of maintaining a clean and understandable repository. Here are some best practices for naming branches: - -1. **Use Descriptive Names**: The branch name should clearly describe the purpose or the feature being worked on. This helps other developers understand the context of the branch at a glance. - -2. **Use Hyphens or Underscores**: Use hyphens (`-`) or underscores (`_`) to separate words in the branch name. This makes the name more readable. - -3. **Prefix with the Type of Change**: Prefix the branch name with a type indicator such as `feature`, `bugfix`, `hotfix`, `release`, `chore`, `refactor`, `docs`, etc. This helps in categorizing the branches. - -4. **Keep It Short but Meaningful**: While being descriptive, try to keep the branch name short to avoid clutter. - -5. **Avoid Special Characters**: Stick to alphanumeric characters and hyphens/underscores. Avoid using special characters like `@`, `#`, `$`, etc. - -6. **Use Lowercase Letters**: Consistently use lowercase letters to avoid case sensitivity issues. - -Here are some examples of well-named branches: - -- `feature/user-authentication` -- `bugfix/login-issue` -- `hotfix/critical-bug` -- `release/v1.2.0` -- `chore/update-dependencies` -- `refactor/user-model` -- `docs/update-readme` - -### Example Workflow - -1. **Creating a New Feature Branch**: - ```sh - git checkout -b feature/user-authentication - ``` - -2. **Creating a Bugfix Branch**: - ```sh - git checkout -b bugfix/login-issue - ``` - -3. **Creating a Hotfix Branch**: - ```sh - git checkout -b hotfix/critical-bug - ``` - -4. **Creating a Release Branch**: - ```sh - git checkout -b release/v1.2.0 - ``` - -5. **Creating a Chore Branch**: - ```sh - git checkout -b chore/update-dependencies - ``` - -6. **Creating a Refactor Branch**: - ```sh - git checkout -b refactor/user-model - ``` - -7. **Creating a Docs Branch**: - ```sh - git checkout -b docs/update-readme - ``` - -By following these guidelines, you can maintain a well-organized and understandable branch structure in your Git repository, making collaboration and code management much easier. - --------------------- - -Message 2 sur 2 de l'utilisateur - 16/08/2025, 08:08:31: -Is it a good practice to use main, develop and functionnal names for branches? - -Mistral Small 3: -Using `main`, `develop`, and feature branches is a common and widely accepted practice in Git workflows, particularly in the context of the Git Flow or GitHub Flow methodologies. Here's a breakdown of these branches and why they are useful: - -1. **`main` Branch**: - - **Purpose**: The `main` branch (or sometimes called `master`) is the stable branch that always contains the production-ready code. It represents the current state of the project that is deployed to production. - - **Usage**: This branch should only contain code that has been thoroughly tested and is ready for release. It is typically protected to prevent direct commits and requires pull requests for changes. - - **Example**: `git checkout main` - -2. **`develop` Branch**: - - **Purpose**: The `develop` branch is used for integrating features and preparing for the next release. It serves as a staging area for features that are in progress but not yet ready for production. - - **Usage**: Developers merge their feature branches into `develop` for integration testing. This branch can be less stable than `main` but should still be in a reasonably good state. - - **Example**: `git checkout develop` - -3. **Feature Branches**: - - **Purpose**: Feature branches are used to develop new features, bug fixes, or any other isolated work. Each feature branch is created from `develop` and merged back into `develop` once the work is complete. - - **Usage**: These branches allow for parallel development without interfering with the stability of `develop` or `main`. They are typically named descriptively, as discussed earlier (e.g., `feature/user-authentication`, `bugfix/login-issue`). - - **Example**: `git checkout -b feature/user-authentication` - -### Example Workflow - -1. **Create a Feature Branch**: - ```sh - git checkout develop - git pull origin develop - git checkout -b feature/user-authentication - ``` - -2. **Develop the Feature**: - - Make changes, commit them, and push the branch to the remote repository. - ```sh - git add . - git commit -m "Add user authentication feature" - git push origin feature/user-authentication - ``` - -3. **Merge the Feature Branch into `develop`**: - - Once the feature is complete and tested, create a pull request to merge it into `develop`. - ```sh - git checkout develop - git pull origin develop - git merge feature/user-authentication - git push origin develop - ``` - -4. **Prepare for Release**: - - When preparing for a new release, create a release branch from `develop`. - ```sh - git checkout -b release/v1.2.0 - ``` - -5. **Merge Release Branch into `main`**: - - After testing the release branch, merge it into `main` and tag the release. - ```sh - git checkout main - git merge release/v1.2.0 - git tag -a v1.2.0 -m "Release version 1.2.0" - git push origin main --tags - ``` - -### Benefits - -- **Stability**: The `main` branch remains stable and always contains production-ready code. -- **Integration**: The `develop` branch allows for continuous integration of features, making it easier to test and integrate new work. -- **Isolation**: Feature branches isolate work, allowing multiple developers to work on different features simultaneously without conflicts. - -Using `main`, `develop`, and feature branches is a good practice as it helps maintain a clean, organized, and manageable repository, facilitating better collaboration and code management. \ No newline at end of file diff --git a/docs/theme-rules.md.old b/docs/theme-rules.md.old new file mode 100644 index 0000000..4274d4b --- /dev/null +++ b/docs/theme-rules.md.old @@ -0,0 +1,103 @@ +# Theme Rules & Color Palette - Aperonight + +Extracted from `app/views/pages/home.html.erb` + +## Color Palette + +### Primary Colors +- **Indigo**: `#4338ca` (rgb(67, 56, 202)) - Used in hero gradient +- **Purple**: `#8b5cf6` (rgb(139, 92, 246)) - Primary brand color +- **Pink**: `#ec4899` (rgb(236, 72, 153)) - Accent color + +### Background Gradients +- **Hero**: `bg-gradient-to-br from-indigo-900 via-purple-800 to-pink-700` +- **CTA**: `bg-gradient-to-r from-purple-900 via-indigo-900 to-pink-900` +- **Cards**: `bg-gradient-to-br from-gray-800 to-gray-900` +- **Buttons**: `bg-gradient-to-r from-purple-600 to-pink-600` + +### Text Colors +- **White**: `text-white` - Primary text +- **Gray-200**: `text-gray-200` - Secondary text +- **Gray-300**: `text-gray-300` - Subtle text +- **Gray-400**: `text-gray-400` - Muted text +- **Transparent gradient**: `text-transparent bg-clip-text bg-gradient-to-r from-purple-400 to-pink-400` - Special highlight + +### Background Colors +- **Gray-900**: `bg-gray-900` - Main background +- **Black**: `bg-black` - Overlay backgrounds +- **Gray-800**: `bg-gray-800` - Card backgrounds +- **White/Transparent**: `bg-white bg-opacity-10 backdrop-blur-sm` - Glass effect + +## Spacing & Layout + +### Hero Section +- **Height**: `min-h-[70vh]` +- **Max-width**: `max-w-7xl mx-auto` +- **Padding**: `px-4 sm:px-6 lg:px-8` + +### Grid Layouts +- **Responsive**: `grid-cols-1 md:grid-cols-2 lg:grid-cols-3` +- **Gap**: `gap-8` standard spacing + +### Padding Classes +- **Section**: `py-16`, `py-20` +- **Card**: `p-4`, `p-6`, `p-8` +- **Button**: `py-3`, `py-4`, `px-6`, `px-8` + +## Typography + +### Font Sizes +- **Hero Title**: `text-5xl md:text-7xl` +- **Section Title**: `text-4xl` +- **Card Title**: `text-2xl` +- **Body**: `text-xl`, `text-lg` +- **Small**: `text-sm` + +### Font Weights +- **Bold**: `font-bold` (headings) +- **Semibold**: `font-semibold` (buttons, important text) +- **Medium**: `font-medium` (labels) + +## Interactive States + +### Hover Effects +- **Scale**: `hover:scale-105` +- **Transition**: `transition-all duration-300` +- **Button Hover**: `hover:from-purple-700 hover:to-pink-700` +- **Glass Hover**: `hover:bg-opacity-20` + +### Shadows +- **Default**: `shadow-lg` +- **Strong**: `shadow-xl` +- **Card**: `shadow-2xl` + +## Border Radius +- **Buttons**: `rounded-full` (pill-shaped) +- **Cards**: `rounded-2xl` +- **Inputs**: `rounded-lg` + +## Icon Colors +- **Primary**: `text-white` (on colored backgrounds) +- **Accent**: `text-purple-400`, `text-pink-400` +- **Muted**: `text-gray-400` + +## Usage Examples + +### Primary Button +```html +class="bg-gradient-to-r from-purple-600 to-pink-600 hover:from-purple-700 hover:to-pink-700 text-white font-semibold py-4 px-8 rounded-full transition-all duration-300 transform hover:scale-105 shadow-lg" +``` + +### Card Background +```html +class="bg-gradient-to-br from-gray-800 to-gray-900 rounded-2xl overflow-hidden hover:transform hover:scale-105 transition-all duration-300 shadow-xl" +``` + +### Hero Gradient +```html +class="bg-gradient-to-br from-indigo-900 via-purple-800 to-pink-700" +``` + +### Glass Effect +```html +class="bg-white bg-opacity-10 backdrop-blur-sm border border-white border-opacity-30" \ No newline at end of file