Skip to content

docs: FAQ page components and data#6402

Merged
matthewelwell merged 4 commits intoFlagsmith:mainfrom
writechoiceorg:faq
Dec 17, 2025
Merged

docs: FAQ page components and data#6402
matthewelwell merged 4 commits intoFlagsmith:mainfrom
writechoiceorg:faq

Conversation

@TyroneOrrego
Copy link
Contributor

Thanks for submitting a PR! Please check the boxes below:

  • I have added information to docs/ if required so people know about the feature!
  • I have filled in the "Changes" section below?
  • I have filled in the "How did you test this code" section below?
  • I have used a Conventional Commit title for this Pull Request

Changes

FAQ section added.

How did you test this code?

Please describe.

@TyroneOrrego TyroneOrrego requested review from a team as code owners December 12, 2025 15:04
@TyroneOrrego TyroneOrrego requested review from matthewelwell and removed request for a team December 12, 2025 15:04
@vercel
Copy link

vercel bot commented Dec 12, 2025

@TyroneOrrego is attempting to deploy a commit to the Flagsmith Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions bot added the docs Documentation updates label Dec 12, 2025
@vercel
Copy link

vercel bot commented Dec 12, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
docs Ready Ready Preview, Comment Dec 16, 2025 2:21pm
2 Skipped Deployments
Project Deployment Review Updated (UTC)
flagsmith-frontend-preview Ignored Ignored Preview Dec 16, 2025 2:21pm
flagsmith-frontend-staging Ignored Ignored Preview Dec 16, 2025 2:21pm

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

@matthewelwell
Copy link
Contributor

@TyroneOrrego can you fix the broken link?

  Exhaustive list of all broken links found:
  - Broken link on source page path = /support/faq/infrastructure-api:
     -> linking to /edge-api/Overview

You should be able to replicate this error message yourself by running npm run build

@TyroneOrrego
Copy link
Contributor Author

@TyroneOrrego can you fix the broken link?

  Exhaustive list of all broken links found:
  - Broken link on source page path = /support/faq/infrastructure-api:
     -> linking to /edge-api/Overview

You should be able to replicate this error message yourself by running npm run build

Hi @matthewelwell I think I have already fixed it. I just committed the changes!

@matthewelwell
Copy link
Contributor

Hi @TyroneOrrego , thanks for fixing the linting issue.

From an aesthetic point of view, I think it looks fairly good, although it still feels a bit 'documentation' vs FAQ.

I'm also a little concerned about the manual expectations here - the 'counts' that appear in the tile view need to be updated manually if a new item is added. Could we look at something like this which might help us out?

If not, I vote for removing the counts for now.

@TyroneOrrego
Copy link
Contributor Author

Hi @matthewelwell, Thanks for the review!

I totally agree regarding the manual counts—that’s definitely a maintenance headache waiting to happen. I’m going to look into the solution you linked to see if I can get it working dynamically without too much overhead.

Regarding the "documentation" feel, I’ve made some styling changes to make the experience feel a bit lighter. I'll push a commit with those updates included shortly!

Cheers,

Tyrone

Copy link
Contributor

@matthewelwell matthewelwell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the aesthetic changes @TyroneOrrego , they look great.

Since we are waiting on these changes before deprecating our old support tool which hosts help.flagsmith.com I'm approving this with a view to merge it, and we can iterate on the code with regards to the changes suggested in my previous comment here in a separate PR.

@matthewelwell matthewelwell merged commit c309665 into Flagsmith:main Dec 17, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants