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

Update Chronograf docs for 0.11 #326

Merged
merged 8 commits into from
Mar 23, 2016
Merged

Update Chronograf docs for 0.11 #326

merged 8 commits into from
Mar 23, 2016

Conversation

rkuchan
Copy link
Contributor

@rkuchan rkuchan commented Mar 17, 2016

  • Creates a new 0.11 section and makes it the default documentation for Chronograf
  • Updates all images and gifs
  • Makes minor edits to the Getting Started guide
  • Creates a new Administration section with two pages: the first documents new features and the second discusses how to upgrade to 0.11 from versions <= 0.4

(Please excuse the unappealing commit history)

parent: Introduction
---

Easily modify the time range and [tag values](/influxdb/v0.10/concepts/glossary/#tag-value) displayed by a visualization and/or dashboard.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be 0.11 link?

@mark-rushakoff
Copy link
Contributor

There's a couple spots where there are 0.10 mentions/links that i think should be 0.11.

Besides that small detail, very well written. 👍

@rkuchan
Copy link
Contributor Author

rkuchan commented Mar 17, 2016

Thank you, @mark-rushakoff. I changed the 0.10 reference in the Getting Started guide.

I kept the 0.10 links that reference the InfluxDB documentation because we don't have docs for InfluxDB 0.11 yet. I'll be updating those once we get those docs up.

@rkuchan rkuchan merged commit 0d338ff into master Mar 23, 2016
@rkuchan rkuchan deleted the chronograf-update-011 branch March 23, 2016 03:28
@rkuchan rkuchan mentioned this pull request Mar 23, 2016
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants