Repository navigation
Conversation
✅ Deploy Preview for flowfuse-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
2 of 5 tasks
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.
InlineMarkdown renders links to CTA destinations through CtaLink, with a position per caller (faq in Faq).
Yndira-E
force-pushed
the
feat/unify-faq
branch
from
October 5, 2026 11:10
e6fa737 to
e1d2974
Compare
*a **b** c* rendered as three separate em spans, losing the bold. The HTML-string renderer produced <em>a <strong>b</strong> c</em>.
Both repeated ctaDestinationKey + ctaQuery, and InlineMarkdown called ctaDestinationKey twice per link on every render. InlineMarkdown now resolves each link once.
Answers are markdown now, so defineQuestion was publishing [Contact Us](/contact-us/) and blank lines in the JSON-LD. faqAnswerText() keeps link labels and drops the markup, and every page passes it.
An unknown component renders nothing and the build still passes, so a page still using the old name would ship an empty FAQ.
Faq renders an answer's text through Vue, so an answer written the old way, with <a> or <br> tags, shows the tags as literal text.
The escaping happens in Vue's interpolation now, not in Faq.
- The HTML check skips content/docs and content/blueprints, which are synced from other repositories and not rendered by Faq. - A frontmatter js-yaml can't parse fails with the file's path. - The defineQuestion check reads each call's whole argument, so a call over several lines passes and faqAnswerText on the question fails. - As in CommonMark, an asterisk with a space on its inner side is not emphasis, so "2 * 3 * 4" stays text.
3 of 4 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 the site now renders through
Faq(renamed fromBlogFaq), including/pricing/and/integrations/opcua/, which had their own markup and raw HTML answers.v-html. Output is unchanged for all existing answers.CtaLink, so they're tracked like other inline links (position: faqin FAQs). The link matching is shared withProseAthroughctaLink().faqAnswerText(), instead of the markdown source.InlineMarkdowncomponent.<BlogFaq>, on HTML in a FAQ answer, and on adefineQuestionwithoutfaqAnswerText().Visual change: the pricing FAQ now looks like every other FAQ instead of a Nuxt UI accordion, and the OPC UA FAQ gains 16px above and below.
Heads-up: #5811 and #5747 add
<BlogFaq>usages. Whichever merges second needs to rename them to<Faq>; the new test will catch it.Follow-up:
Faq, so pages don't have to remember to add it (/integrations/opcua/has none today).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.