IndieWeb newsletter should treat pages edited from a redirect to actual content as new...
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The IndieWeb This Week newsletter’s "New Wiki Pages" section, e.g. 2020-01-31 New Wiki Pages should also include pages that are not literally new in MediaWiki terms, but were a redirect page, and during the week before the newsletter were edited to no longer redirect, and have their own content instead.
Currently in order to make a redirect page that’s been converted to a content page show up in the "New Wiki Pages" section, you have to delete the redirect page, and then recreate it with the new content. For example I did this today with the local first page. Ideally there would be no need to take that extra step of deleting the redirect page first.
Label: enhancement.
(Originally published at: https://tantek.com/2020/036/b1/indieweb-redirect-to-content-new)
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 at the code that assembles the newsletter’s “New Wiki Pages” section and inspect how MediaWiki page changes are identified. Verify the behavior against the local first example and define done as including pages changed from redirects to content during the relevant week, without requiring deletion and recreation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- content
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100