Fixed the broken blogs

[Adez017]

Description

Now, the content in the blog is well structured and not mixed

Fixes #382

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

Updated blogs

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/devices
• My changes do not generate new console warnings or errors , I ran npm run build and attached scrrenshot in this PR.
• This is already assigned Issue to me, not an unassigned issue.

[vercel]

@Adez017 is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

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! 😊

[Adez017]

Hi @sanjay-kv , i had made the changes take a look

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
recode-website	Error			Aug 21, 2025 8:38am

[Adez017]

vercel its failing , but locally the build got sucessful

[Adez017]

if there is any version mismatch let me , we have to resolve it so that this problem not occur for future PRs

[sanjay-kv]

yes , its bit tricky , i will figure it out.

[sanjay-kv]

[22:14:35.388] Running build in Washington, D.C., USA (East) – iad1 [22:14:35.388] Build machine configuration: 4 cores, 8 GB [22:14:35.414] Cloning github.com/recodehive/recode-website (Branch: main, Commit: b4b98b5) [22:14:36.930] Cloning completed: 1.516s [22:14:39.608] Restored build cache from previous deployment (9ibxupYesNhuSokpZeXsMboeFktY) [22:14:46.160] Running "vercel build" [22:14:46.655] Vercel CLI 46.0.2 [22:14:47.335] Warning: Detected "engines": { "node": ">=18.0" } in your package.jsonthat will automatically upgrade when a new major Node.js Version is released. Learn More: http://vercel.link/node-version [22:14:47.340] Installing dependencies... [22:14:50.205] [22:14:50.206] up to date in 3s [22:14:50.206] [22:14:50.206] 422 packages are looking for funding [22:14:50.206] runnpm fund for details [22:14:50.248] Running "npm run build" [22:14:50.362] [22:14:50.363] > [email protected] build [22:14:50.363] > docusaurus build [22:14:50.363] [22:14:53.408] [INFO] [en] Creating an optimized production build... [22:14:53.976] [WARNING] Docusaurus found blog posts without truncation markers: [22:14:53.976] - "blog/Spark-Architecture/index.md" [22:14:53.976] - "blog/git-coding-agent/index.md" [22:14:53.977] - "blog/ux-ui-design-job/index.md" [22:14:53.977] - "blog/ux-designers-ai/index.md" [22:14:53.977] - "blog/streamline-ux-ui/index.md" [22:14:53.977] - "blog/google-deepmind/index.md" [22:14:53.977] - "blog/google-backlinks/index.md" [22:14:53.977] [22:14:53.977] We recommend using truncation markers (or{/* truncate */}) in blog posts to create shorter previews on blog paginated lists. [22:14:53.978] Tip: turn this security off with the onUntruncatedBlogPosts: 'ignore' blog plugin option. [22:14:54.539] [info] [webpackbar] Compiling Client [22:14:54.559] [info] [webpackbar] Compiling Server [22:15:04.461] [success] [webpackbar] Server: Compiled successfully in 9.90s [22:15:17.341] [success] [webpackbar] Client: Compiled successfully in 22.80s [22:15:23.508] [22:15:23.510] [ERROR] Error: Unable to build website for locale en. [22:15:23.510] at tryToBuildLocale (/vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:78:15) [22:15:23.510] at async /vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:34:9 [22:15:23.510] ... 4 lines matching cause stack trace ... [22:15:23.510] at async file:///vercel/path0/node_modules/@docusaurus/core/bin/docusaurus.mjs:44:3 { [22:15:23.510] [cause]: Error: Docusaurus found broken links! [22:15:23.510] [22:15:23.510] Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist. [22:15:23.511] Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass. [22:15:23.511] [22:15:23.511] Exhaustive list of all broken links found: [22:15:23.511] - Broken link on source page path = /blogs/: [22:15:23.511] -> linking to /blog/spark-architecture [22:15:23.511] - Broken link on source page path = /: [22:15:23.511] -> linking to blog/spark-architecture (resolved as: /blog/spark-architecture) [22:15:23.511] [22:15:23.511] at throwError (/vercel/path0/node_modules/@docusaurus/logger/lib/logger.js:80:11) [22:15:23.511] at reportBrokenLinks (/vercel/path0/node_modules/@docusaurus/core/lib/server/brokenLinks.js:250:47) [22:15:23.511] at handleBrokenLinks (/vercel/path0/node_modules/@docusaurus/core/lib/server/brokenLinks.js:282:5) [22:15:23.511] at executeBrokenLinksCheck (/vercel/path0/node_modules/@docusaurus/core/lib/commands/build/buildLocale.js:118:47) [22:15:23.511] at /vercel/path0/node_modules/@docusaurus/core/lib/commands/build/buildLocale.js:93:67 [22:15:23.511] at Object.async (/vercel/path0/node_modules/@docusaurus/logger/lib/perfLogger.js:42:47) [22:15:23.512] at buildLocale (/vercel/path0/node_modules/@docusaurus/core/lib/commands/build/buildLocale.js:93:31) [22:15:23.512] at async runBuildLocaleTask (/vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:93:5) [22:15:23.512] at async /vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:74:13 [22:15:23.512] at async tryToBuildLocale (/vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:70:9) [22:15:23.512] at async /vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:34:9 [22:15:23.512] at async mapAsyncSequential (/vercel/path0/node_modules/@docusaurus/utils/lib/jsUtils.js:21:24) [22:15:23.512] at async Command.build (/vercel/path0/node_modules/@docusaurus/core/lib/commands/build/build.js:33:5) [22:15:23.512] at async Promise.all (index 0) [22:15:23.512] at async runCLI (/vercel/path0/node_modules/@docusaurus/core/lib/commands/cli.js:56:5) [22:15:23.513] at async file:///vercel/path0/node_modules/@docusaurus/core/bin/docusaurus.mjs:44:3 [22:15:23.513] } [22:15:23.513] [INFO] Docusaurus version: 3.8.1 [22:15:23.513] Node version: v22.18.0 [22:15:23.591] Error: Command "npm run build" exited with 1

This is the log from vercel

[Adez017]

Hi @sanjay-kv , i think someone had remove it completely from the website :

if you are open , i can now cleanly create a new PR for the same issue #369

[Adez017]

does this means i can create a new PR ? @sanjay-kv