Skip to content

Conversation

DIYA-bot
Copy link
Contributor

@DIYA-bot DIYA-bot commented Oct 17, 2025

Description

Fixes # (issue)

Type of Change

  • New feature (e.g., new page, component, or functionality)
  • Bug fix (non-breaking change that fixes an issue)
  • UI/UX improvement (design, layout, or styling updates)
  • Performance optimization (e.g., code splitting, caching)
  • Documentation update (README, contribution guidelines, etc.)
  • Other (please specify):

Changes Made

Dependencies

  • List any new dependencies or tools required for this change.
  • Mention any version updates or configurations that need to be considered.

Checklist

  • My code follows the style guidelines of this project.
  • I have tested my changes across major browsers and devices
  • My changes do not generate new console warnings or errors .
  • I ran npm run build and attached screenshot(s) in this PR.
  • This is already assigned Issue to me, not an unassigned issue.

The previous version of the introduction article had an illogical flow for new learners, jumping between concepts without building a proper foundation. SEO elements were also minimal.

This commit completely restructures the content to be more beginner-friendly and impactful:

-   Introduces the concept of Version Control first to establish the "why".
-   Clearly distinguishes between Git (the tool) and GitHub (the platform).
-   Improves SEO with a keyword-rich title, meta description, and tags.
-   Rewrites core concepts like 'Repository' and 'Pull Request' for better clarity.
-   Organizes the content with a logical heading structure.
The previous version of the introduction article had an illogical flow for new learners, jumping between concepts without building a proper foundation. SEO elements were also minimal.

This commit completely restructures the content to be more beginner-friendly and impactful:

-   Introduces the concept of Version Control first to establish the "why".
-   Clearly distinguishes between Git (the tool) and GitHub (the platform).
-   Improves SEO with a keyword-rich title, meta description, and tags.
-   Rewrites core concepts like 'Repository' and 'Pull Request' for better clarity.
-   Organizes the content with a logical heading structure.
1.The entire meta block was commented out and has been fixed and enabled.
2.The og:url, og:image, and og:description tags were pointing to an incorrect article about the MERN stack. They now correctly point to the DeepMind article's assets and have an accurate, well-written description.
3.The primary description field was rewritten to be grammatically correct and more compelling.
Updated content to improve clarity and consistency throughout the article, including sections on energy efficiency, healthcare applications, and AI technology.
Fix: Proofread and Correct Metadata in DeepMind Article
1.Frontmatter and Naming Standardization:

Consistent Naming: Standardized the program name to "Google Student Ambassador" throughout the article, removing confusion from variations like "Campus Ambassador" and "Gemini Ambassador."

Synced Metadata: Updated the title, slug, and id in the frontmatter to be consistent with the main <h1> heading and article content. The new slug is /google-student-ambassador-program-2025.

2. Content and Factual Accuracy:

Corrected Time Commitment: Resolved the contradiction in the FAQ. Both Q2 and Q3 now correctly state the time commitment as "5–7 hours per week."

Removed Empty Section: Deleted the "Got Questions & What Happens Next?" section, as it contained no actionable information and detracted from the article's professional tone.

3.Accessibility and Code Quality:

Added Alt Text: Provided descriptive alt text for both images, ensuring the article is accessible to screen readers.

Removed Unused Import: Deleted an unused Layout component import to clean up the code.
1.Frontmatter and Naming Standardization:

Consistent Naming: Standardized the program name to "Google Student Ambassador" throughout the article, removing confusion from variations like "Campus Ambassador" and "Gemini Ambassador."

Synced Metadata: Updated the title, slug, and id in the frontmatter to be consistent with the main <h1> heading and article content. The new slug is /google-student-ambassador-program-2025.

2. Content and Factual Accuracy:

Corrected Time Commitment: Resolved the contradiction in the FAQ. Both Q2 and Q3 now correctly state the time commitment as "5–7 hours per week."

Removed Empty Section: Deleted the "Got Questions & What Happens Next?" section, as it contained no actionable information and detracted from the article's professional tone.

3. Accessibility and Code Quality:

Added Alt Text: Provided descriptive alt text for both images, ensuring the article is accessible to screen readers.

