Conversation
faq-answer.mjs now parses answers into nodes instead of HTML strings, and InlineMarkdown renders them, so no answer needs v-html. Pricing and the OPC UA page use BlogFaq instead of their own FAQ markup, with answers moved from raw HTML to the markdown subset.
It renders every FAQ on the site, not just blog posts.
parseInline is shared by InlineMarkdown and FAQ answers, so it gets its own module; faq-answer.mjs keeps only the paragraph and list handling.
✅ Deploy Preview for flowfuse-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
5 tasks
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Every FAQ on Nuxt pages now renders through
Faq(renamed fromBlogFaq), including/pricing/and/integrations/opcua/, which had their own markup and raw HTML answers. This prepares FAQ links to be tracked like the rest of the site's CTA links, the follow-up to #5857 that comes in the next PR.v-htmland a link can become a component. Output is unchanged for all existing answers.inline-markdown.mjs. The industry Applications copy and the remote device management copy render through the sameInlineMarkdowncomponent.Heads-up: #5811, #5793 and #5747 add
<BlogFaq>usages. They share no files with this PR, so no merge conflict will flag it: whichever merges second needs to rename them to<Faq>, or that FAQ renders empty while the build still passes.Follow-ups:
Faq, so pages don't have to remember to add it (/integrations/opcua/has none today) and answers go out as plain text instead of markdown. On pricing, this PR swaps HTML, which Google accepts, for markdown. Impact is low, since Google only shows FAQ rich results for government and health sites.Related Issue(s)
Checklist
Note
Render all FAQ sections through shared
FaqcomponentBlogFaqtoFaqand routes every FAQ section through this single component, including the custom accordions on the OPC UA and pricing pages.v-htmlstring injection with structured parsing in faq-answer.mjs and inline-markdown.mjs, rendering typed paragraph and list nodes through InlineMarkdown.vue.v-htmlin non-FAQ copy withInlineMarkdownin Applications.vue and remote-device-management.vue.Macroscope summarized e6fa737.