diff --git a/blog/google-icon-update/index.md b/blog/google-icon-update/index.md
new file mode 100644
index 00000000..bc6da150
--- /dev/null
+++ b/blog/google-icon-update/index.md
@@ -0,0 +1,99 @@
+---
+title: "Google Changed Workspace Icon after 6 years"
+authors: [sanjay-kv]
+sidebar_label: "Google Changed Workspace Icon after 6 years"
+tags: [google, icons]
+date: 2026-05-21
+
+description: Google Changed Workspace Icon after 6 years, What Changed, What Did Not, and Why It Took Six Years
+
+draft: false
+canonical_url: https://www.recodehive.com/blog/google-icon-update
+
+meta:
+ - name: "robots"
+ content: "index, follow"
+ - property: "og:title"
+ content: "Google Changed Workspace Icon after 6 years"
+ - property: "og:description"
+ content: "Google Just Changed Every Workspace Icon: What Actually Changed and Why It Took Six Years."
+ - property: "og:type"
+ content: "article"
+ - property: "og:url"
+ content: "https://www.recodehive.com/blog/google-icon-update"
+ - property: "og:image"
+ content: "./images/cover.png"
+ - name: "twitter:card"
+ content: "summary_large_image"
+ - name: "twitter:title"
+ content: "Google Just Changed Every Workspace Icon: What Actually Changed and Why It Took Six Years"
+ - name: "twitter:description"
+ content: "Google Changed Workspace Icon after 6 years"
+ - name: "twitter:image"
+ content: "./images/cover.png"
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+
+
+---
+
+Last week I clicked Google Meet when I meant to click Google Calendar. Again.
+
+**What you'll learn in this post:**
+- How to set up X from scratch
+- How to configure Y for production
+- Common pitfalls and how to avoid them
+
+---
+
+## The Problem That Started in 2020
+
+To understand why this redesign matters, you have to go back to October 2020 when Google rebranded G Suite to Google Workspace.
+
+---
+
+## What Changed in 2026
+
+The new icons do one thing that the 2020 redesign refused to do: they let each app look different from the others.
+
+
+---
+
+## Why Google Is Doing This Now
+
+Two reasons. One practical, one strategic.
+
+---
+
+## What the Internet Actually Thinks
+
+Reactions are split, which is predictable and honestly fair.
+
+---
+
+## Does It Actually Solve the Problem?
+
+Yes. Partially.
+
+---
+
+## What to Watch Next
+
+The rollout is live but incomplete as of today. Google I/O 2026 this week is the most likely venue for a formal announcement with a full rollout timeline. If you are not seeing the new icons in your web launcher yet, they are coming within days based on current reports.
+
+---
+
+## The Bigger Picture
+
+Google changing its icons is a small thing in isolation. But it is interesting as a signal.
+
+---
+
+**About the Author**
+
+Sanjay is a Data Engineer focused on building modern data platforms and writing about technology at RecodeHive. He writes about data engineering, cloud architecture, and the tech decisions that actually affect people's daily work.
+
+
diff --git a/docs/assets/blog-05-new-issue.png b/docs/assets/blog-05-new-issue.png
new file mode 100644
index 00000000..a2271199
Binary files /dev/null and b/docs/assets/blog-05-new-issue.png differ
diff --git a/docs/assets/blog-06-new-issue.png b/docs/assets/blog-06-new-issue.png
new file mode 100644
index 00000000..59c4a0aa
Binary files /dev/null and b/docs/assets/blog-06-new-issue.png differ
diff --git a/docs/assets/blog-07-new-issue.png b/docs/assets/blog-07-new-issue.png
new file mode 100644
index 00000000..52c50c34
Binary files /dev/null and b/docs/assets/blog-07-new-issue.png differ
diff --git a/docs/assets/blog-08-new-issue.png b/docs/assets/blog-08-new-issue.png
new file mode 100644
index 00000000..214db802
Binary files /dev/null and b/docs/assets/blog-08-new-issue.png differ
diff --git a/docs/assets/blog-09-new-issue.png b/docs/assets/blog-09-new-issue.png
new file mode 100644
index 00000000..9c3342b7
Binary files /dev/null and b/docs/assets/blog-09-new-issue.png differ
diff --git a/docs/assets/blog-10-new-issue.png b/docs/assets/blog-10-new-issue.png
new file mode 100644
index 00000000..04fd59c1
Binary files /dev/null and b/docs/assets/blog-10-new-issue.png differ
diff --git a/docs/assets/blog-11-new-issue.png b/docs/assets/blog-11-new-issue.png
new file mode 100644
index 00000000..bd9c6587
Binary files /dev/null and b/docs/assets/blog-11-new-issue.png differ
diff --git a/docs/assets/blog-12-new-issue.png b/docs/assets/blog-12-new-issue.png
new file mode 100644
index 00000000..998de6e1
Binary files /dev/null and b/docs/assets/blog-12-new-issue.png differ
diff --git a/docs/assets/blog-13-new-issue.png b/docs/assets/blog-13-new-issue.png
new file mode 100644
index 00000000..033268cc
Binary files /dev/null and b/docs/assets/blog-13-new-issue.png differ
diff --git a/docs/getting_started.md b/docs/getting_started.md
index 50681b74..9b219353 100644
--- a/docs/getting_started.md
+++ b/docs/getting_started.md
@@ -34,8 +34,8 @@ Head to the the GitHub issue on this [repository](https://github.com/recodehive/
-
- [](https://github.com/recodehive/recode-website/documentations)
+
+ [](https://github.com/recodehive/recode-website/issues)
@@ -59,41 +59,65 @@ Head to the the GitHub issue on this [repository](https://github.com/recodehive/
#### 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
+## Step 5: Create a New Branch
+
+Open your code editor and head into terminal and check current 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
```
-Use a short, descriptive name β for example `blog/intro-to-docker` or `blog/react-hooks-guide`.
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
+ :::info
+the best practice, Use a short, descriptive name for example `blog/intro-to-docker` or `blog/react-hooks-guide`.
+:::
+
---
-:::tip Blog Quality Checklist
-Before starting any development, make sure your blog meets **all** of the following criteria. Your blog can be **rejected** if any requirement is not fulfilled:
+## Step 6: Add your name to Author list : optional
+:::info
+If you are first time contributing to blog section, add yourself as author, this gives you good visibility on Google search and better career opportunities.
+:::
+Open your code editor and head into sidebar and expand the `blog` folder
+and open the file `authors.yml`. Refer the below image and copy paste the code into the yml as shown.
+Replace my name with your name and respective website links of yours.
-- 1. 5 backlinks to different external websites to support our documentation.
-- 2. 5 internal backlinks to other articles on recodehive.
+```yaml
+sanjay-kv:
+ name: Sanjay Viswanthan
+ title: Founder at recode hive
+ url: www.sanjaykv.com
+ image_url: https://avatars.githubusercontent.com/u/30715153?v=4
+ email: sanjay@recodehive.com
+ page: true # Turns the feature on
+ description: >
+ I'm a Software Engineer turned into a Data Engineer and Program Managerπ, π Google ML Facilitator & Ex- GitHub CE who delivered 100+ talks on ML and open source and developer advocacy at various events and platforms.
-- 3. **No generic content** β avoid surface-level topics like "what is Azure" or "difference between X and Y". Write pure, high-depth technical articles with images. See [this example](https://www.recodehive.com/docs/GitHub/Maintainer-guide/milestone) for the standard we aim for. (Tip: tools like [Snagit](https://www.techsmith.com/screen-capture.html) help produce great annotated screenshots.)
+ socials:
+ x: https://x.com/sanjay_kv_
+ linkedin: sanjay-k-v
+ github: sanjay-kv
+ stackoverflow: 8332327
+ instagram: nomad_brains
+ newsletter: https://recodehive.substack.com
+ bluesky: sanjaykv.bsky.social
+```
-- 4. Image filenames must be descriptive and SEO-friendly β no random names like `screenshot123.png`.
-- 5. **Content-to-code ratio**: text should be more than code. Adsense flags pages at 60% code / 40% text - keep it the opposite. If code is long, link to GitHub and reference it in comments instead.
+
+ [](https://github.com/recodehive/recode-website/issues)
+
-- 6. Include a **bulleted summary section** at the top of the blog post.
-- 7. Include a **FAQ section** at the bottom.
-- 8. Use Docusaurus admonitions (`:::tip`, `:::info`, `:::note`) for callouts, tips, and cautions (see formatting guidelines below).
-- 9. Tables must be **center-aligned** - wrap them in an `:::info` block to achieve this in Docusaurus.
-- 10. Use **named code blocks** with a filename label when showing code (e.g., ` ```java title="Sample.java" `).
-- 11. When showing a query and its output together, use a **Tabs** block with separate "Query" and "Output" tabs.
-- 12. Screenshots must follow the naming convention and size guidelines below.
-:::
+The `your-author-id` value must exactly match what you put in the `authors` field of your frontmatter.
---
-## Step 4: Create the Blog Folder and File
+## Step 7: Create the Blog Folder and File
All blog posts live inside the `blog/` directory. Each post gets its own folder.
@@ -103,42 +127,156 @@ All blog posts live inside the `blog/` directory. Each post gets its own folder.
blog/
βββ your-blog-title/
βββ index.md β your blog content
- βββ images/ β screenshots and images (optional)
+ βββ assets/ β screenshots and images (optional png or jpeg)
βββ cover.png
βββ step-01.png
```
-Create the folder and file:
+you can manually Create the folder and file or use below code:
```bash
-mkdir -p blog/your-blog-title/images
+mkdir -p blog/your-blog-title/assets
touch blog/your-blog-title/index.md
```
+
+
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
+
+
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
+
+
---
-## Step 5: Write the Frontmatter
+
+
+
+## Step 9: Write the Frontmatter
Open `blog/your-blog-title/index.md` and add the following frontmatter at the very top of the file:
-```md
----
-title: "Your Blog Post Title"
-authors: [your-author-id]
-sidebar_label: "Your Blog Post Title"
-tags: [tag1, tag2, tag3]
-date: 2026-04-30
+:::tip Blog Quality Checklist
+Copy paste the below code into your index.md file you created, then before writing we slowly change the title and details over here. first thing you need to match the author ID same as you created in authors.yaml file.
+:::
+
+
+ Don't change whatever in the highlighted red area, change the link same as folder name, so it will be easy to edit.
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
+
+
+ Do `npm run build` and complete the build to see everything works fine.
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
+
+
+ Do `npm run serve` or `npm start` and open local host to see the local changes you made.
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
+
+
+ Do search this in local host `http://localhost:3000/your-blog-canonical-url`
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
-description: A one or two sentence summary of what this blog post covers.
+
+ Do search this in local host `http://localhost:3000/your-blog-canonical-url`
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
+
+```yaml
+title: "Google Changed Workspace Icon after 6 years"
+authors: [sanjay-kv]
+sidebar_label: "Google Changed Workspace Icon after 6 years"
+tags: [google, icons]
+date: 2026-05-21
+
+description: Google Changed Workspace Icon after 6 years, What Changed, What Did Not, and Why It Took Six Years
draft: false
-canonical_url:
+canonical_url: https://www.recodehive.com/blog/google-icon-update
+
+meta:
+ - name: "robots"
+ content: "index, follow"
+ - property: "og:title"
+ content: "Google Changed Workspace Icon after 6 years"
+ - property: "og:description"
+ content: "Google Just Changed Every Workspace Icon: What Actually Changed and Why It Took Six Years."
+ - property: "og:type"
+ content: "article"
+ - property: "og:url"
+ content: "https://www.recodehive.com/blog/google-icon-update"
+ - property: "og:image"
+ content: "./images/cover.png"
+ - name: "twitter:card"
+ content: "summary_large_image"
+ - name: "twitter:title"
+ content: "Google Just Changed Every Workspace Icon: What Actually Changed and Why It Took Six Years"
+ - name: "twitter:description"
+ content: "Google Changed Workspace Icon after 6 years"
+ - name: "twitter:image"
+ content: "./images/cover.png"
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+
+---
+Last week I clicked Google Meet when I meant to click Google Calendar. Again.
+
+**What you'll learn in this post:**
+- How to set up X from scratch
+- How to configure Y for production
+- Common pitfalls and how to avoid them
+---
+## The Problem That Started in 2020
+To understand why this redesign matters, you have to go back to October 2020 when Google rebranded G Suite to Google Workspace.
---
+## What Changed in 2026
+The new icons do one thing that the 2020 redesign refused to do: they let each app look different from the others.
+---
+## Why Google Is Doing This Now
+Two reasons. One practical, one strategic.
+---
+## What the Internet Actually Thinks
+Reactions are split, which is predictable and honestly fair.
+---
+## Does It Actually Solve the Problem?
+Yes. Partially.
+---
+## What to Watch Next
+The rollout is live but incomplete as of today. Google I/O 2026 this week is the most likely venue for a formal announcement with a full rollout timeline. If you are not seeing the new icons in your web launcher yet, they are coming within days based on current reports.
+---
+## The Bigger Picture
+Google changing its icons is a small thing in isolation. But it is interesting as a signal.
+---
+**About the Author**
+Sanjay is a Data Engineer focused on building modern data platforms and writing about technology at RecodeHive. He writes about data engineering, cloud architecture, and the tech decisions that actually affect people's daily work.
```
+:::info
+
| Field | Description |
|---|---|
-| `title` | The full title displayed at the top of the post and in search results |
+| `title` | The full title displayed at the top of the post and in search results, Make sure you do research and SEO analysis before proceeding with title|
| `authors` | Your author ID from `blog/authors.yml` (see Step 6) |
| `sidebar_label` | Short label shown in navigation sidebars |
| `tags` | Comma-separated list of relevant topic tags |
@@ -147,34 +285,23 @@ canonical_url:
| `draft` | Set to `true` to hide the post; `false` to publish |
| `canonical_url` | Leave blank unless cross-posting from another site |
----
-
-## Step 6: Register Yourself as an Author
+:::
-Open `blog/authors.yml` and add an entry for yourself if you are not already listed:
-```yaml
-your-author-id:
- name: Your Full Name
- title: Your Role or Title
- url: https://github.com/your-username
- image_url: https://avatars.githubusercontent.com/u/YOUR_GITHUB_USER_ID?v=4
- page: true
- description: >
- A short bio about yourself (2β3 sentences).
- socials:
- github: your-username
- linkedin: your-linkedin-handle # optional
- x: your-twitter-handle # optional
-```
+---
-The `your-author-id` value must exactly match what you put in the `authors` field of your frontmatter.
+## Step 10: Write Your Blog Content : Guidelines
----
+:::tip Blog Quality Checklist
+Now here comes the crutial part, it doesnt matter how it get start, but you gotta finish it as good quality work.
+Open the below taps to find most common errors and guidelines for beautification
-## Step 7: Write Your Blog Content
+
+
+
+ You have already copied this code before, im just explaining what it is. So you know what you doing π₯.
-After the closing `---` of your frontmatter, add the `` comment. Everything **above** this comment becomes the preview shown on the blog listing page; everything below is the full post.
+ After the closing `---` of your frontmatter, add the `` comment. Everything **above** this comment becomes the preview shown on the blog listing page; everything below is the full post.
```md
---
@@ -207,9 +334,13 @@ Every blog must begin with a bulleted summary right after the intro paragraph. T
- Common pitfalls and how to avoid them
```
----
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
-#### Named Code Blocks (Required)
+
+ #### Named Code Blocks (Required)
Always label code blocks with a filename so readers know exactly what file they are editing:
@@ -222,10 +353,13 @@ public class Hello {
}
```
````
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
----
-
-#### Query + Output: Use Tabs (Required)
+
+ #### Named Code Blocks (Required when writing technical articles)
When showing a database query alongside its output, use a Tabs block so both fit in a single window.
@@ -269,13 +403,119 @@ Then structure your query + output like this:
````
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
+
+
+
+:::
+
+
+
+---
+
+
:::tip
-You can add as many `` tabs as needed β for example separate tabs per subquery type, or one tab per language variant.
+You can add as many `` tabs as needed for example separate tabs per subquery type, or one tab per language variant.
+Just check the code base on `getting_started.md`
:::
---
+:::info
+Again a reminder, dont copy from the AI, the whole purpose of we writing this to give some step by step guidelines which AI can't do.
+Especially from an experienced engineers, it will be easy for new genertion coders to start easy with reference ss of every step.
+:::
+
+
+## Step 11: Add Screenshots and Images
+
+### Recommended Screenshot Dimensions
+
+| Use Case | Recommended Size |
+|---|---|
+| Cover / hero image | **1200 Γ 630 px** (16:9 ratio, also ideal for social sharing) refer the image blocks attached below for samples|
+| Full-width step screenshots | **1280 Γ 720 px** or **1280 Γ 800 px** |
+| UI close-ups / partial screenshots | **800 Γ 450 px** |
+| Maximum file size | **500 KB** per image (compress with [Squoosh](https://squoosh.app) or [TinyPNG](https://tinypng.com)) |
+
+Use **PNG** for UI screenshots (crisp text) and **JPEG/WebP** for photos.
+
+### Naming Convention
+
+Use lowercase, hyphen-separated, numbered filenames so they sort correctly and are SEO-friendly. **Never use random or auto-generated names.**
+
+```
+assets/
+βββ cover.png
+βββ 01-open-settings.png
+βββ 02-navigate-to-plugins.png
+βββ 03-final-result.png
+```
+
+
+
+ Do `npm run build` and complete the build to see everything works fine.
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
+
+
+ Do `npm run serve` or `npm start` and open local host to see the local changes you made.
+
+ [](https://github.com/recodehive/recode-website/issues)
+
+
+
+
+
+### Embedding Images in Markdown
+
+Reference images relative to `index.md`:
+
+```md
+
+```
+
+Always write descriptive alt text β it improves accessibility and SEO.
+
+:::tip Screenshot Tool Recommendation
+Tools like [Snagit](https://www.techsmith.com/screen-capture.html) make it easy to produce annotated, professional-quality screenshots. See [this article](https://www.recodehive.com/docs/GitHub/Maintainer-guide/milestone) as a reference for the image quality standard we aim for.
+:::
+
+---
+
+## Step 12: Update the Database
+
+All blog data is linked in the database folder (`\database\blogs\index.tsx`). Update it with the following details:
+
+```json
+{
+ id: sequence_wise,
+ title: "Title of the post",
+ image: "relative path of the cover image for the blog post",
+ description: "A short (2-3) lines of description of the post",
+ slug: "The name of the blog folder (keep it exact)",
+ authors: ["your-author-id"],
+ category: "The category the blog belongs to",
+ tags: ["tags or topics the blog is related to (tools or technologies)"],
+}
+```
+
+:::note
+All details are necessary for correctly rendering the blog card on the blogs page. Take a close look and make sure everything is filled in.
+:::
+
+---
+
+
+
+
+
#### Admonitions: Tips, Notes, Info, and Cautions
Use Docusaurus admonitions to highlight important information. Don't overuse them β only where they add real value.
@@ -355,69 +595,26 @@ A: Yes, the steps are cross-platform. Windows-specific commands are noted where
---
-## Step 8: Add Screenshots and Images
-
-### Recommended Screenshot Dimensions
-
-| Use Case | Recommended Size |
-|---|---|
-| Cover / hero image | **1200 Γ 630 px** (16:9 ratio, also ideal for social sharing) |
-| Full-width step screenshots | **1280 Γ 720 px** or **1280 Γ 800 px** |
-| UI close-ups / partial screenshots | **800 Γ 450 px** |
-| Maximum file size | **500 KB** per image (compress with [Squoosh](https://squoosh.app) or [TinyPNG](https://tinypng.com)) |
-
-Use **PNG** for UI screenshots (crisp text) and **JPEG/WebP** for photos.
-
-### Naming Convention
-
-Use lowercase, hyphen-separated, numbered filenames so they sort correctly and are SEO-friendly. **Never use random or auto-generated names.**
-
-```
-images/
-βββ cover.png
-βββ 01-open-settings.png
-βββ 02-navigate-to-plugins.png
-βββ 03-final-result.png
-```
-
-### Embedding Images in Markdown
-
-Reference images relative to `index.md`:
-
-```md
-
-```
-
-Always write descriptive alt text β it improves accessibility and SEO.
-
-:::tip Screenshot Tool Recommendation
-Tools like [Snagit](https://www.techsmith.com/screen-capture.html) make it easy to produce annotated, professional-quality screenshots. See [this article](https://www.recodehive.com/docs/GitHub/Maintainer-guide/milestone) as a reference for the image quality standard we aim for.
-:::
-
----
+:::tip Blog Quality Checklist
+Before starting any development, make sure your blog meets **all** of the following criteria. Your blog can be **rejected** if any requirement is not fulfilled:
-## Step 9: Update the Database
+- 1. 5 backlinks to different external websites to support our documentation.
+- 2. 5 internal backlinks to other articles on recodehive.
-All blog data is linked in the database folder (`\database\blogs\index.tsx`). Update it with the following details:
+- 3. **No generic content** β avoid surface-level topics like "what is Azure" or "difference between X and Y". Write pure, high-depth technical articles with images. See [this example](https://www.recodehive.com/docs/GitHub/Maintainer-guide/milestone) for the standard we aim for. (Tip: tools like [Snagit](https://www.techsmith.com/screen-capture.html) help produce great annotated screenshots.)
-```json
-{
- id: sequence_wise,
- title: "Title of the post",
- image: "relative path of the cover image for the blog post",
- description: "A short (2-3) lines of description of the post",
- slug: "The name of the blog folder (keep it exact)",
- authors: ["your-author-id"],
- category: "The category the blog belongs to",
- tags: ["tags or topics the blog is related to (tools or technologies)"],
-}
-```
+- 4. Image filenames must be descriptive and SEO-friendly β no random names like `screenshot123.png`.
+- 5. **Content-to-code ratio**: text should be more than code. Adsense flags pages at 60% code / 40% text - keep it the opposite. If code is long, link to GitHub and reference it in comments instead.
-:::note
-All details are necessary for correctly rendering the blog card on the blogs page. Take a close look and make sure everything is filled in.
+- 6. Include a **bulleted summary section** at the top of the blog post.
+- 7. Include a **FAQ section** at the bottom.
+- 8. Use Docusaurus admonitions (`:::tip`, `:::info`, `:::note`) for callouts, tips, and cautions (see formatting guidelines below).
+- 9. Tables must be **center-aligned** - wrap them in an `:::info` block to achieve this in Docusaurus.
+- 10. Use **named code blocks** with a filename label when showing code (e.g., ` ```java title="Sample.java" `).
+- 11. When showing a query and its output together, use a **Tabs** block with separate "Query" and "Output" tabs.
+- 12. Screenshots must follow the naming convention and size guidelines below.
:::
----
## Step 10: Preview Your Post