life-itself / life-itself/markdown-to-wordpress
(Blog) Content migration (individual items)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
For a blog post, migrate it ...
How we handle certain things?
- [ ] How will we handle authors
- [ ] How do we handle description
- [ ] How do we handle feature image
- [ ] How will we handle footnotes?
- [ ] How will we handle existing Flowershow redirects - see `_redirects`
- [ ] How will we do redirects for new content? (for now at least we want a dictionary of old path and new path)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the migration checklist in the issue and review the existing `_redirects` file mentioned there. Define how authors, descriptions, feature images, footnotes, and old and new paths are represented. The work is done when these cases have an agreed migration and redirect approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, markdown, wordpress
- Domain
- content, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100