Expandable FAQ Section with FAQ Schema for Blog Posts

[SourabhEstuary]

Please add an optional expandable FAQ section at the end of our blogs, similar to the one shown in the attached screenshot. This section should only be visible when we have specific FAQs to include; otherwise, it should be hidden entirely.

Also, please ensure that once this section is added, the FAQ schema is implemented for it.

Let me know if you need any further details. Thank you!

[travjenkins]

@danthelion - we need to work out a lot more details / discussion.

What content goes in here?
What does the shape of the content look like?
Do all blogs have this content?
How are they tied to blogs?

We need to work out way more details on this.

[SourabhEstuary]

What content goes here?
This section is optional. We'll add 3-4 FAQs at the end of certain blogs to provide additional helpful information. For reference, see an example of currently added FAQs: - https://estuary.dev/netsuite-to-sql-server/ .

What should the content look like?
Each FAQ answer will typically be around 50 words, though some may extend to about 70-75 words.

Will all blogs have FAQs?
No, FAQs are for some priority blogs, primarily for source-to-destination blogs. If there’s no specific FAQ content, this section should remain hidden. This should be managed by strapi.

Where will the FAQs appear in the blog?
FAQs will be placed at the end of the blog, just above our final CTA section.

*A dedicated FAQ section can improve the reader experience and make the content more helpful. It also increases the chances of boosting SEO performance.

[Brenosalv]

We can add optional FAQ fields to the blog posts in Strapi and reuse the FAQ UI from the pricing page.

[travjenkins]

Are you wanting to share these or will they always be fully unique for the blog post?

[danthelion]

They'll be unique to the blog on every occasion

[travjenkins]

Okay cool - yeah just having an array of these on blogs sounds good.