Started, and what's next

[clsty]

The website is nearly ready now, and it feels great after days of work finally becomes fruit.

So, what's next?

Finish for Migration

• Status

@end-4 If you're satisfied, then it's time to eventually finish migration.

i.e. The built-in wiki and README of https://github.com/end-4/dots-hyprland are ready to be removed in favor of this one, and then the URL https://end-4.github.io/dots-hyprland-wiki should be added to suitable places.

l10n (optional)

• Status

The site supports multi language, but it needs manual translation first.
I guess it will be fast if use AI to translate and then manually check and modify.

Of course, a person is capable to do translation only when the target language is their native language, or they are really experienced on this language.

Write Dev notes (optional)

• Status

@end-4 The part of Dev notes is far from complete.
You may write needed content when you have time.

WS over 10 (optional)

• Status

The Usage does not contains "WS over 10" things currently.
@midn8hustlr Since you're the main contributor for this workflow, I sincerely invite you to write this part and submit a PR, if you'd like to.
Thanks in advance!

---

That's it for now.
Happy Chinese New Year!

[end-4]

wonderful!

The wiki

• I like it, but I'll just have material colors like my rice

Translation

• Let's not use automated translation. I don't want weird, low-quality stuff
• I can do Vietnamese. And I assume you're doing Chinese?

Dev notes

• I like the idea. I'll do it

overview for workspace 11+ is broken btw

[clsty]

I like it, but I'll just have material colors like my rice

Sure, feel free to edit the themes. The theme originally comes from the wiki site of my project, I just copied them here.

Let's not use automated translation. I don't want weird, low-quality stuff

I actually meant "assisted", not "automated". If a person speaks the target language every day, then I think it's ok if the person read the whole result and modified every parts that's not suitable, until the person feels nothing wrong.

And as for AI, I actually refer to ChatGPT and similar things. They actually do a much better translation than previous AI translators.
Linux CN had used them in translation and I've read many of them. As a native speaker of Chinese, I should say that it's hard to tell if the articles is or not translated by ChatGPT.

I can do Vietnamese. And I assume you're doing Chinese?

Yes, you're right.

overview for workspace 11+ is broken btw

Hmmm... it seems worky for my PC, but maybe I just don't know what is "worky" at first place lol

[clsty]

@end-4 I suggest we close the built-in "Wiki" for this repo in repo settings.

Also please open "Discussions" for this repo, since the "Issues" may not be suitable for some topic.

[end-4]

I suggest we close the built-in "Wiki" for this repo in repo settings.

and that's how i discovered you could allow others to edit wiki lmao

• Discussions are already enabled

[clsty]

and that's how i discovered you could allow others to edit wiki lmao

Welp, I knew it before, but there will be no limit for editing at all so that it may risk spams.

Oh wait "collaborators only"...

Okay, but still it's not controllable-ly open to every one, similar to PR. i.e. non-collaborators can't contribute at all

[midn8hustlr]

Fabulous work @clsty

The Usage does not contains "WS over 10" things currently. @midn8hustlr Since you're the main contributor for this workflow, I sincerely invite you to write this part and submit a PR, if you'd like to. Thanks in advance!

I will be happy to contribute.
Happy Chinese New Year!

[clsty]

Discussions are already enabled

@end-4 I actually meant the discussion for this repo (wiki).

I just wanted to create a discussion and find it's not enabled here...

---

I'm confused with "Why why why why" in index.mdx. Is this really a good sentence?
Or maybe we can use "Why choose illogical-impulse?" instead ?

---

Group label on sidebar now supports i18n. You may want to add translation for vi in astro.config.mjs.

[end-4]

I actually meant the discussion for this repo (wiki).

oh okay

I'm confused with "Why why why why" in index.mdx. Is this really a good sentence?

I wanted a text that's short enough so they look good with the cards. And that "why"×4 is something unusual that makes people scroll down to read

Group label on sidebar now supports i18n. You may want to add translation for vi in astro.config.mjs.

Cool, I've found some awkwardly translated UI elements and will fix them

[end-4]

can we translate anything other than the content and sidebar?

[clsty]

can we translate anything other than the content and sidebar?

I guess so, refer to https://starlight.astro.build/guides/i18n/#translate-starlights-ui, unsure about whether this is what you wanted though.

I wanted a text that's short enough so they look good with the cards. And that "why"×4 is something unusual that makes people scroll down to read

Excuse me but, to be honest, it still seems weird to me, and I don't know whether it can truly achieve the effect you desire. Maybe we could refer to another person's opinion (esp. native English speaker).

[clsty]

I've moved the dev notes into a new group.

---

I think it's actually not necessary to translate the dev notes, because:

• A dev must be familiar with English.
• The dev notes may update much more often than other docs, so that translation update for it may cost too much time, or not up-to-date often, which makes the translated dev notes meaningless.
• I have the dev notes collapsed by default on sidebar. And, even if a person using non-English language clicks on it, it won't return 404, but just fallback to the English doc.

@end-4 If you agree with me, I'll remove the translated dev notes, only keep the English ones.
They don't contain many words in total, so it's not a big loss, and this act will surely save us lots of time in future.

[end-4]

i agree

[clsty]

@midn8hustlr This issue is 3/4 done.

I'm looking forward to your contribution on WS-over-11 workflow, and it will be the last piece to make the usage doc completed :)

[midn8hustlr]

Sorry I didn't have my laptop past week, will try to update today

[end-4]

Sorry I didn't have my laptop past week, will try to update today

you shouldn't update yet
i still haven't fixed that workflow for workspace 11+ since when I implemented animations into it

[clsty]

you shouldn't update yet
i still haven't fixed that workflow for workspace 11+ since when I implemented animations into it

Oops, sorry I didn't understand the situation clearly @midn8hustlr @end-4

Please take your time.

[end-4]

@midn8hustlr I'm happy to say that group behavior of the overview widget has now been fixed in end-4/dots-hyprland@b4fe73c
you can update now