fix: resolve formatting conflicts between Prettier and markdownlint

- Updated .markdownlint.json to use asterisk style for MD049/MD050 rules
- This aligns with Prettier's formatting of bold text (**text**)
- All formatting and linting checks now pass successfully
- Resolves CI formatting failures in GitHub Actions

Author: Thavarshan

.markdownlint.json

@@ -41,10 +41,10 @@
   },
   "MD047": false,
   "MD049": {
-    "style": "underscore"
+    "style": "asterisk"
   },
   "MD050": {
-    "style": "underscore"
+    "style": "asterisk"
   },
   "MD051": false
 }

DOCS_SYNC_SETUP.md

@@ -6,22 +6,22 @@ This guide will help you set up automatic synchronization between your main repo
 
 The setup creates:
 
-- __Separate docs repository__: `altus4/docs` for documentation only
-- __Automatic sync__: Changes in `docs/` directory trigger sync to docs repo
-- __GitHub Pages__: Auto-deployment of documentation site with Mermaid diagram support
-- __Manual sync__: Script for manual synchronization when needed
+- **Separate docs repository**: `altus4/docs` for documentation only
+- **Automatic sync**: Changes in `docs/` directory trigger sync to docs repo
+- **GitHub Pages**: Auto-deployment of documentation site with Mermaid diagram support
+- **Manual sync**: Script for manual synchronization when needed
 
 ## Prerequisites
 
-1. __GitHub Account__ with permissions to create repositories in the `altus4` organization
-2. __Git configured__ with SSH keys or personal access token
-3. __Repository access__ to both main and docs repositories
+1. **GitHub Account** with permissions to create repositories in the `altus4` organization
+2. **Git configured** with SSH keys or personal access token
+3. **Repository access** to both main and docs repositories
 
 ## Step-by-Step Setup
 
 ### Step 1: Create the Documentation Repository
 
-1. __Create the repository__ on GitHub:
+1. **Create the repository** on GitHub:
 
    ```text
    Repository name: altus4/docs
@@ -30,48 +30,48 @@ The setup creates:
    Initialize: Add a README file
    ```
 
-2. __Enable GitHub Pages__:
-   - Go to repository __Settings__ → __Pages__
-   - Source: __GitHub Actions__
+2. **Enable GitHub Pages**:
+   - Go to repository **Settings** → **Pages**
+   - Source: **GitHub Actions**
    - This allows the workflow to deploy automatically
 
 ### Step 2: Create Personal Access Token
 
-1. __Generate a token__:
-   - Go to GitHub __Settings__ → __Developer settings__ → __Personal access tokens__ → __Tokens (classic)__
-   - Click __Generate new token (classic)__
+1. **Generate a token**:
+   - Go to GitHub **Settings** → **Developer settings** → **Personal access tokens** → **Tokens (classic)**
+   - Click **Generate new token (classic)**
    - Name: `docs-sync-token`
-   - Expiration: __No expiration__ (or set as needed)
+   - Expiration: **No expiration** (or set as needed)
    - Scopes:
      - `repo` (Full control of private repositories)
      - `workflow` (Update GitHub Action workflows)
 
-2. __Copy the token__ - you'll need it in the next step
+2. **Copy the token** - you'll need it in the next step
 
 ### Step 3: Configure Repository Secrets
 
-In your __main repository__ (this one):
+In your **main repository** (this one):
 
-1. Go to __Settings__ → __Secrets and variables__ → __Actions__
-2. Click __New repository secret__
+1. Go to **Settings** → **Secrets and variables** → **Actions**
+2. Click **New repository secret**
 3. Add the following secret:
-   - __Name__: `DOCS_SYNC_TOKEN`
-   - __Value__: The personal access token from Step 2
+   - **Name**: `DOCS_SYNC_TOKEN`
+   - **Value**: The personal access token from Step 2
 
 ### Step 4: Test the Setup
 
-1. __Make a change__ to any file in the `docs/` directory
-2. __Commit and push__ to the `main` or `develop` branch:
+1. **Make a change** to any file in the `docs/` directory
+2. **Commit and push** to the `main` or `develop` branch:
 
    ```bash
    git add docs/
    git commit -m "docs: test sync setup"
    git push origin main
    ```
 
-3. __Check the Actions tab__ in your main repository to see the sync workflow running
-4. __Verify the docs repository__ receives the changes
-5. __Check GitHub Pages__ deployment (may take a few minutes)
+3. **Check the Actions tab** in your main repository to see the sync workflow running
+4. **Verify the docs repository** receives the changes
+5. **Check GitHub Pages** deployment (may take a few minutes)
 
 ## Manual Sync Options
 
