|
Documentation Channel for #raku | This channel is logged | Roadmap: github.com/raku/doc/wiki Set by [Coke] on 23 May 2022. |
|||
|
01:01
Nemokosch joined
|
|||
| Nemokosch | I think it would be really good to get semi-formal feedback on this site proposal: github.com/Raku/problem-solving/issues/158 | 01:02 | |
| probably not the first time I'm bringing it up (and same goes for CIavash probably) | 01:03 | ||
| to declare intents, at least - is this meant to be "the new site" or not? | 01:06 | ||
|
01:29
Nemokosch left
01:37
Kaiepi left
04:04
Geth joined
04:05
lizmat joined
|
|||
| [Coke] | that's a site for raku.org \, not the docs site | 04:21 | |
| CIAvash | People have created tools for creating documentation websites with Hugo(the static site generator I used for the website). But that probably is not what you want, I think. | 04:42 | |
| As for JS, the framework I like is Svelte(svelte.dev/) which has server side rendering with Sveltekit(kit.svelte.dev/). But if that is too much and you want to use Cro for most things and use a framework for some JS things, maybe Solid framework(www.solidjs.com/) is another option; which claims to have a performance close to vanilla JS, but I have not used it myself. | 04:48 | ||
|
06:06
Geth left,
Geth__ joined,
Geth__ left,
Geth joined
08:08
Geth left
08:16
Kaiepi joined
09:18
sena_kun joined
11:07
sena_kun left
11:44
sena_kun joined
|
|||
| [Coke] | I don't know that the stuff we're doing requires high performance; I expect that for docs (and other sites) optimizing for developer time is fine | 14:18 | |
|
14:24
Altai-man joined,
sena_kun left
16:25
sena_kun_ joined
16:28
Altai-man left
17:39
Kaipei joined
17:42
Kaiepi left
18:17
sena_kun_ left
18:54
sena_kun joined
19:40
Kaipii joined
19:43
Kaipei left
22:46
sena_kun left
|
|||