https://ethercalc.net/dc4vcnnl8zv0
people.
danielsidhion/fricklerhandwerk.

Does it support GitHub-flavored markdown? [nrd:] If we implement it
Can we render it to multiple pages? [nrd:] If we implement it
How can someone navigate the rendered docs? [nrd:] Single-page output with only immediate children visible on each section

we are increasingly concerned that people don't fucking read what we say. gfm is supported (the manual uses gfm tables!), multipage rendering is in use right now, tocgen is configurable.

infinisil asked as to come back to answer questions regarding the tooling, we've yet to hear one. should we just fucking leave again?

In reply to @pennae:matrix.eno.space

https://ethercalc.net/dc4vcnnl8zv0
people.
danielsidhion/fricklerhandwerk.

Does it support GitHub-flavored markdown? [nrd:] If we implement it
Can we render it to multiple pages? [nrd:] If we implement it
How can someone navigate the rendered docs? [nrd:] Single-page output with only immediate children visible on each section

we are increasingly concerned that people don't fucking read what we say. gfm is supported (the manual uses gfm tables!), multipage rendering is in use right now, tocgen is configurable.

infinisil asked as to come back to answer questions regarding the tooling, we've yet to hear one. should we just fucking leave again?

gfm is supported (the manual uses gfm tables!)

gfm tables isn't the complete set of gfm, and from what I saw the current code doesn't support the full set (more importantly, doesn't support the github note/tip/warning box style).

multipage rendering is in use right now

The manuals aren't rendered in multiple pages and we have already established that it's not about just toggling a switch. If you render the manual in multiple pages, links break. It requires more effort than just a switch.
When I say multipage, I say the way that we expect chapers and sections to be in their own pages.

tocgen is configurable

It's already understood that we can change nrd's implementation the way we see fit, but for that particular line what matters is what the tool currently does

infinisil asked as to come back to answer questions regarding the tooling, we've yet to hear one

As for this, I wanted to have that spreadsheet filled out before engaging in review, and then in its discussion, where questions and discussion about the tooling would be most important (and having the fresh discussion would be helpful IMO). I haven't had enough time to dedicate lately to filling out the sheet. It's something that will get done eventually as I put more effort in.

In reply to @shalokshalom:kde.org
Ah, a Hickey video I dont know yet ^^

In reply to @danielsidhion:nixos.dev
(I just updated the spreadsheet to reflect that gfm tables are supported for nrd, and the rest of it if we implement it. I think it's a better reflection of the facts. Thank you again for calling it out)

In reply to @efx:matrix.org
silly question: as a contributor, when I make changes to a nixpkgs language markdown file, how do I easily test the manual generates correctly?

cd doc
nix-shell
devmode

In reply to @efx:matrix.org
silly question: as a contributor, when I make changes to a nixpkgs language markdown file, how do I easily test the manual generates correctly?

cd doc
nix-shell
devmode

In reply to @fricklerhandwerk:matrix.org

cd doc
nix-shell
devmode

In reply to @shalokshalom:kde.org
where can I see this spreadsheet please?