I like the idea of tagging for external blog posts. We can set some mandatory tags for external blogs, something like "external".
On Sat, 4 Jan 2020, 7:57 am Kamil Breguła, <kamil.breg...@polidea.com> wrote: > Hello, > > Maybe we should allow teaser posts, but with a visible label? New > users, who do not know Airflow well, can see these teasers easily and > find these valuable content. A website without content will be of > little use and will have a low informational character. As a new > person, I would like to have easy access to these posts on other sites > also. They were more valuable to me than posts describing internal > project topics - GSOD, Airflow website launch. The website supports > tag mechanism, so it can be easily done. > > Best regards, > Kamil > > On Sat, Jan 4, 2020 at 12:09 AM Kaxil Naik <kaxiln...@gmail.com> wrote: > > > > Agree with Jarek. > > > > On Fri, Jan 3, 2020 at 5:14 PM Jarek Potiuk <jarek.pot...@polidea.com> > > wrote: > > > > > > > > > > > > > > Is it okay to copy the content from the original source to airflow > > > website? > > > > > > > > > > From what I know from our PR/Marketing people - think this practice is > > > discouraged and makes search engines demote ranks of the "copy" sites. > > > Google highly promotes original content and demotes sites that are > copying > > > it. > > > > > > J. > > > > > > > > > > On Fri, Jan 3, 2020 at 11:20 PM Jarek Potiuk < > jarek.pot...@polidea.com> > > > > wrote: > > > > > > > > > BTW. I just looked at the blogs - I am also ok with removing the > two > > > > blogs > > > > > that we originally had - they were more to seed the "blogs" than > > > > intended > > > > > to drive traffic. It would make more sense to remove them so that > we > > > can > > > > > tell the contributors that we prefer original content. > > > > > > > > > > J > > > > > > > > > > On Fri, Jan 3, 2020 at 4:13 PM Jarek Potiuk < > jarek.pot...@polidea.com> > > > > > wrote: > > > > > > > > > > > +1. > > > > > > > > > > > > On Fri, Jan 3, 2020 at 3:43 PM Tomasz Urbaszek < > turbas...@apache.org > > > > > > > > > > wrote: > > > > > > > > > > > >> +1 for publishing whole blog posts on the Airflow website. > > > > > >> > > > > > >> T. > > > > > >> > > > > > >> On Fri, Jan 3, 2020 at 3:37 PM Kaxil Naik <kaxiln...@gmail.com> > > > > wrote: > > > > > >> > > > > > >> > Hey all, > > > > > >> > > > > > > >> > I wanted to raise a point regarding our Blog on the Airflow > > > website. > > > > > >> > > > > > > >> > There is an open PR: > > > > https://github.com/apache/airflow-site/pull/231 > > > > > >> from > > > > > >> > Chandu Kavar to add 2 blog posts based on his nicely written > > > Airflow > > > > > >> > testing material. > > > > > >> > > > > > > >> > However, the blog post basically links back to the original > > > content > > > > on > > > > > >> > medium instead of providing the content on the website itself. > > > > > >> > > > > > > >> > I replied saying we should have the entire content on the > website > > > > for > > > > > >> it to > > > > > >> > be meaningful to serve any purpose. > > > > > >> > > > > > > >> > And then I actually checked the currently published blog > posts too > > > > and > > > > > >> > found out that some posts are similar. > > > > > >> > > > > > > >> > The blog post isn't that useful in that case. > > > > > >> > > > > > > >> > So I would like to propose the following guidelines: > > > > > >> > > > > > > >> > - The content should be on the Blog Post itself and not > something > > > > like > > > > > >> "To > > > > > >> > Read more visit this website" > > > > > >> > - Linking to own and other good blogs/article/docs are fine > and > > > > > >> encouraged > > > > > >> > where it makes sense but not to intentionally drive traffic > away > > > > from > > > > > >> the > > > > > >> > Blog Post > > > > > >> > > > > > > >> > Let me know your thoughts. > > > > > >> > > > > > > >> > Regards, > > > > > >> > Kaxil > > > > > >> > > > > > > >> > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Jarek Potiuk > > > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer > > > > > > > > > > > > M: +48 660 796 129 <+48660796129> > > > > > > [image: Polidea] <https://www.polidea.com/> > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Jarek Potiuk > > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer > > > > > > > > > > M: +48 660 796 129 <+48660796129> > > > > > [image: Polidea] <https://www.polidea.com/> > > > > > > > > > > > > > > > > > > -- > > > > > > Jarek Potiuk > > > Polidea <https://www.polidea.com/> | Principal Software Engineer > > > > > > M: +48 660 796 129 <+48660796129> > > > [image: Polidea] <https://www.polidea.com/> > > > >
