-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Can I help maintain #1187
Comments
Initially, you could try help with |
Will do.
…On Wednesday, February 15, 2023, Denis Pushkarev ***@***.***> wrote:
Initially, you could try help with help wanted
<https://github.com/zloirock/core-js/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22help+wanted%22>
issues -)
—
Reply to this email directly, view it on GitHub
<#1187 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATOOUFWHQQYOCSJ4PE4PMVLWXTJKLANCNFSM6AAAAAAU4ME5EA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Same here I will try some |
Same here. I saw the first issue, and I can create a rudimentary website to host the documentation. But I noticed there is open pr. would you still like someone to contribute to it? to build static site with something like Astro? |
@Bekacru it will be required, but not right now - initially, I should think about the static site generator and the frame of the site. Now you could help with docs in the repo. |
I will also help contribute by picking up some help wanted issues |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Let's move the discussion about docs improvement to #1053. |
Yeah
…On Monday, February 20, 2023, Denis Pushkarev ***@***.***> wrote:
Let's move the discussion about docs improvement to #1053
<#1053>.
—
Reply to this email directly, view it on GitHub
<#1187 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATOOUFQK5Y64VHUUSN2SGWDWYNWFBANCNFSM6AAAAAAU4ME5EA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
First, Vuepress v1 is no longer maintained: vuepress-theme-hope/vuepress-theme-hope#1535 Regarding the stabilitymany projects are already using v2, and I personally have been using it for a while and haven't encountered breaking changes. Vuepress or Vitepress?Vuepress-theme-hope provides very comprehensive features, and Vuepress plug-in ecology is also very good, basically can meet all the needs So, in summary I personally recommend using Vuepress v2
|
Ok, sounds good. I didn't know that so thanks :).
…On Monday, February 20, 2023, 冰雪殇璃陌梦 ***@***.***> wrote:
Never mind, vitepress is still in alpha. How about vuepress v1?
First, Vuepress v1 is no longer maintained: vuepress-theme-hope/vuepress-
theme-hope#1535
<vuepress-theme-hope/vuepress-theme-hope#1535>
Second, v2 is better than v1 in terms of development experience (mainly
thanks to the speed of vite)
Regarding the stability
many projects are already using v2, and I personally have been using it
for a while and haven't encountered breaking changes.
Vuepress or Vitepress?
Vuepress-theme-hope provides very comprehensive features, and Vuepress
plug-in ecology is also very good, basically can meet all the needs
But I did not find so comprehensive vitepress theme, many features may
have to write our own.
So, in summary I personally recommend using Vuepress v2
—
Reply to this email directly, view it on GitHub
<#1187 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATOOUFWBSQR7HL244XTNPTDWYNYQXANCNFSM6AAAAAAU4ME5EA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I would like to try some help wanted issues, too |
yeah no i was such an idiot and a skid back when i made this i'm closing this issue |
I won't be able to be on too much but I'll be able to be on at least a couple hours per day. I really really really really want to help. I can tell you need it from the readme.
The text was updated successfully, but these errors were encountered: