added blog changes and pushing google doc

Author: sanjay-kv

blog/google-icon-update/assets/11-google-new-design-changes.jpg

@@ -22,15 +22,15 @@ meta:
   - property: "og:url"
     content: "https://www.recodehive.com/blog/google-icon-update"
   - property: "og:image"
-    content: "./images/cover.png"
+    content: "./assets/cover-google-icon.jpg"
   - 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"
+    content: "./assets/cover-google-icon.jpg"
 ---
 
 import Tabs from '@theme/Tabs';
@@ -152,11 +152,14 @@ My honest take: some of the new icons are significantly better, Drive and Calend
 
 ## Does It Actually Solve the Problem?
 
-Yes. Partially.
+<span style={{color: 'red'}}> **Yes. Partially. </span>
 
 The core complaint for five years was that all the icons look the same. That complaint is addressed. Calendar is now blue. Drive is now gradient-triangle. Gmail is now warm red-pink. Each app has a visual identity that survives a glance rather than requiring a read.
 
 What is not addressed is the deeper question of whether icon design is even the right layer to solve the problem at. The real confusion in a modern Google workflow is not which icon to click. It is which Google product to use for which task. Should this document live in Drive or Sites? Should this conversation happen in Chat or Gmail? Should this meeting be in Meet or Calendar notes?
+  <BrowserWindow url="https://github.com/recodehive/recode-website/issues" bodyStyle={{padding: 0}}>    
+     [![Github](./assets/11-google-new-design-changes.jpg)]()
+    </BrowserWindow>
 
 Icon legibility is a surface-level fix for a suite that has genuine overlap and redundancy problems underneath. The new icons will help you click the right app faster. They will not help you decide which app you actually need.
 
@@ -170,7 +173,7 @@ Google changing its icons is a small thing in isolation. But it is interesting a
 
 Companies only fix long-standing UX complaints when something else is changing around them. The gradient design language, the AI product push, Google I/O timing, the Workspace positioning against Microsoft 365 and Microsoft Copilot. The icon redesign is a small piece of a larger repositioning story that Google is telling right now.
 
-Whether the new icons are beautiful or not matters less than whether they work. And by the only measure that actually counts, distinguishing one app from another in half a second, the 2026 redesign works better than the 2020 one did.
+Whether the new icons are beautiful or not matters less than whether they work. And by the only measure that actually counts, distinguishing one app from another in half a second, <span style={{color: 'red'}}> **the 2026 redesign works better than the 2020 one did.**</span>
 
 
 

blog/google-icon-update/assets/cover.jpg

@@ -268,6 +268,8 @@ Google changing its icons is a small thing in isolation. But it is interesting a
 ---
 **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.
+
+<GiscusComments/>
 ```
 
 :::info
@@ -323,24 +325,22 @@ Use `##` and `###` headings to structure your content.
 
 #### Bulleted Summary Section (Required)
 
-Every techincal explanation blog must begin with a bulleted summary right after the intro paragraph. This helps readers quickly understand what they'll learn.
+Every techincal explanation blog eg: `how to run codeql on GitHub` must begin with a bulleted summary right after the intro paragraph. This helps readers quickly understand what they'll learn.
 
 ```md
 **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
 ```
