-
Notifications
You must be signed in to change notification settings - Fork 133
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
Documentation: update references to external blogs on Hamilton #1046
Comments
I'd like to take this up! |
Great thank you. Assigned. I believe https://github.com/DAGWorks-Inc/hamilton/blob/main/docs/get-started/learning-resources.md is what you want to modify. Do you have an understanding of where and what to change? |
If I've understood the issue correctly, we want to have the latest blogs in the external blogs section. Is that correct? If that's the case, then I was thinking if I could make use of a substack API(if it exists)/scrape https://substack.com/@dagworks/posts for the posts and then update the posts in external blog sections in the markdown file. |
yep pretty much. You'd need to filter to posts that are about hamilton. Otherwise there's a few other posts that are linked in the issue that should also be added. |
Okay. So I guess I need to hardcode the other 4 posts. Is that right? And how many posts from substack should be added in learning-resources.md(programatically, through script, that is)? |
@sikehish yes that's fine. I think using a date cut off is fine. Since that's how we'd update/run it. Pull posts older than X and add to the docs please :) |
Is your feature request related to a problem? Please describe.
We need to update https://hamilton.dagworks.io/en/latest/get-started/learning-resources/#external-blogs.
Describe the solution you'd like
We need to provide updates for blogs on Hamilton.
Some that come to mind:
Describe alternatives you've considered
N/A
Additional context
It would be great to semi-automate this. E.g. make updating this simpler to do, by running a command for example.
The text was updated successfully, but these errors were encountered: