I second this, especially since the version association for blog posts is often vague. This makes looking at historical blog posts quite annoying because it's difficult to tell if some of the specific advice has changed since. On Jul 24, 2014 2:23 PM, "Jack Krupansky" <j...@basetechnology.com> wrote:
> Blog posts are great for highlighting and focusing the community on new > features, changes, and techniques, but any knowledge content in them > definitely needs to be in the docs as well. > > -- Jack Krupansky > > *From:* Tyler Hobbs <ty...@datastax.com> > *Sent:* Thursday, July 24, 2014 12:07 PM > *To:* user@cassandra.apache.org > *Subject:* Re: Why is the cassandra documentation such poor quality? > > > On Thu, Jul 24, 2014 at 3:55 AM, Nicholas Okunew <naoku...@gmail.com> > wrote: > >> most of the important stuff being in blog format > > > Which blog posts are you referring to? We could definitely have the docs > team integrate some of the blog post topics into the normal docs and keep > them updated for new C* versions. > > > -- > Tyler Hobbs > DataStax <http://datastax.com/> >
