Closed
Conversation
- Marketing site (sixtyfour.ai): 57/120 (Needs Work) - Docs site (docs.sixtyfour.ai): 67/120 (Needs Work) - Identified critical issues: poor developer positioning, missing SDKs, unclear pricing - Documented quick wins and strategic opportunities - Created prioritized action plan with expected score improvements Co-authored-by: John Vajda <jpvajda@users.noreply.github.com>
|
Cursor Agent can help with this pull request. Just |
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
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.
Add a comprehensive Built For Dev score report for SixtyFour's marketing and docs sites to identify developer experience issues and propose an action plan.
The report highlights that the marketing site (57/120) is poorly positioned for developers compared to the docs site (67/120), creating a "broken funnel" where developers bounce before discovering the API. It details critical issues like missing code examples on the homepage, unclear pricing, and lack of SDKs, offering prioritized quick wins and a 3-phase action plan to improve developer adoption.
Linear Issue: FDPM-23