Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain divisions between guides #36

Merged
merged 2 commits into from
Mar 10, 2022
Merged

Explain divisions between guides #36

merged 2 commits into from
Mar 10, 2022

Conversation

jenweber
Copy link
Contributor

This PR follows on work done to try and come up with a rule of thumb to separate CLI guides and Ember guides. It records it for future reference. Here, "rule of thumb" means that these categorizations should usually work, but we can break them on an as-needed basis.

Copy link
Member

@amyrlam amyrlam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Contributor

@locks locks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's some comments inline.

guides.md Outdated Show resolved Hide resolved
guides.md Outdated

In some cases, a feature may be omitted from the Guides until it has reached some level of improvements to tooling or coherence with a mental model, but this is decided on a case-by-case basis.

## The Ember CLI Guides
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## The Ember CLI Guides
### The Ember CLI Guides

guides.md Outdated Show resolved Hide resolved

The Ember Guides are meant to cover the needs of the majority of Ember users. They focus on runtime features, but may have some build time information. If 80% of people who run `ember new` would need the information, it should be covered in the Guides. Deprecated features should not be shown in the latest version. The Guides are not meant to be exhaustive of Ember's features, but rather they read like a book and give you the "happy path" journey through building an app. In contrast, the API Docs are meant to cover all of Ember's features.

In some cases, a feature may be omitted from the Guides until it has reached some level of improvements to tooling or coherence with a mental model, but this is decided on a case-by-case basis.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might want to create an issue to update this once the Stages RFC comes through and we have the "Recommended" stage.

guides.md Outdated Show resolved Hide resolved
guides.md Outdated

## The Ember Guides

The Ember Guides are meant to cover the needs of the majority of Ember users. They focus on runtime features, but may have some build time information. If 80% of people who run `ember new` would need the information, it should be covered in the Guides. Deprecated features should not be shown in the latest version. The Guides are not meant to be exhaustive of Ember's features, but rather they read like a book and give you the "happy path" journey through building an app. In contrast, the API Docs are meant to cover all of Ember's features.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The Ember Guides are meant to cover the needs of the majority of Ember users. They focus on runtime features, but may have some build time information. If 80% of people who run `ember new` would need the information, it should be covered in the Guides. Deprecated features should not be shown in the latest version. The Guides are not meant to be exhaustive of Ember's features, but rather they read like a book and give you the "happy path" journey through building an app. In contrast, the API Docs are meant to cover all of Ember's features.
The Ember Guides are meant to cover the needs of the majority of Ember users. They focus on runtime features, but may have some build time information. If 80% of people who run `ember new` would need the information, it should be covered in the Guides.
Deprecated features should not be shown in the latest version.
The Guides are not meant to be exhaustive of Ember's features, but rather they read like a book and give you the "happy path" journey through building an app. In contrast, the API Docs are meant to cover all of Ember's features.

Giving the paragraphs some breathing room so that at a glance you noticed "Deprecated" and "API Docs".

Copy link
Member

@mansona mansona left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

amazing work! this will be great to get written down explicitly in the handbook 🎉

@jenweber jenweber requested a review from locks May 21, 2020 16:15
Copy link
Member

@MelSumner MelSumner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@mehulkar
Copy link

This looks like it's ready to merge? And so ember-learn/cli-guides#168 can be closed also?

@locks locks merged commit 14f0e02 into main Mar 10, 2022
@locks locks deleted the guides-content-sorting branch March 10, 2022 16:21
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.

6 participants