-
-    <BrowserWindow url="https://github.com/recodehive/recode-website/issues" bodyStyle={{padding: 0}}>    
-     [![Github](assets/blog-09-new-issue.png)](https://github.com/recodehive/recode-website/issues)
-    </BrowserWindow>
   </TabItem>
+  
 
 <TabItem value="Add code blocks" label="Add code blocks">
      #### Named Code Blocks (Required)
 
 Always label code blocks with a filename so readers know exactly what file they are editing:
+Once you copy paste this block it will appear exactly like this for the users.
 
 ````md
 ```java title="Sample.java"
@@ -351,9 +351,7 @@ public class Hello {
 }
 ```
 ````
-  <BrowserWindow url="https://github.com/recodehive/recode-website/issues" bodyStyle={{padding: 0}}>    
-     [![Github](assets/blog-10-new-issue.png)](https://github.com/recodehive/recode-website/issues)
-    </BrowserWindow>
+
   </TabItem>
 
   <TabItem value="Query + Output: Use Tabs" label="Query + Output: Use Tabs">
@@ -372,37 +370,50 @@ Then structure your query + output like this:
 
 ````md
 <Tabs>
-  <TabItem value="Query">
+  <TabItem value="SQL Table" label="SQL Table">
+```sql title="Friends"
+  | id | name            | username         |
+|----|-----------------|------------------|
+| 1  | John Doe        | @johndoe         |
+| 2  | Jane Smith      | @janesmith       |
+| 3  | Bob Johnson     | @bobjohnson      |
+```
+  </TabItem>
+
+<TabItem value="SQL Code" label="SQL Code">
+  
+  ```sql title="Creating SQL Tables & db. "
+
+    -- creating database
+    CREATE DATABASE my_database;
+
+    -- use the database you created
+    USE my_database;
+
 
-  ```sql
   -- Create the table
-  CREATE TABLE friends (
+CREATE TABLE friends (
     id INT PRIMARY KEY,
     name VARCHAR(100),
     username VARCHAR(100)
-  );
+);
 
-  -- Insert data
-  INSERT INTO friends (id, name, username) VALUES
-  (1, 'John Doe', 'johndoe'),
-  (2, 'Jane Smith', 'janesmith'),
-  (3, 'Bob Johnson', 'bobjohnson');
-  ```
+-- Insert data into the table
+INSERT INTO friends (id, name, username) VALUES
+(1, 'John Doe', '@johndoe'),
+(2, 'Jane Smith', '@janesmith'),
+(3, 'Bob Johnson', '@bobjohnson');
 
-  </TabItem>
-  <TabItem value="Output">
-
-  | id | name        | username    |
-  |----|-------------|-------------|
-  | 1  | John Doe    | johndoe     |
-  | 2  | Jane Smith  | janesmith   |
-  | 3  | Bob Johnson | bobjohnson  |
+    ```
 
   </TabItem>
+    
 </Tabs>
+
+
 ````
   <BrowserWindow url="https://github.com/recodehive/recode-website/issues" bodyStyle={{padding: 0}}>    
-     [![Github](assets/blog-10-new-issue.png)](https://github.com/recodehive/recode-website/issues)
+     [![Github](assets/blog-14-new-issue.png)](https://github.com/recodehive/recode-website/issues)
     </BrowserWindow>
   </TabItem>
 
@@ -429,7 +440,7 @@ Especially from an experienced engineers, it will be easy for new genertion code
 :::
 
 
-## Step 11: Add Screenshots and Images
+## Step 11: Add Screenshots and Banner
 
 ### Recommended Screenshot Dimensions
 

blog/google-icon-update/index.md

@@ -13,14 +13,14 @@ const blogs: Blog[] = [
 
   {
     id: 1,
-    title: "Land a Job in UI/UX Design",
-    image: "/img/blogs/04-ux-job-design.png",
+    title: "New Google Icon Changes",
+    image: "/img/blogs/cover-google-icon.jpg",
     description:
-      " Are you passionate about design and dreaming of a career in it? Or maybe you are already in the design space and looking to pivot into UI/UX? ",
-    slug: "ux-ui-design-job",
-    authors: ["sowmiya-v", "sanjay-kv"],
+      " Google has unveiled a new icon design that reflects its commitment to simplicity and accessibility. The updated icon features a more modern ",
+    slug: "google-icon-update",
+    authors: ["sanjay-kv"],
     category: "Design",
-    tags: ["UX", "UI", "Career", "Job"],
+    tags: ["UX", "UI", "design", "Job"],
   },
 
   {