Closes #468
Signed-off-by: IXVG47QZ
IXVG47QZ/website:faq-json into main Closes #468
Signed-off-by: IXVG47QZ
Signed-off-by: IXVG47QZ <jako_accomm@simplelogin.com>
I wish it was possible to just do:
{%- for faq_page in terms.pages -%}
but it doesn't seem to work.
I'm not sure that this is the right use (at least according to the guidelines Google gives for this):
Valid use cases: Both the question and answer are visible on the page.
Invalid use cases: The user can't find the FAQ content on the page at all.
In our case, the users can't actually read the FAQ answers on that page but need to click through to the corresponding pages
In one sense it doesn't matter to follow Google's requirements, because this won't show up in the rich results anyway (it's restricted to health care and government), but on the other hand if Google says it, it can be seen as a best practice.
I'm thinking for AI readability, it would be good to have all the FAQ schema on one page, but we can also have individual FAQ schema on each FAQ page. That would improve the likelihood that ChatGPT and the like will find the right information.
I'd say let's put them on the individual pages then, that way we also don't overload the index/list page!
Signed-off-by: IXVG47QZ <jako_accomm@simplelogin.com>
Done. Should be good to go!
Very nice, tested locally as well 👍
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?