Skip to content

Commit 9d438ad

Browse files
sanjay-kvsanjay-kv
committed
new blog directory and help page update
1 parent cdf798f commit 9d438ad

4 files changed

Lines changed: 196 additions & 55 deletions

File tree

‎blog/google-icon-update/index.md‎

Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
---
2+
title: "Google Changed Workspace Icon after 6 years"
3+
authors: [sanjay-kv]
4+
sidebar_label: "Google Changed Workspace Icon after 6 years"
5+
tags: [google, icons]
6+
date: 2026-05-21
7+
8+
description: Google Changed Workspace Icon after 6 years, What Changed, What Did Not, and Why It Took Six Years
9+
10+
draft: false
11+
canonical_url: https://www.recodehive.com/blog/google-icon-update
12+
13+
meta:
14+
- name: "robots"
15+
content: "index, follow"
16+
- property: "og:title"
17+
content: "Google Changed Workspace Icon after 6 years"
18+
- property: "og:description"
19+
content: "Google Just Changed Every Workspace Icon: What Actually Changed and Why It Took Six Years."
20+
- property: "og:type"
21+
content: "article"
22+
- property: "og:url"
23+
content: "https://www.recodehive.com/blog/google-icon-update"
24+
- property: "og:image"
25+
content: "./images/cover.png"
26+
- name: "twitter:card"
27+
content: "summary_large_image"
28+
- name: "twitter:title"
29+
content: "Google Just Changed Every Workspace Icon: What Actually Changed and Why It Took Six Years"
30+
- name: "twitter:description"
31+
content: "Google Changed Workspace Icon after 6 years"
32+
- name: "twitter:image"
33+
content: "./images/cover.png"
34+
---
35+
36+
import Tabs from '@theme/Tabs';
37+
import TabItem from '@theme/TabItem';
38+
39+
<!-- truncate -->
40+
41+
---
42+
43+
Last week I clicked Google Meet when I meant to click Google Calendar. Again.
44+
45+
46+
---
47+
48+
## The Problem That Started in 2020
49+
50+
To understand why this redesign matters, you have to go back to October 2020 when Google rebranded G Suite to Google Workspace.
51+
52+
---
53+
54+
## What Changed in 2026
55+
56+
The new icons do one thing that the 2020 redesign refused to do: they let each app look different from the others.
57+
58+
59+
---
60+
61+
## Why Google Is Doing This Now
62+
63+
Two reasons. One practical, one strategic.
64+
65+
---
66+
67+
## What the Internet Actually Thinks
68+
69+
Reactions are split, which is predictable and honestly fair.
70+
71+
---
72+
73+
## Does It Actually Solve the Problem?
74+
75+
Yes. Partially.
76+
77+
---
78+
79+
## What to Watch Next
80+
81+
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.
82+
83+
---
84+
85+
## The Bigger Picture
86+
87+
Google changing its icons is a small thing in isolation. But it is interesting as a signal.
88+
89+
---
90+
91+
**About the Author**
92+
93+
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.
94+
95+

‎docs/assets/blog-07-new-issue.png‎

193 KB
Loading

‎docs/assets/blog-08-new-issue.png‎

90 KB
Loading

‎docs/getting_started.md‎

Lines changed: 101 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ Open your code editor and head into sidebar and expand the `blog` folder
8888
and open the file `authors.yml`. Refer the below image and copy paste the code into the yml as shown.
8989
Replace my name with your name and respective website links of yours.
9090

91-
```bash
91+
```yaml
9292
sanjay-kv:
9393
name: Sanjay Viswanthan
9494
title: Founder at recode hive
@@ -113,6 +113,7 @@ sanjay-kv:
113113
[![Github](assets/blog-06-new-issue.png)](vs-code-terminal)
114114
</BrowserWindow>
115115
116+
The `your-author-id` value must exactly match what you put in the `authors` field of your frontmatter.
116117

117118
---
118119

