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

Make page width to be more adaptive to browser #28

Closed
longquanzheng opened this issue Mar 18, 2021 · 9 comments
Closed

Make page width to be more adaptive to browser #28

longquanzheng opened this issue Mar 18, 2021 · 9 comments

Comments

@longquanzheng
Copy link
Collaborator

Screen Shot 2021-03-18 at 2 26 54 PM

Is it possible to make the width of the page more adaptive? @just-at-uber

@just-at-uber
Copy link
Contributor

This is rendered in a table, i don't think there is much you can change here without changing to the format which vuepress uses for their configs:
https://vuepress.vuejs.org/config/#basic-config

@just-at-uber
Copy link
Contributor

@longquanzheng
Copy link
Collaborator Author

This is rendered in a table, i don't think there is much you can change here without changing to the format which vuepress uses for their configs:
https://vuepress.vuejs.org/config/#basic-config

We have almost 300 dynamic configurations and growing. Would it be a problem?

@just-at-uber
Copy link
Contributor

There shouldn't be a word limit restriction for pages if that is the question. Also it will show in the left side navigation all config entries if users want to quickly scan for a particular config. When navigating to different pages, these items will collapse, so it will only be visible for users when they navigate to the config page.

If page size is the concern, it might make sense to split into smaller pages with common dynamic configs.

For example, have a separate page for:

  • Shared Dynamic Configuration
  • Frontend Dynamic Configuration
  • Matching Dynamic Configuration
  • etc.

@longquanzheng
Copy link
Collaborator Author

There shouldn't be a word limit restriction for pages if that is the question. Also it will show in the left side navigation all config entries if users want to quickly scan for a particular config. When navigating to different pages, these items will collapse, so it will only be visible for users when they navigate to the config page.

If page size is the concern, it might make sense to split into smaller pages with common dynamic configs.

For example, have a separate page for:

  • Shared Dynamic Configuration
  • Frontend Dynamic Configuration
  • Matching Dynamic Configuration
  • etc.

Okay, I will try that. Thanks Justin.

@longquanzheng
Copy link
Collaborator Author

Removing the table in #41

@Beyourself123345788900
Copy link

    • [ ]

@just-at-uber
Copy link
Contributor

Is this still an issue @longquanzheng ?

@longquanzheng
Copy link
Collaborator Author

No we can close it now . Thanks Justin

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

No branches or pull requests

3 participants