Make article-specific yaml files for redirects and tags

[cl8n]

Current:

- Article_A/
- Article_B/
...
- redirect.yaml

Proposed:

- Article_with_redirects_or_tags/
    - properties.yaml
- Article_with_no_redirects_or_tags/
...

properties.yaml would contain two sequences, one for redirects and one for tags

needs a web implementation, of course. I think this would be easier to manage, since redirects and tags are not language-specific, and it's kinda annoying to remember about updating redirect.yaml every time an article is added/deleted/moved

[sr229]

I don't think this kind of nesting is preferrable, here's a better one:

Article_Link/
Article_Link/
    | _ redirect.yaml
paths.yaml

Where paths.yaml can be:

paths:
    - 'Article_1/'
    - 'Article_2/'

[cl8n]

what is the purpose of paths.yaml in your suggestion?

[cl8n]

does anyone else have input on this

[Joehuu]

I agree, since it's hard to keep track of articles that have redirects/tags.

[Walavouchey]

my input on this is that it's easier to maintain one file than 900