chore(deps): website: upgrade vuepress 0.x to 1.x#2828
chore(deps): website: upgrade vuepress 0.x to 1.x#2828chenrui333 merged 2 commits intorunatlantis:mainfrom
Conversation
krrrr38
force-pushed
the
docs-vuepress-1.x
branch
from
8c86817 to
29d63c9
Compare
| ga: "UA-6850151-3", | ||
| plugins: [ | ||
| ['@vuepress/google-analytics', { ga: "UA-6850151-3", }] | ||
| ], |
There was a problem hiding this comment.
| // https://vuepress.vuejs.org/theme/inheritance.html#usage | ||
| module.exports = { | ||
| extend: '@vuepress/theme-default' | ||
| } |
There was a problem hiding this comment.
Before setting this, CustomHome doesn't show navbar. So add this setting and mv components/CustomHome.vue into theme/components/Home.vue
| $buttonColor = #34be68 | ||
| $darkBackground = rgb(250, 250, 250) | ||
| .container | ||
| padding-top 3.6rem |
There was a problem hiding this comment.
custom-layout is disappeared. So add padding-top into Home.vue container for navbar.
|
https://app.netlify.com/sites/runatlantis/deploys/63a047b25b06910008582742 .node-version is available. https://docs.netlify.com/configure-builds/manage-dependencies/#node-js-and-javascript |
| @@ -0,0 +1 @@ | |||
| 14.21.2 | |||
There was a problem hiding this comment.
Should we bump this to node 16.x since that's the latest lts? Or should we do that in a separate pr?
There was a problem hiding this comment.
yeah, we can bump it in a separate PR and check with netlify deployment.
|
This is great. Nice work! I think we can wait on upgrading to vue 2.x until it's out of beta. @runatlantis/maintainers i clicked around on the preview website and it looks pretty good. Please take a second look. |
chenrui333
changed the title
|
Thanks @krrrr38! |
nitrocode
changed the title
3 participants
what
why
Currently, we use vuepress 0.x.
discussion
references