Skip to content

Conversation

MantisClone
Copy link
Member

No description provided.

…ructure

- Restructure navigation from 3 basic sections to 6 comprehensive sections:
  * Welcome (enhanced landing page)
  * Use Cases (5 primary scenarios)
  * API Features (conceptual documentation)
  * API Reference (technical reference)
  * Resources (cross-cutting support)
  * API Setup & SDK Legacy (setup and migration)

- Enhanced landing page with 'What is a Payment Request?' explanation,
  interactive demo placeholder, and developer journey guidance

- Created 5 use case pages (invoicing, payouts, payroll, checkout, subscriptions)
  each with consistent structure: quickstart, EasyInvoice integration,
  implementation options, and API features links

- Added comprehensive API features documentation following DRY principle:
  payment types, advanced features, and integration patterns

- Established API reference structure with authentication and webhooks

- Added resources for supported chains/currencies, smart contracts, and community

- Included setup guide and SDK migration documentation

This foundational structure enables use case-driven navigation per proposal
and provides comprehensive placeholder content ready for GitBook migration.
* Estimated defaults: page header = 700, section headers = 600
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant