Blogpost Path Uniqueness

Open
#213 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
content, web-dev

Research direction

Start by locating the blog post path-generation entry point and the metadata handling for titles and dates. Verify how existing blog URLs are produced, then confirm that combining the date with the title gives distinct paths for posts with duplicate titles without breaking the expected blog URL format.

Written by the indexing model from the issue text.

Description

enhancement Good First Issue help wanted

Problem

Currently, the title of a blog post will become it's path on the website, for instance a blog post with metadata title "My first Terasology blog!" will be served at /blog/my-first-terasology-blog. This means, that the title needs to be unique, which doesn't really make sense. For instance, if somebody today would write a blog post and title it the same as a blog post written 2 years ago, we would have a conflict there which might not be resolved deterministically.

Proposal

Use the date in combination with the title to avoid the requirement on titles to be unique.

Dominant language
JavaScript
Stars
7
Forks
17
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MovingBlocks/movingblocks.github.com

All issues in MovingBlocks/movingblocks.github.com

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.