Merge branch 'main' into fix/accessibility-navbar

Author: sanjay-kv

.github/workflows/lint.yml

@@ -9,5 +9,5 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: 20
-      - run: npm ci || npm install
+      - run: npm ci --legacy-peer-deps || npm install --legacy-peer-deps
       - run: npm run lint

.npmrc

@@ -0,0 +1 @@
+legacy-peer-deps=true

blog/authors.yml

@@ -31,7 +31,8 @@ Aditya-Singh-Rathore:
   email: rathoreadityasingh30@gmail.com
   page: true # Turns the feature on
   description: >
-    I'm a Self Learned Fabric Certified Data Engineer & an Open Source Contributor 🏆
+    Aditya is a self-taught, Fabric-certified Data Engineer, GSSoC winner, author, and open-source enthusiast passionate about building scalable data solutions, contributing to the community, and sharing knowledge through blogs and public learning.
+
 
   socials:
     linkedin: aditya-singh-rathore0017

docs/assets/blog-01-new-issue.png

@@ -17,47 +17,51 @@ This guide walks you through everything you need to write and publish a blog pos
 :::
 ---
 
-## Step 1: Raise a New issue 
-
-Head to the the GitHub issue on this [repository](https://github.com/recodehive/recode-website/issues)
-     <BrowserWindow url="https://github.com/recodehive/recode-website/issues" bodyStyle={{padding: 0}}>    
-     [![Github](assets\blog-01-new-issue.png)](https://github.com/recodehive/recode-website/issues)
+## Step 1: Raise a New issue on GitHub
+
+Head to the the GitHub issue on this [repository](https://github.com/recodehive/recode-website/issues), raise an new issue under documentation update. 
+    :::info
+    * Few things to remember, don't raise random generic topics.
+    * Write from real experience, try to include real dashboard pictures, no copy paste articles.
+    * You can generate AI pictures, but need to be edited any tools like Canva.
+    * Your article must teach something offical documentation doesnot. Means no Intro to X or What is X.
+    * Start working on Issue When its assigned to you by @sanjay-kv or any Maintainer. ref step 4.
+<Tabs>
+  <TabItem value="Step 1" label="Step 1">
+    <BrowserWindow url="https://github.com/recodehive/recode-website/issues" bodyStyle={{padding: 0}}>    
+     [![Github](assets/blog-01-new-issue.png)](https://github.com/recodehive/recode-website/issues)
     </BrowserWindow>
+  </TabItem>
 
+<TabItem value="Step 2" label="Step 2">
+     <BrowserWindow url="https://github.com/recodehive/recode-website/documentation" bodyStyle={{padding: 0}}>    
+     [![Github](assets/blog-02-new-issue.png)](https://github.com/recodehive/recode-website/documentations)
+    </BrowserWindow>
 
-## Step 1: Fork and Clone the Repository
-
-1. Go to [https://github.com/recodehive/recode-website](https://github.com/recodehive/recode-website) and click **Fork** (top-right corner).
-
-2. Clone your fork to your local machine:
-
-   ```bash
-   git clone https://github.com/your-username/recode-website.git
-   cd recode-website
-   ```
-
-3. Add the upstream remote so you can stay in sync:
-
-   ```bash
-   git remote add upstream https://github.com/recodehive/recode-website.git
-   ```
-
----
-
-## Step 2: Install Dependencies and Run Locally
+  </TabItem>
+    
+  <TabItem value="Step 3" label="Step 3">
+      <BrowserWindow url="https://github.com/recodehive/recode-website/issues/1586" bodyStyle={{padding: 0}}>    
+     [![Github](assets/blog-03-new-issue.png)](https://github.com/recodehive/recode-website/issues/1577)
+    </BrowserWindow>
+    </TabItem>
 
-```bash
-npm install
-npm start
-```
+  <TabItem value="Step 4" label="Step 4">
+      <BrowserWindow url="https://github.com/recodehive/recode-website/issues/1577" bodyStyle={{padding: 0}}>    
+     [![Github](assets/blog-04-new-issue.png)](https://github.com/recodehive/recode-website/issues/1577)
+    </BrowserWindow>
+    </TabItem>
+  
+</Tabs>
 
-This starts a local development server. Open [http://localhost:3000](http://localhost:3000) in your browser to preview the site live. Changes you make to files will hot-reload automatically.
+:::
 
+#### Just follow the steps on forking the repositories and installing the dependencies on your local repository, if you dont know refer the steps 2 to 6 on [welcome page](https://www.recodehive.com/docs/).
 ---
 
 ## Step 3: Create a New Branch
 
-Never commit directly to `main`. Create a dedicated branch for your blog post:
+Never commit directly to `main`. Create a dedicated branch for your blog post: test
 
 ```bash
 git checkout -b blog/your-blog-title