@@ -97,9 +97,9 @@ npm run docs:sync:force
 
 ### Using GitHub Actions (Manual Trigger)
 
-1. Go to __Actions__ tab in your main repository
-2. Select __Sync Documentation__ workflow
-3. Click __Run workflow__
+1. Go to **Actions** tab in your main repository
+2. Select **Sync Documentation** workflow
+3. Click **Run workflow**
 4. Choose branch and optionally force sync
 
 ## Repository Structure
@@ -168,17 +168,17 @@ on:
 
 ### Common Issues
 
-1. __Permission Denied__
+1. **Permission Denied**
    - Check that `DOCS_SYNC_TOKEN` secret is set correctly
    - Verify token has `repo` and `workflow` permissions
    - Ensure token hasn't expired
 
-2. __Repository Not Found__
+2. **Repository Not Found**
    - Verify `altus4/docs` repository exists
    - Check repository name in script matches exactly
    - Ensure you have access to the docs repository
 
-3. __Sync Script Fails__
+3. **Sync Script Fails**
    - Run script manually to see detailed error messages:
 
      ```bash
@@ -187,7 +187,7 @@ on:
 
    - Check git configuration and credentials
 
-4. __GitHub Pages Not Deploying__
+4. **GitHub Pages Not Deploying**
    - Verify GitHub Pages is enabled in docs repository settings
    - Check that Pages source is set to "GitHub Actions"
    - Review the deploy workflow in the docs repository
@@ -211,27 +211,27 @@ bash -x scripts/sync-docs.sh
 
 When everything is working correctly:
 
-1. __Automatic Sync__: Changes to `docs/` trigger the sync workflow
-2. __Docs Repository__: Updated within minutes of main repo changes
-3. __GitHub Pages__: Documentation site updates automatically
-4. __Manual Sync__: `npm run docs:sync` works without errors
+1. **Automatic Sync**: Changes to `docs/` trigger the sync workflow
+2. **Docs Repository**: Updated within minutes of main repo changes
+3. **GitHub Pages**: Documentation site updates automatically
+4. **Manual Sync**: `npm run docs:sync` works without errors
 
 ## Next Steps
 
 After setup is complete:
 
-1. __Bookmark the docs site__: `https://altus4.github.io/docs`
-2. __Update README__: Add link to documentation site
-3. __Team notification__: Inform team about the new documentation workflow
-4. __Monitor__: Check sync status after first few documentation changes
+1. **Bookmark the docs site**: `https://altus4.github.io/docs`
+2. **Update README**: Add link to documentation site
+3. **Team notification**: Inform team about the new documentation workflow
+4. **Monitor**: Check sync status after first few documentation changes
 
 ## Useful Links
 
-- __Documentation Site__: <https://altus4.github.io/docs>
-- __Docs Repository__: <https://github.com/altus4/docs>
-- __VitePress Documentation__: <https://vitepress.dev/>
-- __GitHub Actions Documentation__: <https://docs.github.com/en/actions>
+- **Documentation Site**: <https://altus4.github.io/docs>
+- **Docs Repository**: <https://github.com/altus4/docs>
+- **VitePress Documentation**: <https://vitepress.dev/>
+- **GitHub Actions Documentation**: <https://docs.github.com/en/actions>
 
 ---
 
-__Need help?__ Check the troubleshooting section above or create an issue in the main repository.
+**Need help?** Check the troubleshooting section above or create an issue in the main repository.

README.md

@@ -4,31 +4,31 @@ A modern, responsive marketing website for Altus 4 - an AI-enhanced MySQL full-t
 
 ## Features
 
-- __Modern Design__: Clean, professional design with gradient backgrounds and smooth animations
-- __Responsive__: Mobile-first design that works on all devices
-- __Performance Optimized__: Fast loading with optimized assets and smooth scrolling
-- __SEO Friendly__: Comprehensive meta tags and semantic HTML structure
-- __Accessible__: Built with accessibility best practices
-- __Documentation__: Integrated VitePress documentation with automatic sync to separate repository
+- **Modern Design**: Clean, professional design with gradient backgrounds and smooth animations
+- **Responsive**: Mobile-first design that works on all devices
+- **Performance Optimized**: Fast loading with optimized assets and smooth scrolling
+- **SEO Friendly**: Comprehensive meta tags and semantic HTML structure
+- **Accessible**: Built with accessibility best practices
+- **Documentation**: Integrated VitePress documentation with automatic sync to separate repository
 
 ## Tech Stack
 
