Consider a specific action you took within the DEV community. How do you think it might have created a ripple effect, impacting others or shaping the community?
Follow the DEVteam for more discussions and online camaraderie!
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (7)
Last year, I made a docs contribution to Dev.to's Editor Guide.
docs: making updates to Editor Guide #20258
What type of PR is this? (check all applicable)
Description
This PR makes a couple of updates in the Editor Guide. I noticed that when scheduling a post to be published the next day, the message, "This URL is public but secret, so share at your own discretion". After raising this issue to @michael-tharrington and learning that posts will only appear in feeds and on a user's profile when they are published on the day they are scheduled. Through another conversation, Michael pointed out that the bullet point about the Markdown editor needs to be updated since Dev.to now has two editors. By making these adjustments, users would gain a better understanding of how to edit and publish their posts.
Related Tickets & Documents
Not applicable
QA Instructions, Screenshots, Recordings
UI accessibility checklist
If your PR includes UI changes, please utilize this checklist:
Critical
andSerious
issues?For more info, check out the Forem Accessibility Docs.
Added/updated tests?
We encourage you to keep the code coverage percentage at 80% and above.
[optional] Are there any post deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?
@michaeltharrington talks more about this his spotlight contributor's article:
DEV Community Contributor Spotlight: Christine Belzie
Michael Tharrington for The DEV Team ・ Nov 10 '23
Love it! Thanks again for all the awesome work on this, Chrissy. 🙌
Last year, I convinced some great developers to start writing here on Dev.to. I'm quite happy to help grow the tech writing culture.
I have been writing articles for a while now. Initially, I posted them only on my blog. However, once I started crossposting them here, I noticed that developers found them useful in finding solutions to problems or as a resource for their work. As a result, my articles have gained good views and followers.
Well, whenever I've overcome a problem where there has been no documentation covering it I post it here. That has only really occurred 3 times, but yeah.
Lately easily 25% of the articles are pure AI, so I decided to start putting a comment for the author to see with the URL to the Dev.To guidelines on AI-assisted articles. This seems to enfuriate authors. Some say "this comment offends me", others delete the article and repost it later, and others hide my comment. But 100% of the authors ignore the guidelines completely.
By participating in js web framework flame wars on which is best :)