Reworked getting started experience#800
Reworked getting started experience#800mit-mit merged 34 commits intoflutter:masterfrom mit-mit:getting-started-beta
Conversation
|
OK, this is ready for review now! As discussed in email I keep everything setup as-is today to minimize risk. I will focus on the setup piece for beta 2. |
|
Just to be clear: The present PR is the subset I am hoping we can land this week so it's ready before first beta. |
|
Staging site: https://flutter-website-staging.firebaseapp.com/ |
| a new window. For example: | ||
|
|
||
| 1. Determine the directory where you cloned Flutter's git repo. You will | ||
| 1. Determine the directory where where you placed the Flutter SDK. You will |
| in the code window and select `Reformat with Dart style`. You can add a keyboard | ||
| shortcut to this in Keymap section of IntelliJ Preferences. | ||
|
|
||
| ### Automatically formatting code in VS Code |
There was a problem hiding this comment.
visual studio code , or vs code ?
There was a problem hiding this comment.
Well, color me wrong. I thought it was "VSCode", but I checked and it's "VS Code". I have to change my docs. :)
There was a problem hiding this comment.
Microsoft uses both 'Visual Studio Code' and 'VC Code'. I personally much prefer the latter as it's less likely to cause confusion with "big" Visual Studio.
|
|
||
| ### Automatically formatting code in VS Code | ||
|
|
||
| Automatic formatting of code is supported in Visual Studio Code if you |
There was a problem hiding this comment.
for future: try phrasing like "Install the Dart Code plugin to automatically format your Dart code."
|
I love the new suggested section titles from Filip, PR and staging updated to those! As for the overview and exit pages, see email I sent |
| <li><a href="/getting-started/">Create and run your first app</a></li> | ||
| <li><a href="/ide-setup/">Setting up the IDE</a></li> | ||
| <li><a href="/bootstrap-into-dart/">Bootstrap into Dart</a></li> | ||
| <li><a href="/get-started/">1: Overview</a></li> |
There was a problem hiding this comment.
I still think this should go. /get-started/ as a destination should stay (so that we can't send people to a place "of no escape"), but shouldn't be linked from sidenav. It's a very underwhelming destination page.
| <li><a href="/ide-setup/">Setting up the IDE</a></li> | ||
| <li><a href="/bootstrap-into-dart/">Bootstrap into Dart</a></li> | ||
| <li><a href="/get-started/">1: Overview</a></li> | ||
| <li><a href="/get-started/install/">2: Install Flutter</a></li> |
There was a problem hiding this comment.
Remove 'Flutter'. It's implicit.
| <li><a href="/bootstrap-into-dart/">Bootstrap into Dart</a></li> | ||
| <li><a href="/get-started/">1: Overview</a></li> | ||
| <li><a href="/get-started/install/">2: Install Flutter</a></li> | ||
| <li><a href="/get-started/editor-configuration/">3: Editor configuration</a></li> |
There was a problem hiding this comment.
"Configure editor". It's weird to have a noun when other steps are verbs. Verbs are better.
| <li><a href="/get-started/install/">2: Install Flutter</a></li> | ||
| <li><a href="/get-started/editor-configuration/">3: Editor configuration</a></li> | ||
| <li><a href="/get-started/test-drive/">4: Test drive</a></li> | ||
| <li><a href="/get-started/codelab/">5: Core concepts codelab</a></li> |
There was a problem hiding this comment.
"Write your first Flutter app". I believe it's much more appealing than "Core concepts codelab", and it's a verb.
| <li><a href="/get-started/editor-configuration/">3: Editor configuration</a></li> | ||
| <li><a href="/get-started/test-drive/">4: Test drive</a></li> | ||
| <li><a href="/get-started/codelab/">5: Core concepts codelab</a></li> | ||
| <li><a href="/get-started/learn-more/">6: Learn more</a></li> |
There was a problem hiding this comment.
I think we should lose this from the sidenav. Only link it from the end of the codelab.
For independent "learn more", we'll have flutter.io/docs
There was a problem hiding this comment.
I'm going to keep this for now, havn't fully understood how /docs plays into this.
| "type": 301 | ||
| }, | ||
| { | ||
| "source": "/setup-ide", |
There was a problem hiding this comment.
This page doesn't exist. You probably meant https://flutter.io/ide-setup/.
| @@ -0,0 +1,85 @@ | |||
| --- | |||
| layout: page | |||
| title: "Get Started: Editor Configuration" | |||
| @@ -0,0 +1,174 @@ | |||
| --- | |||
| layout: page | |||
| title: "Get Started: Test Drive an App" | |||
There was a problem hiding this comment.
Not sure if we want "an App" there. You're test driving the tooling here, the SDK.
There was a problem hiding this comment.
Changed to just Test Drive
| @@ -0,0 +1,26 @@ | |||
| --- | |||
There was a problem hiding this comment.
FYI, much of this work is duplicated in the new flutter.io/docs page (#817).
If you want, we could just link to that, and set up Google Analytics to track the funnel strictly (only people coming from codelab to the docs page count to the funnel's last step).
There was a problem hiding this comment.
I have not heard of that page before now (and don't see it staged anywhere), so hard for me to comment on that. The goal of this last learn more step is not to offer an list of all docs; it's to offer a short, opinionated list of likely next steps.
| title: Flutter installation & setup | ||
| permalink: /setup/ | ||
| title: "Get Started: Install Flutter" | ||
| permalink: /get-started/install/ |
There was a problem hiding this comment.
Can we add a link to test-drive at the end of this file as well? I know in theory people will go to setup-<platform> and continue to test-drive from there, but I think there'll inevitably be people who will expect a "next step" link here as well.
| Install the `Dart-Code` plugin (see [Editor setup](/get-started/editor/) | ||
| to enable automatic formatting of code in VS Code. | ||
|
|
||
| To automatically format the code in the current source code window, right-click |
There was a problem hiding this comment.
VS Code has some settings that are probably relevant here:
editor.formatOnSaveeditor.formatOnTypeeditor.formatOnPaste
All of these should work with Dart Code and I think we should encourage people to turn them on (they can do so globally, or just for Dart by using language-specific settings).
| 1. Specify a location to place the project, and press the blue OK button | ||
| 1. Wait for the project creation to continue, and the `main.dart` file to appear | ||
|
|
||
| The above command creates a Flutter project directory called `myapp` that contains a simple demo |
There was a problem hiding this comment.
This says myapp but a few lines up it says firstapp; I think they're supposed to be the same?
| The above command creates a Flutter project directory called `myapp` that contains a simple demo | ||
| app that uses [Material Components](https://material.io/guidelines/). | ||
|
|
||
| In the project directory, the code for your app is in `myapp/lib/main.dart`. |
There was a problem hiding this comment.
In some places in this text the paths are relative to the project (eg. lib/main.dart in the hot reload section) but this one includes the project folder; I think they should be consistent (I think without the project folder prefix may be best, but don't feel strongly).
|
|
||
| Automatic formatting of code is supported in IntelliJ if you have the | ||
| `Dart` plugin (see [IntelliJ setup](/ide-setup/)). | ||
| Install the the `Dart` plugin (see [Editor setup](/get-started/editor/) |
There was a problem hiding this comment.
This line has an unclosed paren
|
|
||
| ### Automatically formatting code in VS Code | ||
|
|
||
| Install the `Dart-Code` plugin (see [Editor setup](/get-started/editor/) |
There was a problem hiding this comment.
This one has unclosed paren too (also, it suggests editor page has a section in enabling automatic formatting, but I can't see it; though the next paragraph explains how to sort-of-automatically-but-not-on-type format).
|
|
||
| ### Install VS Code | ||
|
|
||
| * [VS Code](https://code.visualstudio.com/), version 1.19 or later. |
There was a problem hiding this comment.
Currently we need 1.20.1 but we also bump along with Code updates pretty frequently (since things in Code change quite frequently) so it might be best not to mention this (or encourage latest stable)? Unlike with some IDEs, I don't think updating Code is a big deal (it doesn't bring new versions of .NET, for ex like Visual Studio does) so users probably won't be reluctant to do it (I think it auto-updates by default on all platforms too?).
There was a problem hiding this comment.
I just updated it to 1.20.1. Would be nice if you could help update this when you take a new version dependency.
|
It'd be good if the selected editor persisted across pages (eg. when going from Configure Editor to Test Drive); maybe we should drop something in localStorage/cookie/whatever and then re-select on page loads (this way it could be carried around the whole site easily)? |
|
@DanTup: I don't think we have time to do that before merging. Can you open an issue? @mit-mit: Thanks, this looks really good. I actually liked the step numbers in the side navigation. That way it looked more like a flow and less like an assorted bunch of pages. @mjohnsullivan: Could you review, please? https://flutter-website-staging.firebaseapp.com/ |
|
@DanTup: Yeah, the Flutter team has opted to only have one Issues repo, and that's flutter/flutter. |
|
Makes sense! Done @ flutter/flutter#14888 |
|
FYI: I just ran this with #816 (checks inbound links) and found no issues. |
Re-work the getting started flow to:
Staging link: https://flutter-website-staging.firebaseapp.com/