Removed Unused Import: Deleted an unused Layout component import to clean up the code.
1.Activated Social Media Metadata:
The entire meta block containing Open Graph and Twitter card information was commented out. This has been uncommented, enabling rich previews when the article is shared on social platforms.
2.Added Canonical URL:
Populated the empty canonical_url field to prevent duplicate content issues and improve search engine indexing.
3.Aligned Page Titles:
The frontmatter title has been updated to match the on-page <h1> heading for better SEO alignment and user experience. The sidebar_label was also shortened for better UI fit.
4.Improved Image Accessibility:
Enhanced the alt text for the architecture diagram to be more descriptive for users with screen readers.
1.The entire meta block containing Open Graph and Twitter card information was commented out. This has been uncommented, enabling rich previews when the article is shared on social platforms.
2.Populated the empty canonical_url field to prevent duplicate content issues and improve search engine indexing.
3.The frontmatter title has been updated to match the on-page <h1> heading for better SEO alignment and user experience. The sidebar_label was also shortened for better UI fit.
4.Enhanced the alt text for the architecture diagram to be more descriptive for users with screen readers.
Copy link

vercel bot commented Oct 17, 2025

@DIYA-bot is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

  1. Get free Consultation use code recode50 to get free: Mentorship for free.

  2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

  3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

@github-actions github-actions bot added hacktoberfest-accepted recode this is label for leaderboard labels Oct 17, 2025
Copy link

vercel bot commented Oct 17, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
recode-website Error Error Oct 17, 2025 5:27pm

@sanjay-kv sanjay-kv added the under review Review under the maintainers or the admins label Oct 17, 2025
@sanjay-kv
Copy link
Member

