website icon indicating copy to clipboard operation
website copied to clipboard

(FWE) "Getting started" landing page + learning pathway

Open ericwindmill opened this issue 8 months ago • 3 comments

In order to land FWE, we need to...

  • [ ] Create a landing page
  • [ ] Set up the side nav properly
  • [ ] Deprecate existing "fundamentals"

The landing page should include...

  • An introduction to the tutorial
  • Links to either of the possible starting points and explanations of why the reader would choose one or the other.
    • The first Dart lesson
    • The first Flutter lesson
  • Learning pathway links -- what to do, in what order, for a brand new dev:
    1. installation
    2. dart FWE
    3. Flutter FWE
    4. Watch "How Flutter works" series
    5. Architecture case study

Known TODOs

  • [ ] Create a page at docs.flutter.dev/learn
  • [ ] Redirect the marketing site page at flutter.dev/learn to this new page, and remove that page from the marketing site
  • [ ] To move all FWE lessons to /learn in the content repository
  • [ ] to update dart.dev pages to use /learn in the URL and in the repo organization (tracked here)
  • [ ] Point everything to this new page

Open questions

  • Design? After all this work, it'd be shame to not have the landing page look great. Perhaps we can re-use some of the assets from the existing learn page
  • Navigation? Are we going to add a "Learn" link to the top nav? What about the side nav?

Googlers, the source of truth is go/dash-onboarding-experience That doc contains the relevant changes needed on the Dart docs and across other mediums like YouTube and Codelabs.

ericwindmill avatar May 23 '25 21:05 ericwindmill

Hi @ericwindmill - Super excited about this landing soon! I am thinking that maybe this should be something that lives in the learn page itself perhaps? Especially since we have the list of all resources a developer would need as they get into using Flutter. That way, it becomes truly the canonical page to uplevel - rather than punching them out to a separate page?

Or maybe the separate page becomes where the list of all the FWE content is - but you "discover" it from the learn landing page?

abdallahshaban557 avatar Dec 01 '25 20:12 abdallahshaban557

Hi [@ericwindmill](https://github.com/ericwindmill) - Super excited about this landing soon! I am thinking that maybe this should be something that lives in the learn page itself perhaps? Especially since we have the list of all resources a developer would need as they get into using Flutter. That way, it becomes truly the canonical page to uplevel - rather than punching them out to a separate page?

Or maybe the separate page becomes where the list of all the FWE content is - but you "discover" it from the learn landing page?

I would prefer to make a new learn page on the docs site, and just remove/redirect the marketing site /learn to that new page. A few reasons:

  1. It's likely going to be iterated on, and its easier to update if its on the docs site.
  2. I very much dislike the existing learn page, because it has WAY too many suggestions.
  3. We need a landing page for the new tutorial either way

edit: To be clear, I think we should make the new page look fancy, and perhaps reuse the assets from the existing /learn page.

I have tried to write FWE in a way that, once it lands, we can totally forget the name "FWE". It's not a single tutorial, it's a collection of small tutorials. I'd like to transform /learn into the part of the site where our how-to style docs live.

This possible deprecation of the learn page has been discussed in the past, but never formally, and I think people support the idea. That said, now is the time formalize it and tell me why this idea is bad. @abdallahshaban557

ericwindmill avatar Dec 01 '25 20:12 ericwindmill

@ericwindmill - I am in favor of removing the learn page and just routing people to the new FWE pages you are creating. The current learn page doesn't give a clear path to learn Flutter as a new comer - I think we'd have much better luck in giving new devs a taste of Flutter with FWE. Especially if you are thinking of using the pieces that make sense in the docs.

It also feels more natural to have it in docs than in the marketing page. LMK how I can help here!

abdallahshaban557 avatar Dec 02 '25 19:12 abdallahshaban557