y/cs Blog Post Submission
Thank you for writing an article for the y/cs Blog!

Our blog is a promotional platform open to all members, and we are welcoming of all kinds of topics. Whether it is a feature you added to a project, concept you learned in class, musings about recent tech news or even applications of AI (writing emails, studying for tests), all are encouraged!

In order to get your writing posted to the y/cs Blog, there are only two requirements:

1. Get at least 1 review from a friend/peer (having them leave comments on the document as proof)
2. Get approved by a y/cs reviewer (after this form, simple check for inappropriate content, typos, etc)

Once your blog is posted to our website, we will also promote it on our LinkedIn, tagging you in the post. We may also promote in on Instagram, Discord, and biweekly newsletter. Overall, this is a great, low-effort way to share your skills and build your personal brand!

Reach out to yalecomputersociety@gmail.com with any questions.
Email *
Contributors and Contact Information
Name(s) of Author(s) - First and Last *
Preferred Email - (for feedback and post notification) *
Name(s) of Peer Reviewer(s) - First and Last *
Google Document Guidelines
Please submit your article to us in the form of a Google Document. There should be some comments on that document as proof of peer review. Make sure to include a title for you post in the document, and feel free to add images!

Your document must be shared with yalecomputersociety@gmail.com for us to review.
Link to Google Document - (please make sure to share it with yalecomputersociety@gmail.com) *
LinkedIn Details
Optional details if you would like us to promote your blog on the y/cs LinkedIn and tag you
(Optional) Links to LinkedIn profiles for promotion
(Optional) Short, 5 sentence summary for LinkedIn and newsletter promotion
A copy of your responses will be emailed to .
Submit
Clear form
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google. - Terms of Service - Privacy Policy

Does this form look suspicious? Report