This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
reorganize Readme #4375
Merged
reorganize Readme #4375
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Moved paragraphs around so least technical (most user-oriented) is on top, then tech/contributing (hacker info) is near the end. This allowed to streamline the prose, but I tried to avoid changing the text as much as possible. Linked blog in welcome section (great for finding features; helps users decide if Brackets is for them). Used H4 vs **bold** for sub-headers.
(note to self; don't Push with only 4 hours of sleep)
|
(got feedback) |
ghost
assigned 
| @@ -1,8 +1,6 @@ | |||
| Welcome to Brackets! [](https://travis-ci.org/adobe/brackets) | |||
| ------------------- | |||
|
|
|||
| Installers for the latest build can be [downloaded here](http://download.brackets.io/). | |||
There was a problem hiding this comment.
We want to keep this at the top since it's important that people know how to get an installed build (it's not so easy for people to get started with Brackets just from the github repos, since they have to build the shell, etc.).
There was a problem hiding this comment.
Never mind, I see that it's in a clearly marked section below.
|
This is great, thanks for doing this! I'm going to go ahead and merge it as is, then just make the tweaks I mentioned above myself. Thanks again. |
|
Thank you @njx for both the merge & critique. I'll keep your comments in mind for future edits. I hope in the future it is mentioned that "extensions" are brackets' "plug-ins"; will help some understand better IMHO. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moved paragraphs around so least technical (most user-oriented) is on top, then tech/contributing (hacker info) is near the end. This allowed to streamline the prose, but I tried to avoid changing the text as much as possible.
Linked blog in welcome section (great for finding features; helps users decide if Brackets is for them).
Used H4 instead of bold for sub-headers.
cheers!