Skip to content

docs(readme): rebuild the landing page (FR-26112) - #147

Closed
dianaKhortiuk-frontegg wants to merge 1 commit into
masterfrom
docs/readme-landing
Closed

dianaKhortiuk-frontegg wants to merge 1 commit into
masterfrom
docs/readme-landing

Conversation

@dianaKhortiuk-frontegg

Copy link
Copy Markdown
Collaborator

The landing page had no install step and no code

README.md is a symlink to docs/README.md, so one file serves both the GitHub landing page and flutter-guide.frontegg.com. It gave an intro, a list of documentation links, and stopped — no requirements, no pub add, no snippet.

Now reads: what it is → install → quick start → documentation → examples → support. Same structure as iOS#316, Android#280 and RN#125, with Flutter's own content.

  • Install — dart pub add and the pubspec.yaml form, with iOS 14+ / Android API 26+ stated inline.
  • Quick start — redirect URLs per platform, a pointer to the native setup, then FronteggProvider and context.frontegg.
  • Documentation — the five guides as a table saying what each covers.
  • Example apps — all three, named.

The snippets are taken from this repo's own usage.md and the hosted example's main.dart, so they match code that actually runs here.

Step 2 defers to the Get Started guide rather than reproducing the Gradle and plist setup — it is the one genuinely per-platform part, and duplicating it would create two copies to keep in sync.

🤖 Generated with Claude Code

Applies the structure now used by the iOS, Android and React Native SDKs:
product header with a live pub.dev and licence badge, a capability summary,
then install, quick start, documentation, examples and support.

The page previously listed documentation links and stopped, so a reader never
saw the platform requirements, the pub command or a working snippet without
leaving for the guide site.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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