Rename "Core Concepts" to "Learn" #433
Closed
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
mattyg
reviewed
Mar 21, 2024
mattyg
approved these changes
Mar 21, 2024
Co-authored-by: Matt Gabrenya <[email protected]>
|
I'm having second thoughts about this -- instead, I think I'll just rename it in the menus and URLs, but keep the name 'Core Concepts' in the page content. I have plans for other stuff -- video content (which I don't want to do but I know people want), maybe more tutorials which are sorta buildy but more properly learny. Therefore, 'Core Concepts' seems useful as a header for the abstract stuff. |
|
Picking this up in #436 -- in which I only change the menu, not even the URLs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
making this into its own PR based on @mattyg 's suggestion in #413 . Rationale: 'Learn' is more consistent with 'Get Started' and the future 'Build', and it may be more consistent with how other dev docs are structured too.