Improve SDK developer onboarding and integration flow

[aguilar1x]

Context

Developers should be able to go from discovering the SDK to rendering a working widget in minutes. This issue focuses on the developer experience needed to make adoption frictionless: clear onboarding, reliable API discovery, and a way to test the widget before integrating it.

Scope

• Build a developer site using Nextra/Next.js.
• Add a quickstart that gets a developer to a working integration quickly.
• Generate the API reference directly from the SDK types so it stays aligned with the code.
• Add an interactive playground where developers can configure the widget, preview it live using pk_test, and copy the generated integration snippet.

Acceptance criteria

• A developer can follow the quickstart and render the widget without additional context.
• The copied snippet works when pasted as-is.
• The API reference is regenerated in CI whenever SDK types change.
• The playground renders the widget in test mode and outputs a valid snippet.

Dependencies

Depends on #13, #15, and #19.

[Macnelson9]

Hi team, I'd like to take on this issue.

I specialize in Rust development, smart contract engineering, and frontend development with Next.js, React, and TypeScript. My experience allows me to bridge on-chain functionality with intuitive user experiences, ensuring both technical correctness and usability.

I'll follow the existing codebase conventions, communicate progress clearly, and deliver a high-quality solution within the expected timeline.

Thank you for your consideration.

[josueazc]

Hi team,

I'd like to work on this issue.

I have experience building applications with React, Next.js, and TypeScript, including developer-facing tools, documentation sites, reusable components, and interactive web interfaces. I've also worked with API integrations, component libraries, and maintaining clean documentation for projects.

For this task, I can:

Set up and structure the documentation site using Nextra and Next.js.
Create a clear quickstart guide and developer onboarding flow.
Generate and maintain API reference documentation directly from TypeScript types.
Build the interactive playground that renders the widget live and generates copy-paste ready snippets.
Configure CI workflows to automatically regenerate documentation when SDK types change.
Ensure the generated snippet works as-is and matches the latest SDK API.

I understand the importance of developer experience and documentation quality for SDK adoption, and I'll focus on making the docs intuitive, maintainable, and easy to extend as the SDK evolves.

Looking forward to contributing. Thanks for your consideration!

[Justnevo]

Hell team pacto, I will like to work on this issue and I promise to deliver within the expected timeline.

[Fabiana1504]

Hi! I’d like to work on this because I have web development experience and enjoy building clear docs. I would create a simple documentation site with an interactive playground that is easy to use.

[KevinLatino]

Hi! I'm Kevin Latino, a Software Engineer with 3 years of professional experience building developer-focused products and web applications.

I'd love to work on this issue. I have experience improving developer experience, building frontend applications, writing technical documentation, and creating intuitive interfaces that make integrations simple and easy to adopt. I'd be happy to take ownership of this implementation.

[grantfox-oss]

🦊 GrantFox — @KevinLatino has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #20)
2. Your PR will be reviewed by the PACTO-LAT maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@KevinLatino's PR #33 was approved and merged by @Villarley.

🏆 @KevinLatino: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (48 total points). Track your full progress on GrantFox.

👏 Great work, @KevinLatino! Keep contributing to PACTO-LAT.