@@ -131,63 +132,110 @@ blog/
131132
└── step-01.png
132133
```
133134
134-
Create the folder and file:
135+
you can manually Create the folder and file or use below code:
135136
136137
```bash
137138
mkdir -p blog/your-blog-title/images
138139
touch blog/your-blog-title/index.md
139140
```
141+
<Tabs>
142+
<TabItem value="Step 7" label="Step 7">
143+
<BrowserWindow url="https://github.com/recodehive/recode-website/issues" bodyStyle={{padding: 0}}>
144+
[![Github](assets/blog-07-new-issue.png)](https://github.com/recodehive/recode-website/issues)
145+
</BrowserWindow>
146+
</TabItem>
140147

141-
---
142-
143-
148+
<TabItem value="Step 8" label="Step 8">
149+
<BrowserWindow url="https://github.com/recodehive/recode-website/documentation" bodyStyle={{padding: 0}}>
150+
[![Github](assets/blog-08-new-issue.png)](https://github.com/recodehive/recode-website/documentations)
151+
</BrowserWindow>
144152

153+
</TabItem>
154+
155+
</Tabs>
156+
---
145157

146158

147159
:::tip Blog Quality Checklist
148-
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:
149-
150-
- 1. 5 backlinks to different external websites to support our documentation.
151-
- 2. 5 internal backlinks to other articles on recodehive.
152-
153-
- 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.)
154-
155-
- 4. Image filenames must be descriptive and SEO-friendly — no random names like `screenshot123.png`.
156-
- 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.
157-
158-
- 6. Include a **bulleted summary section** at the top of the blog post.
159-
- 7. Include a **FAQ section** at the bottom.
160-
- 8. Use Docusaurus admonitions (`:::tip`, `:::info`, `:::note`) for callouts, tips, and cautions (see formatting guidelines below).
161-
- 9. Tables must be **center-aligned** - wrap them in an `:::info` block to achieve this in Docusaurus.
162-
- 10. Use **named code blocks** with a filename label when showing code (e.g., ` ```java title="Sample.java" `).
163-
- 11. When showing a query and its output together, use a **Tabs** block with separate "Query" and "Output" tabs.
164-
- 12. Screenshots must follow the naming convention and size guidelines below.
160+
Let's start write article
165161
:::
166162

167163

168-
169164
## Step 5: Write the Frontmatter
170165

171166
Open `blog/your-blog-title/index.md` and add the following frontmatter at the very top of the file:
172167

173-
```md
174-
---
175-
title: "Your Blog Post Title"
176-
authors: [your-author-id]
177-
sidebar_label: "Your Blog Post Title"
178-
tags: [tag1, tag2, tag3]
179-
date: 2026-04-30
168+
```yaml
169+
title: "Google Changed Workspace Icon after 6 years"
170+
authors: [sanjay-kv]
171+
sidebar_label: "Google Changed Workspace Icon after 6 years"
172+
tags: [google, icons]
173+
date: 2026-05-21
180174

181-
description: A one or two sentence summary of what this blog post covers.
175+
description: Google Changed Workspace Icon after 6 years, What Changed, What Did Not, and Why It Took Six Years
182176

