Skip to content

Conversation

@josedonizetti
Copy link
Contributor

This is part of the ongoing work to versioned prometheus documentation.
prometheus/docs#857

@grobie

- [Overview](overview.md)
- [Introduction](introduction.md)
- [Configuration](configuration.md)
- [Clients](clients.md)
Copy link
Contributor

Choose a reason for hiding this comment

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

Clients should go last, that's a technical reference very very few people need.

docs/index.md Outdated
- [Introduction](introduction.md)
- [Configuration](configuration.md)
- [Clients](clients.md)
- [Notifications](notifications.md)
Copy link
Contributor

Choose a reason for hiding this comment

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

The word Template should be in here

@@ -0,0 +1,16 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

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

Are the indexes not automatically generated?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@brian-brazil not sure about it. I didn't get the idea that the index.md on the promo repo was generated. Is there any reference about this?

Copy link
Contributor

Choose a reason for hiding this comment

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

If you look at them they're just the section title, with nothing else.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@grobie how did you generate the index.md on the prometheus doc?

Copy link
Member

Choose a reason for hiding this comment

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

I wrote the index.md by hand actually. My intent was to give users who read the docs locally a starting point. It was not meant to be just a list of the pages, but to include a small introduction as well. We can change that, but I guess a little explanation that the main documentation lives on a page online would be nice.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@brian-brazil @grobie should I add a brief content to it, or just remove it for now?

Copy link
Member

Choose a reason for hiding this comment

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

I'd keep it as starting point. But I'm fine with either.

Copy link
Member

@grobie grobie left a comment

Choose a reason for hiding this comment

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

Thanks a lot @josedonizetti! One last comment, then let's merge this!

docs/clients.md Outdated
---
title: Clients
sort_rank: 6
nav_icon: sliders
Copy link
Member

Choose a reason for hiding this comment

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

Remove all the nav_icon settings please.

@josedonizetti
Copy link
Contributor Author

@grobie Done! Question, after this is merged how will be the process to update the documentation?
When a PR is merged to change the documentation here, will the docs project rebuild itself or something else is needed?

@grobie
Copy link
Member

grobie commented Nov 8, 2017

We use https://www.netlify.com/ now to build and host the docs. They provide webhooks and I configured prometheus/prometheus to use the trigger that on every push. I'll do the same for alertmanager.

I need to make some changes to the docs repo to support multiple versioned repo docs. Took some shortcuts on the way.

@josedonizetti
Copy link
Contributor Author

@grobie

@stuartnelson3 is cutting a new release for alertmanger, and there are some important changes that must be updated in the documentation (pagerduty, and opsgenie were upgraded to a new version of their APIs) #1089

Do we change the existing docs so users have it properly there, and later update it here, or the change you will do on the docs repo to support alertmanager is coming soon and we wait to update it only here?

@grobie
Copy link
Member

grobie commented Nov 9, 2017

I'm almost done with the nanoc4 upgrade. I hope to have the changes ready tonight or latest Saturday night.

@josedonizetti
Copy link
Contributor Author

@grobie Any updates on this? Anything I can help?

@stuartnelson3
Copy link
Contributor

@grobie ping

@grobie
Copy link
Member

grobie commented Dec 14, 2017 via email

@josedonizetti
Copy link
Contributor Author

@grobie Is this doc migration for alertmanager still happening?

@aioue
Copy link
Contributor

aioue commented Jan 26, 2018

any way I can help progress this merge?

@grobie
Copy link
Member

grobie commented Jan 26, 2018 via email

@stuartnelson3
Copy link
Contributor

@grobie status on this?

@juliusv
Copy link
Member

juliusv commented Jun 1, 2018

@grobie Ping. Status?

@grobie
Copy link
Member

grobie commented Jun 3, 2018

No progress. Depends on a change and rewrite of the docs infrastructure. I'll try to pick that up again during the next two weeks, but can't guarantee anything.

@juliusv
Copy link
Member

juliusv commented Jun 5, 2018

@grobie Is this something that Luc (our new docs person) could help with, or are you too far into it?

@roidelapluie
Copy link
Member

Superseeded by #2292 , and prometheus/docs#1657

@stale stale bot removed the stale label Jun 9, 2020
@roidelapluie roidelapluie mentioned this pull request Jun 9, 2020
@josedonizetti
Copy link
Contributor Author

Considering @roidelapluie work, I’m closing this PR.

@josedonizetti josedonizetti deleted the docs branch June 11, 2020 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants