| 22 May 2022 | |||
| patrickb | Maybe a fix could be to have the menu auto-retract or start retracted, once the screen is small enough so the menu starts to overlay the content. | 13:58 | |
| [Coke] | in my continuing may adventures, will be offline a bit mid week, mostly wednesday. | 16:46 | |
| patrickb: if you can make sure there's a ticket that reflects that on github.com/Altai-man/docs.raku.org/issues, that would be helpful | 16:51 | ||
| sena_kun just fixed 3 simpler tickets and deploying in progress | 16:53 | ||
| in a better version of reality I'd took a look at what to do with support of the invalid URLs of the old website and the Documentable PR | 16:54 | ||
| [Coke] | sena_kun++ | 17:00 | |
| uzl[m] | Was the meeting recorded? | 21:47 | |
| .tell [Coke] I can volunteer to test Altai-man 's version of the doc, although I am not sure what that entails yet | 21:49 | ||
| 23 May 2022 | |||
| [Coke] | recorded, no, minutes, yes | 13:30 | |
| coleman put them on the wiki, should be on the menu on the right | |||
| coleman, sena_kun & I had homework; if you want to help, we definitely need help with new docs, editing, testing. | |||
| brb. | 13:31 | ||
| for testing: test navigation. feedback on CSS, any JS errors, rendering bugs... e.g. more like "this doesn't render on <screen>" instead of "I would like the color palette if it were more green." | 13:53 | ||
| coleman: any luck building either site yet? | 14:41 | ||
| I don't know if this was ever explicitly said, but: we're moving forward with the new site; it will help us address *so many* open tickets in the repo. | 14:42 | ||
| if anyone else wants to provide testing on the site, please reach out to myself (or sena_kun), and we'll you the URL/issue repo. Looking primarily for remaining functional issues as opposed to purely stylistic. | 14:43 | ||
| One thing about the new site that is different content wise is the groupings (used mainly for search headings). Feedback on those also welcome, though the goal there is to move to a new, streamlined structure, not follow the existing ad-hoc settings we've accumulated over the years. | 14:48 | ||
| test | 15:36 | ||
| [Coke] | Documentation Channel for #raku | This channel is logged | github.com/raku/doc/wiki | ||
| [Coke] | Documentation Channel for #raku | This channel is logged | Roadmap: github.com/raku/doc/wiki | 15:41 | |
| [Coke] | I know several of the issues in raku/doc are resolved by the new site work; is there a canonical list? We can add a tag to the tickets, but the tag will be obsolete soon. | 16:23 | |
| when reviewing the new site, we should also review github.com/Raku/doc/labels/site to see if there are any to add to the list. | 16:24 | ||
| Does the new site have the all-in-one page? | 16:26 | ||
| Altai-man | [Coke], most of the things assigned to me, no canonical list. | 16:40 | |
| >all-in-one page | |||
| no | |||
| re list: I can write one if needed | |||
| I think the old one has it mostly by accident, I'm not sure what's the status of Pod::To::BigPage now. | 16:41 | ||
| [Coke] | well, it won't be a requirement to go live, but we do want to get something like it back. (maybe we go directly to "build an ebook format") as a different build. | 16:45 | |
| Altai-man | I agree. | 16:55 | |
| [Coke] | m: say Compiler.new.^methods; #ahh | 17:58 | |
| ww | |||
| coleman | I have only tried the old site; I will try the new site after work today | 18:46 | |
| What does "all in one page" mean? | 18:52 | ||
| [Coke] | all the content, single html file | 19:11 | |
| was theoretically a stopgap on the way to an e-reader version | |||
| coleman | cool, that's neat | ||
| [Coke] | reading a bit into epub3 format, looks like we could probably easily take a "html with everything" and throw it into an epub | 19:23 | |
| Long term would be nice to have a specific ordering for that, maybe with some additional content to at least explain "this isn't meant to be read as a book" | 19:24 | ||
| trying the docker install now (doing the initial build takes a second) | 22:54 | ||
| (for new-site) | 22:55 | ||
| apparently haven't run docker on this mac in years | |||
| so if there's an update to the docs repo, what's the steps to re-update the site? we wouldn't need a full rebuild of the docker image, would we? | 23:01 | ||
| "updating rea mirror" - probably want to add --/rea to all the zef steps | 23:02 | ||
| 24 May 2022 | |||
| coleman | The kind of artifact we should yield kind of depends on what ops wants | 00:25 | |
| [Coke] | ok, the 2-step docker process - the build went ok, I think; the run step doesn't seem to be doing anything. | 01:58 | |
| no output on the run command, nothing responding on port 10K | |||
| also: when did telnet stop being a thing, I missed the memo. :| | |||
| curl localhost:10000/ -> empty reply | 01:59 | ||
| tried opening a shell in the running 'next-docs' but it is (of course) very barebones. (couldn't find 'ps') | 02:23 | ||
| ... ok, restarted it at least once, tried going in with a shell, tried ... opening in the browser again and I am looking at the docs locally in the browser. :) | 02:24 | ||
| Can we get github.com/Raku/doc/issues/4072 in the new site? would be fine if it was a separate, unlinked URL and not on each page. | 02:50 | ||
| 25 May 2022 | |||
| coleman | Haven't had a chance to try to build the new site yet; will do it as soon as I can | 17:23 | |