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

Create a blog post about why you should use Kedro #21

Closed
stichbury opened this issue Nov 29, 2022 · 2 comments
Closed

Create a blog post about why you should use Kedro #21

stichbury opened this issue Nov 29, 2022 · 2 comments
Assignees
Labels
Blog post creation Blog posts (ideas and execution)

Comments

@stichbury
Copy link
Contributor

stichbury commented Nov 29, 2022

This captures the creation of content to promote best practices and encourage Kedro usage as a way to follow those practices.

We should probably write 2 posts: one which is the best practice (forms the basis of Academy) and second builds upon it to talk about Kedro. Then we can put the first post into a publication like "Towards Data Science" which doesn't like marketing, and publish the second ourselves.

There's also scope for other formats such as video, webinar or podcast script, but for now, this issue is purely about the mechanics of getting two complementary articles written, in draft, to share with GetInData for co-marketing.

@stichbury stichbury self-assigned this Nov 29, 2022
@stichbury stichbury transferred this issue from kedro-org/kedro Feb 3, 2023
@stichbury stichbury added the Blog post creation Blog posts (ideas and execution) label Feb 3, 2023
@stichbury
Copy link
Contributor Author

First post is complete (on towards data science) and second post (with GetInData) is in progress

@stichbury
Copy link
Contributor Author

Done! This is the "Meet your new team lead: Kedro" blog post.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blog post creation Blog posts (ideas and execution)
Projects
None yet
Development

No branches or pull requests

1 participant