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

Chore: Import blog posts from dev.to #328

Open
nickytonline opened this issue Jun 10, 2024 · 3 comments
Open

Chore: Import blog posts from dev.to #328

nickytonline opened this issue Jun 10, 2024 · 3 comments
Assignees
Labels
chore label to mark dependency and documentation updates

Comments

@nickytonline
Copy link
Member

nickytonline commented Jun 10, 2024

Do an initial import of blog posts from DEV.

@nickytonline and @BekahHW have some scripts they're using, but at some point we should clean up those scripts and add them as part of the guide to get blog posts in or maybe even a GitHub action that generates a pull request.

@BekahHW
Copy link
Member

BekahHW commented Jun 20, 2024

@nickytonline I'm not sure if that makes sense here. We want the Dev blog to use opensauced.pizza/community-resources as the canonical_url.

@nickytonline
Copy link
Member Author

What I meant was we can create a script that pulls the latest from dev.to, manipulates it to be viewable on opensauced.pizza/docs and creates a PR.

Nothing related to the canonical URL, although when we pull them in from DEV, we can set the canonical URL via the dev.to API or just do it manually after the fact.

@BekahHW
Copy link
Member

BekahHW commented Jun 21, 2024

@nickytonline, I understood. The Dev posts definitely need to have the OpenSauced canonical_url if we want to benefit. What I was trying to say above is that I would create the post here first and then move it to Dev. I guess it doesn't really matter as long as we set the canonical_url.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore label to mark dependency and documentation updates
Projects
None yet
Development

No branches or pull requests

2 participants