-- __Framework__: Vue.js 3 (Composition API)
-- __Language__: TypeScript
-- __Styling__: Tailwind CSS
-- __Components__: Custom UI components inspired by Shadcn-Vue
-- __Icons__: Lucide Vue Next
-- __Build Tool__: Vite
-- __Documentation__: VitePress
+- **Framework**: Vue.js 3 (Composition API)
+- **Language**: TypeScript
+- **Styling**: Tailwind CSS
+- **Components**: Custom UI components inspired by Shadcn-Vue
+- **Icons**: Lucide Vue Next
+- **Build Tool**: Vite
+- **Documentation**: VitePress
 
 ## Sections
 
-1. __Hero Section__: Value proposition with clear CTA buttons
-1. __Features Section__: Showcase of key capabilities (AI, Performance, Security)
-1. __Technical Specifications__: Architecture overview and tech stack details
-1. __Project Status__: Current metrics, completion status, and roadmap
-1. __Call to Action__: Community engagement and quick start links
-1. __Footer__: Contact information, resources, and tech stack
+1. **Hero Section**: Value proposition with clear CTA buttons
+1. **Features Section**: Showcase of key capabilities (AI, Performance, Security)
+1. **Technical Specifications**: Architecture overview and tech stack details
+1. **Project Status**: Current metrics, completion status, and roadmap
+1. **Call to Action**: Community engagement and quick start links
+1. **Footer**: Contact information, resources, and tech stack
 
 ## Quick Start
 
@@ -80,8 +80,8 @@ npm run preview
 
 The website uses a custom color palette defined in `tailwind.config.js`. Main colors:
 
-- __Primary__: Blue (#3b82f6) for buttons and accents
-- __Secondary__: Gray scale for text and backgrounds
+- **Primary**: Blue (#3b82f6) for buttons and accents
+- **Secondary**: Gray scale for text and backgrounds
 
 ### Components
 
@@ -95,12 +95,12 @@ All UI components are located in `src/components/ui/` and can be easily customiz
 
 To update the content:
 
-1. __Hero Section__: Edit `src/components/HeroSection.vue`
-2. __Features__: Modify `src/components/FeaturesSection.vue`
-3. __Tech Specs__: Update `src/components/TechSpecsSection.vue`
-4. __Project Status__: Change metrics in `src/components/ProjectStatusSection.vue`
-5. __CTA__: Customize links in `src/components/CallToActionSection.vue`
-6. __Footer__: Update contact info in `src/components/FooterSection.vue`
+1. **Hero Section**: Edit `src/components/HeroSection.vue`
+2. **Features**: Modify `src/components/FeaturesSection.vue`
+3. **Tech Specs**: Update `src/components/TechSpecsSection.vue`
+4. **Project Status**: Change metrics in `src/components/ProjectStatusSection.vue`
+5. **CTA**: Customize links in `src/components/CallToActionSection.vue`
+6. **Footer**: Update contact info in `src/components/FooterSection.vue`
 
 ## Documentation
 
@@ -114,9 +114,9 @@ Live Documentation: [https://altus4.github.io/docs](https://altus4.github.io/doc
 
 The `docs/` directory is automatically synchronized to the [`altus4/docs`](https://github.com/altus4/docs) repository:
 
-- __Automatic__: Triggered on push to `main` or `develop` branches
-- __Manual__: Use `npm run docs:sync` for manual synchronization
-- __GitHub Pages__: Auto-deployment to documentation site
+- **Automatic**: Triggered on push to `main` or `develop` branches
+- **Manual**: Use `npm run docs:sync` for manual synchronization
+- **GitHub Pages**: Auto-deployment to documentation site
 
 ### Working with Documentation
 
@@ -166,9 +166,9 @@ Tailwind is configured in `tailwind.config.js` with:
 
 ## Performance
 
-- __Lighthouse Score__: 90+ (Performance, Accessibility, Best Practices, SEO)
-- __Bundle Size__: Optimized with Vite's tree shaking
-- __Loading Speed__: Lazy loading and optimized images
+- **Lighthouse Score**: 90+ (Performance, Accessibility, Best Practices, SEO)
+- **Bundle Size**: Optimized with Vite's tree shaking
+- **Loading Speed**: Lazy loading and optimized images
 
 ## Deployment
 
@@ -196,7 +196,7 @@ This project is licensed under the MIT License.
 
 ## Author
 
-Thavarshan
+Jerome (Thavarshan) Thayananthajothy
 
 - Website: [thavarshan.com](https://thavarshan.com)
 - GitHub: [@thavarshan](https://github.com/thavarshan)
@@ -207,4 +207,4 @@ Contributions, issues, and feature requests are welcome! Feel free to check the
 
 ---
 
-Made with care for the Altus 4 project
+Made with ❤️ for the Altus 4 project by Jerome Thayananthajothy