Improved documentation with examples #3
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
Formatted messages Started documentation with apiary.io Updated gitignore Added launch.json for people with VS code
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.
I recently explored this project and while it sparked my interest, I noticed the documentation could use some enhancement for better clarity. To address this, I've initiated updates to improve it and am in the process of creating an interactive "playground" to help new users verify the application’s functionality.
The initial updates have been committed to the development branch of my fork. Although it's a work in progress, the foundation is set. I am also considering developing a feature to handle Cloudflare notification translations, should there be a demand for it.