Will Meighan; https://github.com/Will-Meighan
Elom Amouzou; https://github.com/eamouzou
Dan Reardon; https://github.com/dreardon1021
As a user,
On the article show page,
I should see three related youtube videos,
that can be played without leaving the page,
styled in an aesthetically pleasing format.
The backend developers, Will and Elom, were able to succesfully consume the Youtube API using the search function. We used a partial within the article show page to direct our code to the youtube view, where we then used fetch to begin the Youtube MVC function. We used the article keywords and tags as the parameters, and created a JSON object for the front end.
Dan, our front end developer, was able to manipulate the JSON object to disply the videos in an aesthetically pleasing format. He was able to utilize stylesheets and liquid tags to format the youtube videos. The youtube videos are playable directly from the article show page.
The hardest aspect of this project for each of us was simply absorbing this monolithic code base and understanding where we would need to work and what we would need to do to get to our desired product. Once we were able to digest the code base, we felt pretty good about how to accomplish our goal.
The only spot we felt needed refactoring was our youtube API consumption. We were originally only using the article tags for the search function, but we felt we should incorporate the keywords as well to make the search more robust and dynamic, in case there were to ever be updated to the code base.
Below is the flow chart of the code base we used and adjusted for our given track, elsewhere on the internet.
Welcome to the dev.to codebase. We are so excited to have you. With your help, we can build out DEV to be more stable and better serve our community.
dev.to (or just DEV) is a platform where software developers write articles, take part in discussions, and build their professional profiles. We value supportive and constructive dialogue in the pursuit of great code and career growth for all members. The ecosystem spans from beginner to advanced developers, and all are welcome to find their place within our community. ❤️
- What is dev.to?
- Table of Contents
- Contributing
- Getting Started
- Developer Documentation
- Core team
- Vulnerability disclosure
- License
We encourage you to contribute to dev.to! Please check out the Contributing to dev.to guide for guidelines about how to proceed.
This section provides a high-level quick start guide. If you're looking for the installation guide, you'll want to refer to our complete Developer Documentation.
We run on a Rails backend, and we are currently transitioning to a Preact-first frontend.
A more complete overview of our stack is available in our docs.
- Ruby: we recommend using rbenv to install the Ruby version listed on the badge.
- Yarn 1.x: please refer to their installation guide.
- PostgreSQL 9.4 or higher.
- ImageMagick: please refer to ImageMagick's installation instructions.
- Redis 4 or higher.
- Elasticsearch 7 or higher.
View Full Installation Documentation.
Check out our dedicated docs page for more technical documentation.
- @benhalpern
- @jessleenyc
- @peterkimfrank
- @maestromac
- @zhao-andy
- @lightalloy
- @rhymes
- @jacobherrington
- @mstruve
- @atsmith813
- @citizen428
- @nickytonline
- @joshpuetz
- @vaidehijoshi
- @juliannatetreault
- @ridhwana
- @fdoxyz
We welcome security research on DEV under the terms of our vulnerability disclosure policy.
This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. Please see the LICENSE file in our repository for the full text.
Like many open source projects, we require that contributors provide us with a Contributor License Agreement (CLA). By submitting code to the DEV project, you are granting us a right to use that code under the terms of the CLA.
Our version of the CLA was adapted from the Microsoft Contributor License Agreement, which they generously made available to the public domain under Creative Commons CC0 1.0 Universal.
Any questions, please refer to our license FAQ doc or email [email protected].