feat(website): add recent blogs section to homepage

[Aman123lug]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

This PR adds a "Latest Blogs" section to the Docusaurus homepage that dynamically displays the 3 most recent blog posts. This helps visitors quickly discover recent content and encourages engagement with the blog.

Changes:

• Add recentBlogs plugin to expose recent blog posts via global data using the allContentLoaded lifecycle hook
• Add RecentBlogs component with responsive blog post cards
• Integrate component on homepage between Features and Tweets sections

Features:

• Automatically updates at build time (no manual editing needed)
• i18n support with <Translate> component
• Responsive grid layout (3 columns on desktop)
• Shows title, date, description, and author avatars

Test Plan

1. yarn install
2. yarn workspace website start
3. Visit homepage at http://localhost:3000
4. Verify the "Latest Blogs" section appears between Features and Tweets
5. Verify it shows 3 blog post cards with correct titles, dates, and descriptions
6. Click through to verify links work correctly

Test links

Deploy preview: https://deploy-preview-11665--docusaurus-2.netlify.app/

• Homepage with new Recent Blogs section: https://deploy-preview-11665--docusaurus-2.netlify.app/

Related issues/PRs

N/A - This is a new feature contribution.

[meta-cla]

Hi @Aman123lug!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	5226efe
🔍 Latest deploy log	https://app.netlify.com/projects/docusaurus-2/deploys/69692a8347935d000854033c
😎 Deploy Preview	https://deploy-preview-11665--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[miaromero6401-bot]

El jue., 15 de enero de 2026 2:08 p. m., meta-cla[bot] < ***@***.***> escribió:

…

*meta-cla[bot]* left a comment (facebook/docusaurus#11665) <#11665 (comment)> Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! — Reply to this email directly, view it on GitHub <#11665 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BWTJKI4QFVQDFRAFO3RMTAL4G7XVNAVCNFSM6AAAAACR2KFW6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONJWGY2TQOJZGM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[slorber]

This technically works, and could serve as a nice "dogfood demo", but you implemented a feature that we did not request, and I don't think this improves our landing page. Also, it looks like you used AI to do so, and we require you to disclose that. For these reasons, I'm closing the PR.

Please ask us before implementing feature to be sure we want them in the first place, and please disclose any AI usage in your next PRs. It's preferable that you first submit non-AI PRs to gain our trust.