2nd pr article test#10
Open
hectorkambow wants to merge 1 commit intoclassic5594:masterfrom
Open
Conversation
2nd pr article test
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.
2nd pr article test
Copy the Text below to paste into template.
If this is your 1st PR - read the paragraph below carefully.
Feel free to delete the bottom text - if this is NOT your 1st PR.
Contribution Guidelines
In order to achieve a level of consistent style and increasingly elevated quality, we have created this document to help new contributors. Let's start by reviewing what's needed.
Ensure all article submissions are pre-checked for English grammar technically accurate and delivered under the assertion that the content is original to you and includes proper citations (including sourced images).
Before submitting your article, we request that you cross-check the readability of your content using this free tool.
http://www.hemingwayapp.com/
This check helps make your writing BOLD & CLEAR by calling attention to any lengthy, complex sentences and common errors. If you see a yellow sentence, you may want to shorten or split it.
For Code Snippets:
https://repl.it/
Repl.it is an interactive programming environment and you can link those code examples into your articles.
Use it on any code examples to be included in future articles to allow the audience a chance to test and play with the code you are referencing.
Communicating your key takeaways
Articles should be clear, accurate, and fully explained. We are more interested in substance than length, and supporting examples are always encouraged. At the same time, articles that include mostly code with very little narrative lack sufficient depth and guidance for the audience to fully grasp important concepts.
We suggest you think about what is most important to your article or any pain point you are addressing. Assume the audience is smart but has no prior exposure to the common terminology in your article.
For example:
If your article is about serving ML models with Django, then the reader should have a decent understanding of something like:
The structure of a Django app
How to use such an app to serve a model for inference
The details your article gives should help further grow the readers’ skills as they practice on their own projects.
Articles should be a minimum of 750 words.