docs(markdown): add markdown supported features#30
Open
Abo3baziz wants to merge 4 commits into
Open
Conversation
…ith syntax examples - Add structured explanations for core Markdown elements (headings, emphasis, blockquotes, lists) - Document code block usage for both Markdown and Nunjucks with supported language labels - Include examples for links, images, horizontal rules, and tables (standard + aligned) - Add escape character reference table for Markdown formatting
Member
|
I think this should be another md file, not in the README |
Member
|
@Abo3baziz Are you still working on this? |
Contributor
Author
If you have any suggestions I can make it |
Member
|
- create docs directory - seperate supported markdown features to standalone file - add code image example
This file contains hidden or 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
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.
Closes #23
Rebased work onto the correct base branch after mistakenly branching from an unapproved PR.
Reapplied the changes on a clean branch to ensure the PR only contains the intended updates.