[Bug] RelatedPostsFactory throws runtime error / fails when blog posts have empty or null tags

[suryaff733]

🐛 Bug Description

When a blog post's frontmatter has an empty tags: field (or tags: null), RelatedPostsFactory fails with runtime errors and prevents the "Related Posts" section from properly calculating recommendations.

There are two failure modes:

1. Current post has no tags: RelatedPostsFactory.getPosts() logs "RelatedPostsFactory: Tags not provided, use setTags()." and returns an empty array [], completely skipping category-based recommendations.
2. Candidate post in the pool has no tags: addTagsPoints() in src/components/Related-Posts/relatedPostsFactory.js:69 invokes .forEach() directly on post.frontmatter.tags with no null check, throwing TypeError: Cannot read properties of null (reading 'forEach').

---

📍 Location of Bug

• File: src/components/Related-Posts/relatedPostsFactory.js
• Lines: 34–37 and 65–74

const addTagsPoints = (post, tags) => {
  const tagPoint = 1;
  const slug = getSlug(post);

  // 💥 Crashes when post.frontmatter.tags is null
  post.frontmatter.tags.forEach((tag) => {
    if (includes(tags, tag)) {
      identityMap[slug].points += tagPoint;
    }
  });
};

[Bryandero98]

Hi! I'd like to work on this issue.

• I've read CONTRIBUTING.md, including the DCO sign-off requirement.
• I have a working local dev environment (cloned with --depth=1 as recommended) and have traced the bug to the exact lines cited above.
• Intended approach: addTagsPoints() will guard post.frontmatter.tags (default to [] when null/undefined) before calling .forEach(), fixing the crash for any candidate post lacking tags. I'll also relax the early-return in getPosts() so that a current post without tags still gets category-based recommendations instead of an empty array, normalizing this.tags the same way. Both changes stay scoped to relatedPostsFactory.js, no other files touched.

Could you assign this to me (@Bryandero98)? Thanks!