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 Install with Browser Compat. & FAQ #7682

Closed
wants to merge 1 commit into from
Closed

Conversation

jsosulska
Copy link
Contributor

This adds a compatibility guideline and updates the FAQ regarding IE11 support

@jsosulska jsosulska added type/docs Documentation needs to be created/updated/clarified type/docs-cherrypick labels Apr 21, 2020
@@ -76,3 +76,17 @@ it is on your PATH or you may get an error about Consul not being found.
```shell
$ consul -v
```

## Consul UI Supported Versions
Copy link
Member

Choose a reason for hiding this comment

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

I am wondering if this is the best place to up the supported versions. Maybe this could go into the faq too. What do you think?

Copy link
Contributor

Choose a reason for hiding this comment

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

@i0rek Would it make more sense if this was in its own page underneath Install? Unless we created a separate page for Supported Platforms/System requirements and placed it there, it would also make sense.

We do need to work on a simple docs page that defines what users should expect when installing and managing consul. cc @mikemorris

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for putting this together @jsosulska !

Good call @i0rek ! I'd agree with that, I'd say we just move the entire chunk under the FAQ's. I'd also consider we use the FAQ question:

##Q: What browsers does the Consul UI support? (or similar)

Which means this is about 'browser support generally' rather than just 'IE11 support'. We will want to be clear about our browser support even after IE11 has completely gone.

Just my 2 cents here though, I think this will be a great help whichever.

@jescalan
Copy link
Contributor

If this doesn't need to go out before the 1.8 release, is there any chance you could base it off the je.new-website branch?

@jescalan jescalan removed their request for review April 24, 2020 18:13
@jescalan
Copy link
Contributor

Removing myself as a reviewer, as I am not involved in the UI's browser support decisions, but the PR looks good to me if that means anything!

@jsosulska
Copy link
Contributor Author

Closing in favor of #7861

@jsosulska jsosulska closed this May 12, 2020
@kisunji kisunji deleted the compatibility branch September 13, 2021 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/docs Documentation needs to be created/updated/clarified
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants