Alexis

i'm happy to do all this once a decision is made on whether or not to split the "Firewalls" section as per #508.

@Duncaen: Do you feel a sitemap is still needed for accessibility purposes? The sidebar seems to essentially be a sitemap, and can be tabbed through (after first tabbing through the...

In a conversation on IRC, @Duncaen indicated he'd like a page with links to each section of the Handbook, accompanied by when that section was last updated. i'd like to...

Thanks for opening this issue! i'd definitely like the Handbook to be available in multiple languages. Thank you also for registering your willingness to work on a Polish translation. :-)...

@kuchikuu: Thanks for sharing your thoughts on the issue space! Something i'd like to note is that all of the people working on Void are volunteers - we're doing this...

Another issue that comes to mind is reviews of PRs for translations. i know only smatterings of languages other than English; certainly not enough to be able to do translation...

@travankor: > I'm not a fan of "forking" the repo for translated copies; this will result in fragmentation and in inconsistent quality standards -- these were the reasons why Void...

@ericonr: Thanks, PR updated.

#416 is now basically ready to be merged, modulo any feedback from @void-linux/pkg-committers. However, some things to follow up in the future: * The ToC structure follows LaTeX conventions, rather...

@bobertlo: Thanks for the feedback, and the suggestions. :-) LaTeX provides defaults for each `documentclass` (such as `article` or `book`) that are considered "good typographic style" for that particular class,...