-
-
Notifications
You must be signed in to change notification settings - Fork 17
feat: structured data for faq #545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
therobrob
commented
Dec 26, 2025
- refactored expander-code
- split up faq markdown
- added faq in structured data
|
Hi there! 👋 Thank you for your contribution to the FIP Guide! 🚀 Checklist before merging:
|
✅ Deploy Preview for fipguide ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| "name": "{{ $item.Title }}", | ||
| "acceptedAnswer": { | ||
| "@type": "Answer", | ||
| "text": {{ $item.Content | jsonify | safeHTML }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line doesn't convince me, because the output is in the wrong format yet.
|
|
||
| {{ $faq := where $gi.Pages ".File.Dir" "==" "generalinformation/faq/" }} | ||
|
|
||
| {{ range sort $faq ".File.BaseFileName" }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the sorting order relevant to us? If so, we could use the weight-property in the preface to force a specific order.
Maybe we should rename the md-Files to the question-names?
| "title" $title | ||
| "type" $type | ||
| "name" $name | ||
| "content" .Inner |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
didn’t work with capital letters..