vuepress / ecosystem Goto Github PK
View Code? Open in Web Editor NEWOfficial plugins and themes for VuePress2
Home Page: https://ecosystem.vuejs.press
License: MIT License
Official plugins and themes for VuePress2
Home Page: https://ecosystem.vuejs.press
License: MIT License
The auto sidebar feature of the default theme is quite useful, especially in cases where the pages are autogenerated documentation from something like TypeDoc.
Currently you can only use the auto feature on all pages or manually specify the sidebar for every page. It would be great if you could turn the feature on per page as well.
I was able to hack it to make it work for the data-grid-vue site using vue router nav guards but its not maintainable and would probably be pretty easy to implement in the theme unless the changes to not use the vue router are going to make the auto sidebar feature more difficult to implement in general.
https://github.com/nruffing/data-grid-vue/blob/main/vuepress/.vuepress/client.ts#L63
Implement passing 'auto' to a SidebarConfigArray
for a given page in the theme's config object.
We could also change SidebarConfigObject
to allow a string directly.
export type SidebarAuto = 'auto'
export type SidebarConfigObject = Record<string, SidebarConfigArray | SidebarAuto>
sidebar: {
'/guide/': [
{
text: 'Guide',
children: [
'/guide/README.md',
'/guide/columns.md',
'/guide/sorting.md',
'/guide/filtering.md',
'/guide/paging.md',
'/guide/more-coming-soon.md',
],
},
],
'/generated/': 'auto'
'/dotnet-generated/': 'auto',
},
No response
No response
The URL path is missing for links to headings in the sidebar. This is also occurring on the docs of the default theme. This issue can be seen when hovering over any of the links to headings on the provided reproduction page.
https://ecosystem.vuejs.press/themes/default/config.html
npm
-
md文档存放在中文路径下 ,并正确配置sidebar,navbar,文档标题不在侧边栏中展示
默认主题当前还不支持右侧的锚点功能,如果单个md文档内容过多,容易导致sidebar太长,现有的插件往往和最新vuepress版本之间存在兼容性问题
添加配置开关,用户可进行选择是否使用右侧锚点
No response
No response
Since Apple introduced new Safari design in WWDC 2021, personally, I think that changing theme-color with dark mode dynamically would have a nicer look for upcoming Safari 15.x (maybe improve other browsers too). Or in another word the current theme-color is too bright for the dark mode, compared in the attached video.
Not experienced in Vue but I think something like this would did help:
// ToggleDarkButton.vue
…
const changeThemeColor = (): void => {
const themeColorEl = window?.document.querySelector(
'meta[name="theme-color"]'
)
themeColorEl?.setAttribute('content', !isDark.value ? '#3eaf7c' : '#22272e')
}
…
const setDark = (): void => {
setDarkClass()
changeThemeColor()
}
onMounted(() => {
…
watch(isDark, setDark, { immediate: true })
})
If it fine I could pull a request, thanks for reviewing.
Mixpanel is a service like Baidu Analytics. But its SDK provided by mixpanel is not developer-friendly to SPA and requires manual reporting of routing change events. How about providing a vuepress plugin to extract this part of the common logic?
The SDK provided by MixPanel is not developer-friendly to SPA and requires manual reporting of routing change events. How about providing a vuepress plugin to extract this part of the common logic?
No response
No response
Is there a VuePress 2 plugin available that simplifies the deployment of Google Tag Manager, making it easier to incorporate various analytics and third-party service codes without the need to directly modify the template.html
file?
Existing plugins appear to focus on individual analytics, making it inconvenient for potential future expansions.
template.html
file.No response
No response
RT,问题来源于
DGP-Studio/Snap.Hutao.Docs#119 (comment)
搜索出的两个标题显示的内容相同,但实际上被重定向到了两个不同的三级标题。
显示三级标题(可选)
No response
No response
Redirect popup can not unlock page scrolling when navigating.
npm
.
When on production, plugin-baidu-analytics complains Uncaught (in promise) Error: useClientData() is called without provider.
and doesn't load script.
https://stackblitz.com/edit/vuepress-demo-19211d7
To reproduce:
pnpm install && pnpm build && pnpm preview
pnpm
System:
OS: Windows 11 10.0.22621
CPU: (6) x64 AMD Ryzen 5 4500U with Radeon Graphics
Memory: 1.16 GB / 7.23 GB
Binaries:
Node: 20.10.0 - C:\nodejs\node.EXE
Yarn: 1.22.22 - ~\AppData\Local\pnpm\yarn.CMD
npm: 10.2.3 - C:\nodejs\npm.CMD
pnpm: 8.15.3 - ~\AppData\Local\pnpm\pnpm.CMD
bun: Not Found
Utilities:
Git: 2.37.3.
Browsers:
Chrome: Not Found
Edge: Chromium (122.0.2365.92), ChromiumDev (123.0.2420.10)
npmPackages:
@vuepress/bundler-vite: 2.0.0-rc.8 => 2.0.0-rc.8
@vuepress/bundler-webpack: Not Found
@vuepress/cli: Not Found
@vuepress/client: Not Found
@vuepress/core: Not Found
@vuepress/markdown: Not Found
@vuepress/shared: Not Found
@vuepress/utils: Not Found
vue: ^3.4.21 => 3.4.21
vue-router: Not Found
vuepress: 2.0.0-rc.8 => 2.0.0-rc.8
plugin-pwa
replaces the viewport
meta element forces user-scalable=no
to be set.
https://github.com/vuepress/ecosystem/blob/3bddc56a1d33707fc2e50674bb2ba678de53fc1b/plugins/plugin-pwa/src/node/injectLinksToHead.ts#L89C64-L89C80
Is there a reason we needed to do this? It violates the WCAG standard to not disable zoom and scaling features of the browser for low vision users.
https://dequeuniversity.com/rules/axe/4.8/meta-viewport?application=AxeChrome
https://www.boia.org/blog/web-accessibility-tips-dont-disable-zooming-yes-even-on-mobile
pnpm
NA
The page has a table with display: block
and overflow-x: scroll
, and the table is having long content which it's horizontal scrollable.
If any external link is outside the initial width of page, the external link will break the page layout:
The whole page is scrollable
If setting display: none
to .external-link-icon-sr-only
, then the page layout becomes normal again.
I would prefer this is a bug.
Not needed
pnpm
Not related
When copying the text does not work: undefined
https://gravitlauncher.com/install/
yarn
Sorry. i'm use yarn manager
`vuepress: command not found`
Dequeue/Axe recommends not to include alt text on an image that is also already displayed next to it. A screen reader will then read it twice.
https://dequeuniversity.com/rules/axe/4.8/image-redundant-alt?application=AxeChrome
Currently the brand image in the default theme will also use the site title it displays as the alt text of the brand image.
I think we should add a theme option to specify the brand image alt text and default it to an empty string but still render the attribute like Dequeue recommends.
We will also need to make sure this works appropriately with screen readers when in a mobile resolution where the brand image is displayed but the title is hidden.
No response
No response
Provide client config file for theme and plugins, so that user can modify client-only options to get an HMR instead of a server restart.
See vuepress/core#914 (comment)
No response
No response
I receive many users complaining that they are unable to use our tools to build a existing markdown folder in their project.
Mainly because we do not have full support of GFM.
It's good for us to support "standard" markdown files in GitHub.
Add a new gfm
option
use vuepress-plugin-md-enhance
with { gfm: true }
option
See https://ecosystem.vuejs.press/
https://ecosystem.vuejs.press/
pnpm
Not needed
want to explicitly set the id attribute of headings from the Markdown document, for example to keep them consistent across translations.
No response
No response
support safari and firfox Android
use svg attr
No response
No response
No control over generated content for robots.txt
If it exists under the public directory, it should not be generated or provide the option to generate content.
If it exists under the public directory, it should not be generated
plugins/plugin-seo/src/node/generateRobotsTxt.ts
no
Dequeue recommends all HTML landmarks have a unique role, title or aria-label. If the page is using the auto link page nav there are two nav elements on the page with the same landmark role.
https://dequeuniversity.com/rules/axe/4.8/landmark-unique?application=AxeChrome
NA
npm
NA
Shikiji is a pure esm rewrite of shiki, with some improvement.
Migrate from shiki to shikiji. No need to update the plugin name, as shikiji might become shiki 1.0 in the future
No response
No response
a11y issue for redirect modal
Not needed
npm
.
We might have other alternative ones now.
replace workbox
No response
No response
On 2rc0 and prior versions, it was possible to use relative paths as a source for navbar/sidebar's text generation as described here:
This is broken somewhere between 2rc0 and 2rc9; it doesn't throw any warning or error if a title isn't found, it just sets to <page>.html
.
In our case, it's not exactly feasible to use absolute paths, as this would break our translation platform, Crowdin, in a configuration where the default language is at the root of the site and the translated languages are in a subdirectory.
https://github.com/lifehackerhansol/dsi.cfw.guide/tree/vuepress-2rc9, with submodule https://github.com/lifehackerhansol/emiyl-theme-2
npm
$ ./node_modules/.bin/vuepress info
System:
OS: Linux 6.5 Ubuntu 23.10 23.10 (Mantic Minotaur)
CPU: (16) x64 AMD Ryzen 7 3800X 8-Core Processor
Memory: 116.61 GB / 125.71 GB
Shell: 5.2.15 - /bin/bash
Binaries:
Node: 20.12.2 - ~/.nvm/versions/node/v20.12.2/bin/node
Yarn: Not Found
npm: 10.5.0 - ~/.nvm/versions/node/v20.12.2/bin/npm
pnpm: Not Found
bun: Not Found
Utilities:
Git: 2.40.1 - /usr/bin/git
Browsers:
Chrome: Not Found
npmPackages:
@vuepress/bundler-vite: 2.0.0-rc.9
@vuepress/bundler-webpack: ^2.0.0-rc.9 => 2.0.0-rc.9
@vuepress/cli: 2.0.0-rc.9
@vuepress/client: 2.0.0-rc.9
@vuepress/core: 2.0.0-rc.9
@vuepress/markdown: 2.0.0-rc.9
@vuepress/shared: 2.0.0-rc.9
@vuepress/utils: 2.0.0-rc.9
vue: 3.4.25
vue-router: 4.3.2
vuepress: 2.0.0-rc.9 => 2.0.0-rc.9
create-vuepress
does not support VuePress 2 yet.
create-vuepress
No response
No response
Add transformers support in shiki plugin
Currently our shiki plugin is pretty minimal. This FR is to support transformers
option.
Also we need to update the docs to show how to make use of a transformer. For example, twoslash
copy code 无法在微信H5中使用,点击无响应
但通过 extendsMarkdown的方式 注入 markdown-it-copy 可以成功复制,但UI 需要自定义调整,有点麻烦
Add some helper functions for developer.
They might be commonly used while developing plugins and themes, but not part of functionality of vuepress core.
A new @vuepress/helper
package.
Proving @vuepress/helper/noopModule
and @vuepress/helper/noopComponent
for empty pkg and vue component.
This can be useful when developers want to do tree-shaking with alias
.
We provide a lot of bundler related files, as it's likely for a plugin or theme to modify bundler config.
Writing codes directly can be annoying, see the following example:
- // extends options of @vuepress/bundler-vite
- if (app.options.bundler.name === '@vuepress/bundler-vite') {
- bundlerOptions.vuePluginOptions ??= {}
- bundlerOptions.vuePluginOptions.template ??= {}
- bundlerOptions.vuePluginOptions.template.compilerOptions ??= {}
- const isCustomElement = bundlerOptions.vuePluginOptions.template.compilerOptions.isCustomElement
- bundlerOptions.vuePluginOptions.template.compilerOptions.isCustomElement = (tag) => {
- if (isCustomElement?.(tag)) return true
- if (tag === 'my-custom-element') return true
- }
- // extends options of @vuepress/bundler-webpack
- if (app.options.bundler.name === '@vuepress/bundler-webpack') {
- bundlerOptions.vue ??= {}
- bundlerOptions.vue.compilerOptions ??= {}
- const isCustomElement = bundlerOptions.vue.compilerOptions.isCustomElement
- bundlerOptions.vue.compilerOptions.isCustomElement = (tag) => {
- if (isCustomElement?.(tag)) return true
- if (tag === 'my-custom-element') return true
- }
+ addCustomElement(bundlerOptions, app, 'my-custom-element')
The main problem is that we need to ensure the parent scope of our config exists and we should not drop any existing config. So that's our helper goal.
Docs already exists at https://shared.vuejs.press/node/bundler.html (published as vuepress-shared
)
For seo feed or blogging, we need a concept called excerpt to describe a page main content using html, while VuePress2 remove this from core.
A good generator should do the following things:
<RouterLink>
to <a>
tag and so on.So that's getPageExcerpt
for.
Some websites that are not open to the public and do not want to be indexed by search engines.
interface SeoPluginOptions {
/**
* Whether to block search engine indexing
*
* 是否阻止搜索引擎收录
*/
block?: boolean
}
-> robots.txt
:
User-agent: *
Disallow: /
No response
No response
We might need to build a separate docs for ecosystem.
Maybe deployed at https://ecosystem.vuejs.press
No response
No response
This package should support common languages repl out of box.
It should try to be tree-shakable, and allow users adding new one themselves.
No response
No response
When I use vue 3.4.0 and then run pnpm docs:dev
, and then open my local vuepress site, the navbar and sidebar will lose their responsive capability.
当我用 vue 3.4.0 并且运行 pnpm docs:dev
,再打开本地的 Vuepress 网页时,顶部导航和侧边栏都会失去它们的响应性。
The guide in guide of vuepress tells me to install vue normally like pnpm add -D vue
在官方文档中提到的方法,只是简单地让我直接安装 vue——pnpm add -D vue
This situation is the same in higher version (3.4.14, which is the lastest version)
同样的情况(指失去响应性)当然也发生在了更高版本。
However, if i install vue 3.3.13 like the official documents do, it will run responsively.
然而,如果我像官方文档里写的一样,为我的 vuepress 安装 vue 3.3.13,又可以成功运行了。
This problem may caused by the update of vue 3.4, which added some breaking features.
这可能是因为 vue3.4 的更新带来了一些新特性。
https://github.com/LdoDoeg222/vuepress-bugrepo
pnpm
System:
OS: Windows 10 10.0.19045
CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
Memory: 5.79 GB / 15.80 GB
Binaries:
Node: 18.14.2 - D:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 9.5.0 - D:\Program Files\nodejs\npm.CMD
Utilities:
Git: 2.39.0.
Browsers:
Chrome: 94.0.4606.71
Edge: Chromium (120.0.2210.133)
npmPackages:
@vuepress/bundler-vite: 2.0.0-rc.0 => 2.0.0-rc.0
@vuepress/bundler-webpack: Not Found
@vuepress/cli: Not Found
@vuepress/client: 2.0.0-rc.0 => 2.0.0-rc.0
@vuepress/core: 2.0.0-rc.0 => 2.0.0-rc.0
@vuepress/markdown: Not Found
@vuepress/plugin-active-header-links: Not Found
@vuepress/plugin-back-to-top: Not Found
@vuepress/plugin-container: Not Found
@vuepress/plugin-docsearch: Not Found
@vuepress/plugin-external-link-icon: Not Found
@vuepress/plugin-git: Not Found
@vuepress/plugin-google-analytics: Not Found
@vuepress/plugin-medium-zoom: Not Found
@vuepress/plugin-nprogress: Not Found
@vuepress/plugin-palette: Not Found
@vuepress/plugin-prismjs: Not Found
@vuepress/plugin-pwa: Not Found
@vuepress/plugin-pwa-popup: Not Found
@vuepress/plugin-register-components: Not Found
@vuepress/plugin-search: Not Found
@vuepress/plugin-shiki: Not Found
@vuepress/plugin-theme-data: Not Found
@vuepress/plugin-toc: Not Found
@vuepress/shared: Not Found
@vuepress/theme-default: 2.0.0-rc.0 => 2.0.0-rc.0
@vuepress/utils: Not Found
vue: 3.4.0 => 3.4.0
vue-loader: Not Found
vue-router: Not Found
vuepress: 2.0.0-rc.0 => 2.0.0-rc.0
vuepress-vite: Not Found
vuepress-webpack: Not Found
> [email protected] docs:build C:\Users\msqlx\Documents\workdir\blog
> vuepress build src
@vuepress/plugin-blog: ⚠ Overriding existing page:
/posts/
✔ Initializing and preparing data - done in 29.17s
⠧ Compiling with vite
(!) Some chunks are larger than 1024 kB after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
✔ Compiling with vite - done in 148.13s
✖ Rendering 106 pages - failed in 11.10s
ReferenceError: __COMMENT_OPTIONS__ is not defined
at file:///C:/Users/msqlx/Documents/workdir/blog/node_modules/.pnpm/@[email protected]_@[email protected][email protected]/node_modules/@vuepress/plugin-comment/lib/client/helpers/comment.js:2:24
at ModuleJob.run (node:internal/modules/esm/module_job:222:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:323:24)
at async file:///C:/Users/msqlx/Documents/workdir/blog/node_modules/.pnpm/@[email protected]/node_modules/@vuepress/bundler-vite/dist/index.js:407:30
at async file:///C:/Users/msqlx/Documents/workdir/blog/node_modules/.pnpm/@[email protected]/node_modules/@vuepress/utils/dist/index.js:58:20
at async build (file:///C:/Users/msqlx/Documents/workdir/blog/node_modules/.pnpm/@[email protected]/node_modules/@vuepress/bundler-vite/dist/index.js:396:3)
at async CAC.<anonymous> (file:///C:/Users/msqlx/Documents/workdir/blog/node_modules/.pnpm/@[email protected]/node_modules/@vuepress/cli/dist/index.js:231:3)
ELIFECYCLE Command failed with exit code 1.
https://github.com/hestudio-community/blog
pnpm
> [email protected] docs:info C:\Users\msqlx\Documents\workdir\blog
> vuepress info
System:
OS: Windows 11 10.0.22631
CPU: (4) x64 Intel(R) Celeron(R) CPU J1900 @ 1.99GHz
Memory: 2.04 GB / 7.89 GB
Binaries:
Node: 20.12.0 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD
pnpm: 8.15.5 - ~\AppData\Roaming\npm\pnpm.CMD
bun: Not Found
Utilities:
Git: 2.44.0.
Browsers:
Chrome: Not Found
Edge: Chromium (123.0.2420.65)
npmPackages:
@vuepress/bundler-vite: 2.0.0-rc.9 => 2.0.0-rc.9
@vuepress/bundler-webpack: Not Found
@vuepress/cli: Not Found
@vuepress/client: Not Found
@vuepress/core: Not Found
@vuepress/markdown: Not Found
@vuepress/shared: Not Found
@vuepress/utils: Not Found
vue: ^3.4.21 => 3.4.21
vue-router: Not Found
vuepress: 2.0.0-rc.9 => 2.0.0-rc.9
At the top of a page, it's active:
After scrolling down to the first anchor, it's inactive:
https://ecosystem.vuejs.press/themes/default/locale.html
npm
N/A
Note: this is a variant of an issue which has been reported for v1 but also applies for v2: vuejs/vuepress#2398
Most modern documentations are using layout where page TOC (anchors) links are shown in a sidebar on the right and page tree (h1) is shown on the left sidebar. As of now, vuepress@next default theme shows page tree as well page TOC in-lined. Being able to display page TOC on right would reduce the left nav tree and can significantly improve the readability of docs.
Some themes, like vuepress-theme-hope, and the vuepress-plugin-right-anchor plugin offer this option, but this has become such a common feature with on-line documentations that it should be implemented to VuePress v2 default theme.
Something like what @Mister-Hope did with his theme would be just perfect - with an option like themeConfig.pageTocRightSidebar
with values true
or false
.
I have a feeling that a serious documentation contributor has lots of things to do before editing a page:
From this point of view, the "Edit this page" link (editLink
) of the default theme is a bit useless and inconvenient.
Could VuePress give a design explanation on the topic?
Or, just introduce a "View source" link in the default theme?
No response
On Microsoft Docs, the "Edit This Document" link (pencil button around the beginning of a page) is actually a "view source" link.
On MDN Web Docs, both "Source" and "Edit" links exist near the footer of a page.
When set a very long title for the project, the title can't hide correctly, and the button for the dark/light and search can be blocked
it sometimes happens on the mobile devices
yarn
build correctly
We are in the process of creating a new default theme for the VuePress 2, which will replace the old default theme, with the old theme being renamed to @vuepress/theme-legacy
.
We will list the updated content in this issue, discussing the differences between old and new themes, compatibility solutions, and other updates related to vuepress upstream and downstream.
The new theme will follow the same style as the default theme of VitePress.
SiteTtitle and logo: delete home / logo / logoDark / logoAlt
, use siteTitle / logo / logoLink
instead.
Nav:
NavItem[]
, children
was deprecated, use items
insteadrepo
, use socialLinks
insteadcolorMode / colorModeSwitch
, use appearance
insteadSidebar:
auto
to structure
children
was deprecated, use items
insteadDocFooter: latestUpdated
support lastUpdatedFormatOptions
Code Block: Use shiki
as the default highlighting. support line highlighting
, colors diff
errors and warning
focus
containers: support tip / info / warning / danger / important
, and github alerts.
layout
with pageLayout
in VitePress, as layout
is already used for other purposes in VuePress.outline
to control the display levels of the TOC
within the page. etc. [2, 3]
Note
More content will continue to be added during the development period.
Currently working on vuepress/ecosystem branch:theme-default .
No response
No response
Add e2e testings for ecosystem repo
Use cypress for e2e testing like the core repo.
No response
No response
The default icon, is emm....
Procide a icon option for people to inejct svg strings or html string to customize back-to-top plugin.
No response
No response
The blog plugin can update related temp files correctly, but the page hot reload will throw an error, users must manually click refresh to let it work.
As per #110, all paths in the theme configuration must be hardcoded. This makes it slightly difficult to manage several translated locales as all of them must be manually handled by the end user.
Since the i18n page on VuePress and default theme locale documentation both suggest that a static path has to be passed anyway, I feel that it would make sense if the configurations themselves do not need to have the locale path hardcoded for navbar
and sidebar
, and be automatically prepended, reducing complexity on the user side.
For instance, if a user defines:
sidebar: {
'/get-started.html': [
...
then it can be interpreted as /zh_CN/get-started.html
.
At the moment, it is also impossible to use a variable for items in sidebar
for some reason, i.e. this isn't possible and throws some error:
const locale = 'zh_CN';
sidebar: {
`/${locale}/get-started.html`: [
...
It would be nice if this was supported, as it would be easier to enable languages by just changing $locale
somewhere.
No response
I'm trying to build my project with plugin-feed, only to face this problem.
D:\Programming\blog\blog>yarn build
yarn run v1.22.22
$ vuepress build .
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './shared' is not defined by "exports" in D:\Programming\blog\blog\node_modules\vuepress\package.json imported from D:\Programming\blog\blog\node_modules\@vuepress\plugin-feed\lib\node\feedPlugin.js
at new NodeError (node:internal/errors:387:5)
at throwExportsNotFound (node:internal/modules/esm/resolve:365:9)
at packageExportsResolve (node:internal/modules/esm/resolve:649:3)
at packageResolve (node:internal/modules/esm/resolve:833:14)
at moduleResolve (node:internal/modules/esm/resolve:901:20)
at defaultResolve (node:internal/modules/esm/resolve:1115:11)
at nextResolve (node:internal/modules/esm/loader:163:28)
at ESMLoader.resolve (node:internal/modules/esm/loader:841:30)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:40)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Here's the content in my config.js
:
plugins: [
...
feedPlugin({
hostname: 'https://www.yixiangzhilv.com',
}),
...
],
https://github.com/yxzlwz/blog.git
yarn
System:
OS: Windows 10 10.0.22631
CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
Memory: 5.24 GB / 15.87 GB
Binaries:
Node: 16.19.0 - ~\AppData\Local\Temp\yarn--1712199097396-0.7939861618239752\node.CMD
Yarn: 1.22.22 - ~\AppData\Local\Temp\yarn--1712199097396-0.7939861618239752\yarn.CMD
npm: 8.19.3 - D:\nodejs\npm.CMD
Utilities:
Git: 2.37.3.
Browsers:
Chrome: Not Found
Edge: Chromium (123.0.2420.65)
npmPackages:
@vuepress/bundler-vite: 2.0.0-beta.66
@vuepress/bundler-webpack: 2.0.0-beta.66
@vuepress/cli: 2.0.0-beta.66
@vuepress/client: 2.0.0-beta.66 (2.0.0-beta.64)
@vuepress/core: 2.0.0-beta.66 (2.0.0-beta.64)
@vuepress/markdown: 2.0.0-beta.66 (2.0.0-beta.64)
@vuepress/plugin-active-header-links: 2.0.0-beta.66
@vuepress/plugin-back-to-top: 2.0.0-beta.66
@vuepress/plugin-container: 2.0.0-beta.66
@vuepress/plugin-docsearch: 2.0.0-beta.66
@vuepress/plugin-external-link-icon: 2.0.0-beta.66
@vuepress/plugin-git: 2.0.0-beta.66
@vuepress/plugin-google-analytics: 2.0.0-beta.64 => 2.0.0-beta.64
@vuepress/plugin-medium-zoom: 2.0.0-beta.66
@vuepress/plugin-nprogress: 2.0.0-beta.66
@vuepress/plugin-palette: 2.0.0-beta.66
@vuepress/plugin-prismjs: 2.0.0-beta.66
@vuepress/plugin-pwa: Not Found
@vuepress/plugin-pwa-popup: Not Found
@vuepress/plugin-register-components: 2.0.0-beta.66
@vuepress/plugin-search: 2.0.0-beta.66
@vuepress/plugin-shiki: Not Found
@vuepress/plugin-theme-data: 2.0.0-beta.66
@vuepress/plugin-toc: Not Found
@vuepress/shared: 2.0.0-beta.66 (2.0.0-beta.64)
@vuepress/theme-default: 2.0.0-beta.66
@vuepress/utils: 2.0.0-beta.66 (2.0.0-beta.64)
vue: 3.3.4 (3.4.21)
vue-loader: 17.2.2
vue-router: 4.2.4
vuepress: 2.0.0-beta.66 => 2.0.0-beta.66
vuepress-vite: 2.0.0-beta.66
vuepress-webpack: Not Found
Currently the template of create-vuepress
package is not align with the getting started guide of our docs. The source dir should be docs
instead of src
pnpm create-vuepress vuepress-starter
pnpm
noop
The appearance of currect default theme is really "aweful" comparing to:
Mainly because it lacks some basic function:
Any poor appreance in:
Repo link
Editlink
Page nav
Navbar dropdown
adding animation such as http://vuepress-theme-hope.github.io/v2/ (important)
Current menu is too "Hard"
Sidebar
Have to say that the above tool listed all have better outlook
...
A good official theme is important for such tools to atract users. People probably won't choose a tool which it's project docs have the poorest appearance.
Implement the above ones.
No response
No response
To support data-title
attr
No response
No response
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.