Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for cover images from dev.to #3639

Open
3 tasks
sirinoks opened this issue Jul 25, 2022 · 7 comments
Open
3 tasks

Add support for cover images from dev.to #3639

sirinoks opened this issue Jul 25, 2022 · 7 comments
Assignees
Labels
area: back-end area: docusaurus Anything related to Docusaurus area: front-end area: microservices hacktoberfest Issue recommended for hacktoberfest type: documentation (docs) Improvements or additions to documentation type: enhancement New feature or request type: nice to have Feature that'd be nice to have, but not a priority

Comments

@sirinoks
Copy link
Contributor

sirinoks commented Jul 25, 2022

In dev.to there is an option to add a cover image to your post.
Cover image option
How it looks in dev.to

However, in Telescope we don't get any of that.
How it looks in Telescope currently

Figure out if we can, how to add cover images to Telescope, and implement it.

Resources:

Code locations:

  • Posts api. You might need to change code in this location to include parsing of the cover images.
  • Parser service. You might need to change this too.
  • Front end part of Telescope. You might need to insert the cover image here and make sure it looks right.

Additional comments:

You will need to figure out how telescope's microservice('s) parse posts from specifically dev.to. Besides this back end work, you might also need to change some of front end styling to make sure the cover images appear properly.

It is unknown currently, if we aleady get cover image information of the back end. If so, you will just need to add it to show up in front end. If the task requires you to do both (make sure we get the cover image through the api call in the back end AND make sure it shows up in the front end), it is okay for you to just do the one part of it, while the other part will be made into a different issue. However, it would be cool to do both, as upon completion you will get a visible result.

It would be nice of you to also add a sentence or two about this feature into our docusaurus documentation service. (Check docusaurus service)

Multi-part checklist

It is unknown if the task has one, or multiple parts to it. Here is a checklist for possible parts to be completed. If a PR to this issue is made, make sure to check ALL these features are added. If not - create a separate issue for each of them.

  • Get a cover image through an API call from dev.to
  • Place the cover image into our Telescope front end
  • Add documentation into docusaurus describing the changes you've made

For maintainers

Please provide feedback if we need such a functionality in the first place. If you know more concrete steps to take to implement this, please change the description and lables.

@sirinoks sirinoks added type: enhancement New feature or request type: documentation (docs) Improvements or additions to documentation area: back-end area: front-end type: nice to have Feature that'd be nice to have, but not a priority Priority: Low area: microservices area: docusaurus Anything related to Docusaurus labels Jul 25, 2022
@sirinoks sirinoks added the hacktoberfest Issue recommended for hacktoberfest label Sep 29, 2022
@P-DR0ZD
Copy link
Contributor

P-DR0ZD commented Oct 14, 2022

I would like to try this issue can I be assigned?

@manekenpix
Copy link
Member

@P-DR0ZD all yours!

@liutng
Copy link
Contributor

liutng commented Nov 15, 2022

May I also have this issue? I will work together with @P-DR0ZD on this issue.

@P-DR0ZD
Copy link
Contributor

P-DR0ZD commented Nov 15, 2022

Yea we can split it up into front end back end

@SerpentBytes
Copy link
Contributor

any update on this?

@manekenpix
Copy link
Member

Since there hasn't been any activity in a while, I'm assigning this to @SerpentBytes.

@manekenpix manekenpix assigned SerpentBytes and unassigned liutng and P-DR0ZD Dec 21, 2022
@SerpentBytes SerpentBytes removed their assignment Apr 15, 2023
@SerpentBytes
Copy link
Contributor

Could I get this re-assigned, please? :)

@SerpentBytes SerpentBytes self-assigned this Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: back-end area: docusaurus Anything related to Docusaurus area: front-end area: microservices hacktoberfest Issue recommended for hacktoberfest type: documentation (docs) Improvements or additions to documentation type: enhancement New feature or request type: nice to have Feature that'd be nice to have, but not a priority
Projects
None yet
Development

No branches or pull requests

5 participants