04:27:30.415 Running build in Washington, D.C., USA (East) – iad1
04:27:30.416 Build machine configuration: 4 cores, 8 GB
04:27:30.431 Cloning github.com/recodehive/recode-website (Branch: main, Commit: bec2ca1)
04:27:32.560 Cloning completed: 2.129s
04:27:32.781 Restored build cache from previous deployment (EcQPuwjXBDiUCkRzyV3zB6F329kL)
04:27:33.898 Running "vercel build"
04:27:34.518 Vercel CLI 48.2.9
04:27:35.121 Warning: Detected "engines": { "node": ">=18.0" } in your package.json that will automatically upgrade when a new major Node.js Version is released. Learn More: http://vercel.link/node-version
04:27:35.125 Installing dependencies...
04:27:38.936
04:27:38.936 up to date in 4s
04:27:38.936
04:27:38.936 448 packages are looking for funding
04:27:38.936 run npm fund for details
04:27:38.984 Running "npm run build"
04:27:39.281
04:27:39.281 > [email protected] build
04:27:39.282 > docusaurus build
04:27:39.282
04:27:40.666 [INFO] [en] Creating an optimized production build...
04:27:41.212 [ERROR] Error while parsing Markdown front matter.
04:27:41.212 This can happen if you use special characters in front matter values (try using double quotes around that value).
04:27:41.235 [ERROR] Loading of version failed for version current
04:27:41.235
04:27:41.236 [ERROR] Error: Unable to build website for locale en.
04:27:41.237 at tryToBuildLocale (/vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:83:15)
04:27:41.237 at async /vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:35:9
04:27:41.237 ... 4 lines matching cause stack trace ...
04:27:41.237 at async file:///vercel/path0/node_modules/@docusaurus/core/bin/docusaurus.mjs:44:3 {
04:27:41.237 [cause]: Error: Can't process doc metadata for doc at path path=/vercel/path0/docs/Technical/intro-github.md in version name=current
04:27:41.237 at processDocMetadata (/vercel/path0/node_modules/@docusaurus/plugin-content-docs/lib/docs.js:152:15)
04:27:41.237 at async Promise.all (index 6)
04:27:41.237 at async loadVersionDocsBase (/vercel/path0/node_modules/@docusaurus/plugin-content-docs/lib/versions/loadVersion.js:63:18)
04:27:41.237 at async doLoadVersion (/vercel/path0/node_modules/@docusaurus/plugin-content-docs/lib/versions/loadVersion.js:72:22)
04:27:41.238 ... 16 lines matching cause stack trace ...
04:27:41.238 at async file:///vercel/path0/node_modules/@docusaurus/core/bin/docusaurus.mjs:44:3 {
04:27:41.238 [cause]: YAMLException: can not read a block mapping entry; a multiline key may not be an implicit key at line 19, column 23:
04:27:41.238 Key Features of GitHub:
04:27:41.238 ^
04:27:41.238 at generateError (/vercel/path0/node_modules/gray-matter/node_modules/js-yaml/lib/js-yaml/loader.js:167:10)
04:27:41.238 at throwError (/vercel/path0/node_modules/gray-matter/node_modules/js-yaml/lib/js-yaml/loader.js:173:9)
04:27:41.238 at readBlockMapping (/vercel/path0/node_modules/gray-matter/node_modules/js-yaml/lib/js-yaml/loader.js:1073:9)
04:27:41.238 at composeNode (/vercel/path0/node_modules/gray-matter/node_modules/js-yaml/lib/js-yaml/loader.js:1359:12)
04:27:41.238 at readDocument (/vercel/path0/node_modules/gray-matter/node_modules/js-yaml/lib/js-yaml/loader.js:1525:3)
04:27:41.239 at loadDocuments (/vercel/path0/node_modules/gray-matter/node_modules/js-yaml/lib/js-yaml/loader.js:1588:5)
04:27:41.239 at load (/vercel/path0/node_modules/gray-matter/node_modules/js-yaml/lib/js-yaml/loader.js:1614:19)
04:27:41.239 at Object.safeLoad (/vercel/path0/node_modules/gray-matter/node_modules/js-yaml/lib/js-yaml/loader.js:1637:10)
04:27:41.239 at module.exports (/vercel/path0/node_modules/gray-matter/lib/parse.js:12:17)
04:27:41.239 at parseMatter (/vercel/path0/node_modules/gray-matter/index.js:109:17)
04:27:41.239 at matter (/vercel/path0/node_modules/gray-matter/index.js:50:10)
04:27:41.239 at parseFileContentFrontMatter (/vercel/path0/node_modules/@docusaurus/utils/lib/markdownUtils.js:197:57)
04:27:41.239 at DEFAULT_PARSE_FRONT_MATTER (/vercel/path0/node_modules/@docusaurus/utils/lib/markdownUtils.js:216:54)
04:27:41.239 at parseMarkdownFile (/vercel/path0/node_modules/@docusaurus/utils/lib/markdownUtils.js:271:75)
04:27:41.239 at doProcessDocMetadata (/vercel/path0/node_modules/@docusaurus/plugin-content-docs/lib/docs.js:42:108)
04:27:41.239 at processDocMetadata (/vercel/path0/node_modules/@docusaurus/plugin-content-docs/lib/docs.js:149:22)
04:27:41.239 at processVersionDoc (/vercel/path0/node_modules/@docusaurus/plugin-content-docs/lib/versions/loadVersion.js:54:46)
04:27:41.240 at Array.map ()
04:27:41.240 at loadVersionDocsBase (/vercel/path0/node_modules/@docusaurus/plugin-content-docs/lib/versions/loadVersion.js:63:45)
04:27:41.240 at async doLoadVersion (/vercel/path0/node_modules/@docusaurus/plugin-content-docs/lib/versions/loadVersion.js:72:22)
04:27:41.240 at async loadVersion (/vercel/path0/node_modules/@docusaurus/plugin-content-docs/lib/versions/loadVersion.js:119:16)
04:27:41.240 at async Promise.all (index 0)
04:27:41.240 at async Object.loadContent (/vercel/path0/node_modules/@docusaurus/plugin-content-docs/lib/index.js:152:33)
04:27:41.240 at async /vercel/path0/node_modules/@docusaurus/core/lib/server/plugins/plugins.js:40:23
04:27:41.240 at async Promise.all (index 0)
04:27:41.240 at async /vercel/path0/node_modules/@docusaurus/core/lib/server/plugins/plugins.js:146:25
04:27:41.240 at async loadSite (/vercel/path0/node_modules/@docusaurus/core/lib/server/site.js:155:45)
04:27:41.241 at async buildLocale (/vercel/path0/node_modules/@docusaurus/core/lib/commands/build/buildLocale.js:33:18)
04:27:41.241 at async runBuildLocaleTask (/vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:98:5)
04:27:41.241 at async /vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:79:13
04:27:41.241 at async tryToBuildLocale (/vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:75:9)
04:27:41.241 at async /vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:35:9
04:27:41.241 at async mapAsyncSequential (/vercel/path0/node_modules/@docusaurus/utils/lib/jsUtils.js:21:24)
04:27:41.241 at async Command.build (/vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:34:5)
04:27:41.241 at async Promise.all (index 0)
04:27:41.241 at async runCLI (/vercel/path0/node_modules/@docusaurus/core/lib/commands/cli.js:56:5)
04:27:41.241 at async file:///vercel/path0/node_modules/@docusaurus/core/bin/docusaurus.mjs:44:3 {
04:27:41.241 reason: 'can not read a block mapping entry; a multiline key may not be an implicit key',
04:27:41.242 mark: Mark {
04:27:41.242 name: null,
04:27:41.242 buffer: '\n' +
04:27:41.242 'id: intro-github\n' +
04:27:41.242 'title: Getting Started with GitHub in 2025 \n' +
04:27:41.242 'sidebar_label: Introduction of GitHub #displays in sidebar\n' +
04:27:41.242 'sidebar_position: 1\n' +
04:27:41.242 'tags:\n' +
04:27:41.242 ' [\n' +
04:27:41.242 ' GitHub,git,version control\n' +
04:27:41.242 ' Introduction of GitHub,\n' +
04:27:41.242 ' What is GitHub, open source\n' +
04:27:41.242 ' Why learn GitHub,beginner guide\n' +
04:27:41.242 ' How to use GitHub,\n' +
04:27:41.242 ' ]\n' +
04:27:41.243 "description: New to GitHub? This beginner's guide explains what Git and GitHub are, why they're essential for developers, and how to start your open-source journey. Learn key concepts like repositories, commits, and pull requests.\n" +
04:27:41.243 '\n' +
04:27:41.243 'GitHub is a web-based platform used for version control and collaboration. It allows developers to work together on projects from anywhere in the world. GitHub is built on top of Git, a distributed version control system created by Linus Torvalds in 2005.\n' +
04:27:41.243 '\n' +
04:27:41.243 '\n' +
04:27:41.243 'Key Features of GitHub:\n' +
04:27:41.243 'GitHub will help you to control the version of the project on a large scale.\n' +
04:27:41.243 '\n' +
04:27:41.243 'GitHub offers Premium account for use, Premium users get unlimited Github Repo time, Storage etc. \n' +
04:27:41.243 '\n' +
04:27:41.243 '\n' +
04:27:41.243 '## How to start with GitHub?\n' +
04:27:41.243 '\n' +
04:27:41.243 'Whenever you create something exciting or something new on your own, you always want to show it to others. As programmers, we also want to show our projects and codes to others, but how? So GitHub is the solution, it lets people collaborate and scale the projects all on cloud. Some other example of simillar platform are , Bitbucket, GitLab, Beanstalk, etc. Many of them give you the facility to work on your code together as a team. Currently, Github is more popular than other above-listed platforms for hosting your code.\n' +
04:27:41.243 '\n' +
04:27:41.243 'In the picture below you could see Developer 1, Developer 2... are working on the same project , lets say they are trying to build a amazon website, developer 1 handles the Mens shopping section, Developer 2 deals with Womens section, Developer 3 works on the login feature. \n' +
04:27:41.243 '\n' +
04:27:41.244 'So each indivituals works on different feature from the copy of the central repository, once the development is done they push changes to the remote repository (central repo as per picture). Once code review happens and good to go, the senior developer will merge the code to the central repository so all the feature will be live on production.\n' +
04:27:41.244 '\n' +
04:27:41.244 ' <BrowserWindow url="https://github.com/" bodyStyle={{padding: 0}}> \n' +
04:27:41.244 ' Visual Studio Code\n' +
04:27:41.244 ' \n' +
04:27:41.244 '\n' +
04:27:41.244 '\n' +
04:27:41.244 '\n' +
04:27:41.244 '## What is Git?\n' +
04:27:41.244 '\n' +
04:27:41.244 'So in the above example all the developer where able to work on different feautre simulatneaulsy because of the git. For uploading your project to your Github account, you need to install Git first. In other words, Git helps to do this version management of the files and coordinating work among the diverse team in the software development phase. Git is an open-source project and developed in 2005 by Linus Torvalds and Junior.\n' +
04:27:41.244 '\n' +
04:27:41.245 '1.What is Version control System?: To understand the version control system, let me give you one example; sometimes, you wish you have a record that contains all the changes you made in your code or your project. The version control systems are software tools that record all of your changes in the files. It is like a database of changes. Git is a version control system that most developers prefer to use. We will see how you can upload your code on Github using Git. With VCS you can track the branch, who made changes at what time, line of code added, retrive the previous version of changes. \n' +
04:27:41.245 '2. Basic Git Terminology:\n' +
04:27:41.245 '\n' +
04:27:41.245 ' | Keyword | \tTerminology | \tDescription |\n' +
04:27:41.245 ' | --- | --------------- | -------------------- |\n' +
04:27:41.245 ' | 1.VCS | Version Control System | Track changes to a collection of files |\n' +
04:27:41.245 ' | 2.SCM | Software configuration Management | \tAnother name for VCS, the earlier version of VCS like CVS, SVN used to be centralised server, which cause single point of failure. |\n' +
04:27:41.245 ' |3. DVCS | \tDistributed Version Control System| Git is distributed, the project history is stored both in client and server. Means you can make changes locally and remote. |\n' +
04:27:41.245 ' | 4.Working Tree | Tree | Current version of files where the active project is on |\n' +
04:27:41.245 ' | 5.Repo | \tRepository | \t\tTop of working Tree where git keep all records and history. |\n' +
04:27:41.245 ' | 6.Bare repo | \t | \t\tNot part of working Tree ends with .git, eg. backup.git |\n' +
04:27:41.245 ' | 7.Hash | \t160 bit long SHA-1 | \t\tBased on the hash number, the file has been modified or not.|\n' +
04:27:41.245 ' | 8.Object | \tGit have 4 objects | \t\tTree Object(directory, names), Blob Object(main file), Commit Object(spesfic versions), Tag(name attached to commit) |\n' +
04:27:41.246 ' | 9.Commit | | \tMakes Changes |\n' +
04:27:41.246 ' | 10.Branch | \tA series of Linked commit | \tThe recent commit is called Head. |\n' +
04:27:41.246 ' |11.Remote | \t | \t\tReference to other git repo |\n' +
04:27:41.246 ' | 12.Pull Request: A proposal to merge a set of changes from one branch into another.|\n' +
04:27:41.246 ' |13.Actions: Automate your workflow, such as building, testing, and deploying your code right from GitHub.|\n' +
04:27:41.246 " |14.Fork: A personal copy of another user's repository.|\n" +
04:27:41.246 ' |Git Command | \t\tCheck this tutorial\n' +
04:27:41.246 '\n' +
04:27:41.246 '\n' +
04:27:41.246 '\n' +
04:27:41.247 '## Why Learn GitHub? \n' +
04:27:41.247 '\n' +
04:27:41.247 'GitHub Simplfy all the command line interface of Git and make it more GUI friendly. GitHub is built on top of Git. Here want we do is staging the files and doing the commit, You can clone the entire repository and create a branch and commit to that branch ask the main developer to merge the branch. when you clone in reality you are creating a copy of the real code/repository in your local environment.\n' +
04:27:41.247 '\n' +
04:27:41.247 'Git Structure\n' +
04:27:41.247 ' \n' +
04:27:41.247 ' \n' +
04:27:41.247 '\n' +
04:27:41.247 '1. Basic GitHub Keywords:\n' +
04:27:41.247 '\n' +
04:27:41.247 ' | Category | \tDescription |\n' +
04:27:41.247 ' | --- | -------------------- |\n' +
04:27:41.247 ' | Issues | Retrieve data from tables |\n' +
04:27:41.247 ' | Discussions | |\n' +
04:27:41.248 ' | Pull requests | |\n' +
04:27:41.248 ' | Notifications | |\n' +
04:27:41.248 ' | Labels | |\n' +
04:27:41.248 ' | Actions | |\n' +
04:27:41.248 ' | Forks | |\n' +
04:27:41.248 ' | Projects | |\n' +
04:27:41.248 '\n' +
04:27:41.248 '\n' +
04:27:41.248 'The fork is a personal copy of the repo which is already present or uploaded in GitHub by a different user. Once you fork and make changes to the repository the changes will happen to your forked repo, not the real one.\n' +
04:27:41.248 '\n' +
04:27:41.248 '### Watch the video Tutorial\n' +
04:27:41.248 '<iframe width="853" height="480" src="https://www.youtube.com/embed/GrTV59Y84S8?list=PLrLTYhoDFx-kiuFiGQqVpYYZ56pIhUW63" title="How to start with GitHub in 2024 | Beginner's Guide" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>\n' +
04:27:41.248 '\n' +
04:27:41.249 '\n' +
04:27:41.249 '## Conclusion\n' +
04:27:41.249 '\n' +
04:27:41.249 'If you think this Github Tutorial starter kit for Beginner was useful to you, then don’t forget to share it with others. Till then, we will meet For uploading your project to your Github account, you need to install Git first. which we will discuss in detail in the next post.\n' +
04:27:41.249 '\x00',
04:27:41.249 position: 817,
04:27:41.249 line: 18,
04:27:41.249 column: 22
04:27:41.249 }
04:27:41.249 }
04:27:41.249 }
04:27:41.250 }
04:27:41.251 [INFO] Docusaurus version: 3.9.1
04:27:41.251 Node version: v22.20.0
04:27:41.272 Error: Command "npm run build" exited with 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hacktoberfest-accepted recode this is label for leaderboard under review Review under the maintainers or the admins

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants