Conflict between Tags/Keywords #2

New issue

Open

opened 2021-05-14 13:58:13 +02:00 by anybody · 0 comments

anybody commented

2021-05-14 13:58:13 +02:00

Member

Both Tags and Keywords can be used in Markdown yaml header, which can create inconsistencies, so better for one of the two to be recommended by design.

'Tags' works, also mysandpoingproject/tags returns a valid site
'Keywords' has the advantage that it appears in the rendered website (screenshot), but mysandpoingproject/keywords returns Error 404.

Perhaps one of the two can be forced/recommended by design, as the suggested way to go. Having both can only create incosistencies (screenshot 2) if actually the purpose is the same.

On an additional note, depending on the Sandpoint project, editors might or might not want the 'Keyword' to appear (as in Screenshot 1). It could be great it that was controlled, for example in config.toml (e.g. showKeywords: boolean)

Both Tags and Keywords can be used in Markdown yaml header, which can create inconsistencies, so better for one of the two to be recommended by design. - 'Tags' works, also `mysandpoingproject/tags` returns a valid site - 'Keywords' has the advantage that it appears in the rendered website (screenshot), but `mysandpoingproject/keywords` returns Error 404. Perhaps one of the two can be forced/recommended by design, as the suggested way to go. Having both can only create incosistencies (screenshot 2) if actually the purpose is the same. On an additional note, depending on the Sandpoint project, editors might or might not want the 'Keyword' to appear (as in Screenshot 1). It could be great it that was controlled, for example in config.toml (e.g. showKeywords: boolean)

2021-05-14 14.52.42 sandpoints .png

13 KiB

2021-05-14 14.53.35 sandpoints yaml header.png

3 KiB