183177
draft: false
184-
canonical_url:
178+
canonical_url: https://www.recodehive.com/blog/google-icon-update
179+
180+
meta:
181+
- name: "robots"
182+
content: "index, follow"
183+
- property: "og:title"
184+
content: "Google Changed Workspace Icon after 6 years"
185+
- property: "og:description"
186+
content: "Google Just Changed Every Workspace Icon: What Actually Changed and Why It Took Six Years."
187+
- property: "og:type"
188+
content: "article"
189+
- property: "og:url"
190+
content: "https://www.recodehive.com/blog/google-icon-update"
191+
- property: "og:image"
192+
content: "./images/cover.png"
193+
- name: "twitter:card"
194+
content: "summary_large_image"
195+
- name: "twitter:title"
196+
content: "Google Just Changed Every Workspace Icon: What Actually Changed and Why It Took Six Years"
197+
- name: "twitter:description"
198+
content: "Google Changed Workspace Icon after 6 years"
199+
- name: "twitter:image"
200+
content: "./images/cover.png"
201+
202+
import Tabs from '@theme/Tabs';
203+
import TabItem from '@theme/TabItem';
204+
205+
<!-- truncate -->
206+
---
207+
Last week I clicked Google Meet when I meant to click Google Calendar. Again.
208+
---
209+
## The Problem That Started in 2020
210+
To understand why this redesign matters, you have to go back to October 2020 when Google rebranded G Suite to Google Workspace.
211+
---
212+
## What Changed in 2026
213+
The new icons do one thing that the 2020 redesign refused to do: they let each app look different from the others.
214+
---
215+
## Why Google Is Doing This Now
216+
Two reasons. One practical, one strategic.
217+
---
218+
## What the Internet Actually Thinks
219+
Reactions are split, which is predictable and honestly fair.
220+
---
221+
## Does It Actually Solve the Problem?
222+
Yes. Partially.
223+
---
224+
## What to Watch Next
225+
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.
226+
---
227+
## The Bigger Picture
228+
Google changing its icons is a small thing in isolation. But it is interesting as a signal.
185229
---
230+
**About the Author**
231+
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.
186232
```
187233

234+
:::info
235+
188236
| Field | Description |
189237
|---|---|
190-
| `title` | The full title displayed at the top of the post and in search results |
238+
| `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|
191239
| `authors` | Your author ID from `blog/authors.yml` (see Step 6) |
192240
| `sidebar_label` | Short label shown in navigation sidebars |
193241
| `tags` | Comma-separated list of relevant topic tags |
@@ -196,32 +244,12 @@ canonical_url:
196244
| `draft` | Set to `true` to hide the post; `false` to publish |
197245
| `canonical_url` | Leave blank unless cross-posting from another site |
198246

199-
---
200-
201-
## Step 6: Register Yourself as an Author
202-
203-
Open `blog/authors.yml` and add an entry for yourself if you are not already listed:
204-
205-
```yaml
206-
your-author-id:
207-
name: Your Full Name
208-
title: Your Role or Title
209-
url: https://github.com/your-username
210-
image_url: https://avatars.githubusercontent.com/u/YOUR_GITHUB_USER_ID?v=4
211-
page: true
212-
description: >
213-
A short bio about yourself (2–3 sentences).
214-
socials:
215-
github: your-username
216-
linkedin: your-linkedin-handle # optional
217-
x: your-twitter-handle # optional
218-
```
247+
:::
219248

220-
The `your-author-id` value must exactly match what you put in the `authors` field of your frontmatter.
221249

222250
---
223251

224-
## Step 7: Write Your Blog Content
252+
## Step 7: Write Your Blog Content : resume
225253

226254
After the closing `---` of your frontmatter, add the `<!-- truncate -->` comment. Everything **above** this comment becomes the preview shown on the blog listing page; everything below is the full post.
227255

@@ -257,7 +285,25 @@ Every blog must begin with a bulleted summary right after the intro paragraph. T
257285
```
258286

259287
---
288+
:::tip Blog Quality Checklist
289+
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:
290+
291+
- 1. 5 backlinks to different external websites to support our documentation.
292+
- 2. 5 internal backlinks to other articles on recodehive.
293+
294+
- 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.)
295+
296+
- 4. Image filenames must be descriptive and SEO-friendly — no random names like `screenshot123.png`.
297+
- 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.
260298

299+
- 6. Include a **bulleted summary section** at the top of the blog post.
300+
- 7. Include a **FAQ section** at the bottom.
301+
- 8. Use Docusaurus admonitions (`:::tip`, `:::info`, `:::note`) for callouts, tips, and cautions (see formatting guidelines below).
302+
- 9. Tables must be **center-aligned** - wrap them in an `:::info` block to achieve this in Docusaurus.
303+
- 10. Use **named code blocks** with a filename label when showing code (e.g., ` ```java title="Sample.java" `).
304+
- 11. When showing a query and its output together, use a **Tabs** block with separate "Query" and "Output" tabs.
305+
- 12. Screenshots must follow the naming convention and size guidelines below.
306+
:::
261307
#### Named Code Blocks (Required)
262308

263309
Always label code blocks with a filename so readers know exactly what file they are editing:

0 commit comments

Comments
 (0)