-
Notifications
You must be signed in to change notification settings - Fork 17
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
Make part 1, 2, and 3 of Cadence Tutorial more interactive and streamlined #172
Draft
briandoyle81
wants to merge
21
commits into
main
Choose a base branch
from
brian-doyle/content-updates-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 5 commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
50f852d
Make part 1 and 2 more interactive and streamlined
briandoyle81 7aa4f27
Add 03, further edits to 1 and 2, various files
briandoyle81 42789da
Revert resources.mdx to .md
briandoyle81 3763139
Update playground image
briandoyle81 102d994
Restore file names in versioned docs
briandoyle81 7fb6b08
Apply Ali's feedback
briandoyle81 1deb4b2
Use specific link in First Steps
briandoyle81 f1565e8
Fix broken links in 04
briandoyle81 93e146c
Add draft of Cadence 4 Capabilities
briandoyle81 d82ef55
fix links
nialexsan c29aee4
Merge remote-tracking branch 'origin/main' into brian-doyle/content-u…
nialexsan 259f4a8
Fix typo
briandoyle81 235c458
Fix typo
briandoyle81 d23ff53
Update tutorial 5
briandoyle81 fd22f98
Update title to match content
briandoyle81 16aa66e
Add draft of udpated cadence 5
briandoyle81 50e54b3
Fix typo
briandoyle81 da23aee
Partial: Stash progress on cadence 6
briandoyle81 4571a72
Stash progress
briandoyle81 59033e1
Update fungible tokens tutorial
briandoyle81 0f8f258
Update starter
briandoyle81 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
Here and below: It looks like only the newlines/line breaks got removed from the original content.
The line breaks are intentional, they are "Semantic Line Breaks": They are ignored in the rendered output, but are useful in the source Markdown, because they keep lines limited to a certain length (<=100) like in source code, and make it easier to review changes.
See https://sembr.org/
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've worked with both methods before and find removing semantic line breaks to generally improve workflow for writing, editing, and updating docs.
Most editors can be set to wrap the text when viewing it, and by not having the line breaks it's much easier to edit and wordsmith the text because updates automatically display similar to how they'd appear on the page without having to save to autoformat, or run a script to rebreak at 80 wide.