-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Update Getting Started (How to change the project and why?) #7708
Conversation
@SAplayer Could you submit a version without all the whitespace diffs? I assume we want the Getting Started HTML code to be consistent with the indentation you'd get if the code was written in Brackets out of the box... |
on and continue. You've now successfully changed your project! | ||
It's always good to set the right project, because some cool features of Brackets are depending on | ||
the right location selected. In other words, things like Live Preview and Quick Edit aren't that great | ||
with the wrong project scope set! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CC @njx for potential wordsmithing here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay. Here's a suggested rewording (also note the added heading and the paragraph/samp structure):
<h3>Projects in Brackets</h3>
<p>In order to edit your own code using Brackets, you can just open the folder containing your files. Brackets treats the currently open folder as a "project"; features like code hints, Live Preview and Quick Edit only use files within the currently open folder.</p>
<samp>Once you're ready to get out of this sample project and edit your own code, you can use the dropdown in the sidebar to switch folders. Right now, the dropdown says "Getting Started" - that's the folder containing the file you're looking at right now. Click on the dropdown and choose "Open Folder..." to open your own folder. You can also use the dropdown later to switch back to folders you've opened previously, including this sample project.</samp>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I made those changes.
@peterflynn Whitespace corrected (even while you normally don't see the whitespace out of the box). |
Please take a look at lines 37 and 38. Are the two newlines intended? |
Adding "triage complete" label. |
<h3>Projects in Brackets</h3> | ||
<p> | ||
In order to edit your own code using Brackets, you can just open the folder containing your files. | ||
Brackets treats the currently open folder as a "project"; features like Code Hints, Live Preview and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@njx I guess it should be Code Hints
instead of code hints
(that's what you wrote), right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was originally thinking that "code hints" isn't a specific feature name (as opposed to Live Preview and Quick Edit), but that might just be a distinction in my head. In any case, it probably looks better to capitalize it as you did.
@SAplayer Looks good - just added a note on the ellipses. |
Merging (finally :)) - thanks! |
Update Getting Started (How to change the project and why?)
@peterflynn and I talked about this on gitter.