[Proposal] Create a "Blog" or Newsletter for Organization Wide EUI Communication

[breehall]

Summary
I'd like to propose an EUI "blog", newsletter, or other organization wide medium where we can not only share EUI updates, but also share general tips & tricks that will help and educate EUI consumers. We currently have an email newsletter that is released to Kibana, but having an additional or expanded medium could be beneficial to all consumers.

What would be included?
I don't think there has be an exact content style for this "blog" or a dedicated release schedule. It could just be published as we have information to share. Topics can include:

• Decision Trees
  EUI has a wide variety of components and deciding which one best suites your needs may be tricky for consumers. What if we were able to create something explaining the similarities and differences between certain components?
  For example:

  • Using EuiBasicTable vs. using EuiDataGrid
  • Using EuiFilterGroup vs. using EuiSelectable inside of a popover

• FAQ
  We get some great questions in the EUI Slack channel, but if you're not subscribed it's likely you'll miss them. This will give us a space to document and reference those questions and answers as needed. This could also prevent duplicate questions and issues from being posted in Slack and in the EUI Github repo.

• Tips / Tricks / EUI Education
  Some of these tips & tricks will likely come from questions and from seeing component implementation in working systems. There may be things that we can educate consumers on to make their development and testing process a little easier. For example, I've noticed that when some consumers create unit tests for code that includes EUI components, they may not be aware of its nested components. I've seen this with components that use EuiScreenReaderOnly. Tests maybe looking for strict equality of a certain phase and because the EuiScreenReaderOnly component includes its own text, these tests will fail.

Proposed Solutions
I used the word "blog" above, but I'm sure what the best medium would be for this publication. I like the thought of having a dedicated page on the EUI Docs site in the package section where we can post articles and keep them in one place, but this would place the responsibility of reading on consumers (which defeats the purpose). I also like the thought of a newsletter that interested parties can willingly opt into, however, this method wouldn't provide the ease of searching for something specific.
I don't have an exact method in mind, just bits and pieces that I'm hoping we can stitch together.

I would love to know what your thoughts are!

[cchaos]

Just a couple ideas about delivery:

• A newsletter style that anyone including consumers outside of Elastic can subscribe to. We'd need to use something like MailChimp to maintain a list and deliver the email.
• This newsletter would have two initial subscribers, our UX and dev google groups, replacing the typical one we just send as an email

[cchaos]

Then someone smart could also figure out a script that could hook up a panel on the home page to link to the latest newsletter

[breehall]

What do you think about combining the newsletter with a static page within the EUI docs? For each newsletter we send out, what if we included a copy of it (in Markdown) on a page in the docs. This way, past issues of the newsletter can be stored and referenced?

[ryankeairns]

May revisit in the future. Newsletter is internal/Elastic focused; CHANGELOG for all.