Custom Decorators in Django

BOVAGE commented 2 years ago

Article checklist

Attention

Our Peer Reviewer and Content Moderator teams do NOT provide any revisions services. All revisions and edits should be completed on your own forked repo (as to not take up room in the queue) in order for our team to review them all in a timely manner.

ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.

As a rule of thumb - please be sure to only submit articles (pull requests) that are fully polished and ready to be published. Be sure to go through our resources documents for extra and 3rd party (vetted) resources to help improve overall technical writing.

Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[ ] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #7701

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

welcome[bot] commented 2 years ago

👋 Welcome and thank you very much for contributing your 1st article to the EngEd Program. We always recommend new contributors to go over our Resources Page, where we have laid out valuable resources meant to help improve our community members' overall technical writing abilities. We are looking forward to going over your amazing content 🚀

probot-cc[bot] commented 2 years ago

Good afternoon and thank you for submitting your pull request for review and publishing. Your pull request has entered our queue and will be reviewed by our team of peer reviewers as soon as possible. 🚀 All articles are reviewed in the order in which they were received. Thank you.

hectorkambow commented 2 years ago

🚀

hectorkambow commented 2 years ago

@BOVAGE

Question, does this pull request have a corresponding topic suggestion form?

BOVAGE commented 2 years ago

@BOVAGE

Question, does this pull request have a corresponding topic suggestion form?

Yes sir, it does. The topic suggestion form

hectorkambow commented 2 years ago

👍

Thank you - just needed to make sure they were linked (see image) that way once the article is published (merged) it auto-closes the topic form as well.

BOVAGE commented 2 years ago

👍

Thank you - just needed to make sure they were linked (see image) that way once the article is published (merged) it auto-closes the topic form as well.

Okay sir. Got it

hectorkambow commented 2 years ago

@BOVAGE just noticed that you have not included any author details (to create your author profile).

This is how your articles will be listed under your profile.

In order to publish the article we would need your author details - please see the new contributor folder for more info on how to submit.

BOVAGE commented 2 years ago

@BOVAGE just noticed that you have not included any author details (to create your author profile).

This is how your articles will be listed under your profile.

In order to publish the article we would need your author details - please see the new contributor folder for more info on how to submit.

I have added the author details now sir.

WanjaMIKE commented 2 years ago

Plagiarism check is done

WanjaMIKE commented 2 years ago

Hello @BOVAGE I will get started on this technical review as soon as possible. Sorry for the delay. Thanks

hectorkambow commented 2 years ago

@Collince-Okeyo would like to do a test review on this PR

@WanjaMIKE if you have not started yet.

👍

WanjaMIKE commented 2 years ago

Sure, @Collince-Okeyo you can take up the PR. Thanks

hectorkambow commented 2 years ago

🚀

Thank you Mike

@Collince-Okeyo

@WanjaMIKE is a veteran in the program - he is always a reliable resource if you have any questions as well. 💯

Collince-Okeyo commented 2 years ago

Sure, @Collince-Okeyo you can take up the PR. Thanks

Thank you @hectorkambow and @WanjaMIKE for this opportunity

Collince-Okeyo commented 2 years ago

@BOVAGE , Please do the suggested corrections once done please let me know to proceed with the review process.

BOVAGE commented 2 years ago

@Collince-Okeyo, I have made the suggested changes. Thank you.

hectorkambow commented 2 years ago

@Collince-Okeyo

It looks like this PR is ready for a "ready for final review" label?

Assuming both prelim & tech review have been completed?

Collince-Okeyo commented 2 years ago

@Collince-Okeyo

It looks like this PR is ready for a "ready for final review" label?

Assuming both prelim & tech review have been completed?

@hectorkambow , thank you for following up,...

The PR is ready for a "ready for final review" label since all the reviews are completed.

Collince-Okeyo commented 2 years ago

Hello @hectorkambow ,

Please add the 'ready for final review' tag to this PR

BOVAGE commented 2 years ago

Hello @hectorkambow.

@Collince-Okeyo is done with the review.

hectorkambow commented 2 years ago

Thank you for the ping @BOVAGE

I lose many notification in my inbox.

hectorkambow commented 2 years ago

@BOVAGE Well done !

Please review any edits made by your peer reviewer (or myself) to improve future blog post.

You'll be able to see your live published article on the site (in about 30 mins or so).

To give your article a boost in page engagement - be sure to share it across your social site (LinkedIn/Twitter) and tag the EngEd program so we can also share it and give it some traction/exposure as well!

If you have not done so already - consider adding a skill section to your author page. This will go a long way for potential future employers.

NOTE: Also, take into consideration that you can add any other past projects of yours: videos, talks, tutorials, articles (on ANY other site) - you can add them to your EngEd profile.

Think of the EngEd profile as your one-stop shop for everything you do in DEV - making it easier for you to share all your accomplishments when you go out for an interview or employment opp.

It can be from any blog site (or site in general).

Let me know if you have any questions moving forward.

Also important NOTE: We wanted to mention that we're going to take a focus on content centered around Kubernetes (K8s) for the month of August.

The best five (5) K8s related articles that come in this month will be eligible to receive a complimentary virtual pass to KubeCon USA ($75.00 value) in Oct.

We're looking for content that enriches developers' understanding of K8s, best practices, and its many use cases. Please be sure to go over the already published content the EngEd community has created on Kubernetes to see where we can build upon or further explore. 🚀

section-engineering-education / engineering-education