27 Jan 2023
sena_kun oooh 14:00 <- that's how it was Supposed(tm) to look like
[Coke] rf, think Just waiting for food analyst to take a look at it 20:32
Apparently speech to text has some problems with Richards nickname
Thanks for time to submit the PR I really appreciate it 20:33
Dumb come from somebody who doesn't use themes how do I test the themes out in chro 20:35
dumb question, i meant
I guess that's my last send using dictation on Mac..
rf Absolutely haha 20:41
[Coke]: What you need to do is just compile the css and restart 20:48
I have no idea how to make it auto-update I think finanalyst is big time caching 20:49
basically ./update-css <MY-MODULE>
Sorry for late response had to run to a meeting
28 Jan 2023
NemokoschKiwi do you all have no problems with the built-in search? (not the extended one) 13:39
I'm surprised nobody reported things I'm experiencing with it 13:40
like it opens slightly off, there are scrollbars in both directions and sometimes if you click them, the whole thing will just close
coleman fin and I reviewed the site build. The build environment I set up for Altai-Man's site 8 months ago came in handy, and it was more straightforward than anticipated 16:16
I have some notes that I need to process into scripts. 16:17
raschip The new doc site is looking very good
rf_ How is the site being deployed? Bare metal or docker or ? 16:22
raschip What's the intent of the new docs instance? I'm willing to contribute to the docs and maybe get into Cro, should I use the instance of the new doc website for reading the docs and report issues or it's meant just for work on the site itself for now? 16:36
rf Its intended to replace the existing docs when its done 16:39
That's all I know D:
coleman The first method of deployment will likely be pure static files in an nginx container 16:46
if the docs build is successful, there's a folder called rendered_html, which should be a totally self-contained web root
After that is working well, we should create a Cro-based container as well 16:48
Cro is a dependency of the build, but at the tail end of the build it's possible to serve with any web server, too 16:49
rf I see 16:52
github.com/Raku/doc-website/pull/45 Fixup table styles, requested by Finanalyst 17:06
I think we should probably do the buttons at some point too. 17:07
coleman Added an ssh deploy key to doc-website, doc soon, as well 18:08
some may get an email from GitHub about it. That's me.
Automated builds are still a WIP, but here is a container using static assets compiled from main 21:40
podman run -p 8080:80 --name raku quay.io/colemanx/raku-doc-website
that should be a public image.
I do not know if we have an official registry, yet, or what it ought to be
I'm going to proceed with just my own stuff; then work with infra team to factor it out into something shared 21:41
29 Jan 2023
rf While i'm in this code would anyone be against me sprucing up the JavaScript 23:38
It's fairly dated
coleman Open an issue with some suggestions 23:40
sprucing up is ambiguous
I'd be against introducting SPA-style frameworks, but in favor of adopting vanilla JS where it can replace existing jQuery, etc. 23:41
rf Basically just turning var to const, and using forEach inplace of imperative loops 23:44
coleman var->const sounds find 23:47
go for it; but perhaps submit separate PRs for the cleanup stuff 23:48
makes that sort of thing easier to review
rf Yeah, Im just having a lot of trouble figuring out where I need to look for the stuff I am trying to fix 23:49
Haven't worked in an older JS codebase in a long time :L 23:51
30 Jan 2023
coleman Go for small, incremental changes so it won't be a shock to others; thanks for jumping in 00:11
rf Yeah, I'm trying to figure out the styling for the searchbar auto complete, but it seems to be set in both CSS and JS 00:12
NemokoschKiwi github.com/Raku/doc-website/discussions/51 since I'm this kind of GH Discussions freak, I feel obliged to advertise this question a little bit. Just to raise awareness. 15:38
[Coke] Did you convert that from the issue? thanks. 15:51