!avYyleMexqjFHoqrME:nixos.org

Nix Documentation

438 Members
Discussion about documentation improvements around the Nix ecosystem94 Servers

Load older messages


SenderMessageTime
26 Jul 2023
@asymmetric:matrix.dapp.org.ukasymmetric
In reply to @infinisil:matrix.org
asymmetric: Ping for https://github.com/nix-community/nixdoc/pull/62 :)
Traveling today, will look at it tomorrow hopefully
19:53:14
27 Jul 2023
@ribosomerocker:matrix.orgribosomerocker joined the room.03:04:09
@quark97:matrix.org@quark97:matrix.org left the room.04:35:42
@viktor:kleen.org@viktor:kleen.org left the room.07:07:34
@alejandrosame:matrix.orgalejandrosameI won't be joining today's meeting. See you next week!12:01:50
29 Jul 2023
@infinisil:matrix.orginfinisilI won't be there for the Monday meeting12:33:54
@proofconstruction:matrix.orgproofconstructionI'm back in civilization and will be at the Monday meeting22:57:22
30 Jul 2023
@h7x4:nani.wtfh7x4 set a profile picture.08:30:49
@asymmetric:matrix.dapp.org.ukasymmetrichttps://discourse.nixos.org/t/nixos-installation-instructions-could-use-a-lot-more-details/31062/6?u=asymmetric16:42:32
@asymmetric:matrix.dapp.org.ukasymmetricIs the SE placement of the manuals something that the marketing team needs to work on (as in SEO), or is it dependent on us, for example by splitting the manual to reduce page load?16:43:47
@alejandrosame:matrix.orgalejandrosameHello all! This issue shouldn't be too problematic, but if you have any considerations to improve the exposition I'll appreciate the feedback: https://github.com/NixOS/nixpkgs/issues/24623418:55:07
@khaneliman:matrix.orgAustin Horstman joined the room.20:03:38
@khaneliman:matrix.orgAustin Horstman changed their display name from Austin Horstman to Khaneliman.20:09:56
@khaneliman:matrix.orgAustin Horstman set a profile picture.20:12:06
@fricklerhandwerk:matrix.orgfricklerhandwerk
In reply to @asymmetric:matrix.dapp.org.uk
Is the SE placement of the manuals something that the marketing team needs to work on (as in SEO), or is it dependent on us, for example by splitting the manual to reduce page load?
It seems to mainly hinge on the page size. Good tagging and summaries of smaller pages would surely have positive impact as well.
21:26:43
@proofconstruction:matrix.orgproofconstruction
In reply to @asymmetric:matrix.dapp.org.uk
Is the SE placement of the manuals something that the marketing team needs to work on (as in SEO), or is it dependent on us, for example by splitting the manual to reduce page load?
It seems to mainly hinge on the page size. Good tagging and summaries of smaller pages would surely have positive impact as well.
22:40:52
@proofconstruction:matrix.orgproofconstructiongenuinely no idea what happened there. i guess i forwarded that message to this channel? finding some rough edges in fluffychat apparently!22:41:22
@proofconstruction:matrix.orgproofconstruction
In reply to @alejandrosame:matrix.org
Hello all! This issue shouldn't be too problematic, but if you have any considerations to improve the exposition I'll appreciate the feedback: https://github.com/NixOS/nixpkgs/issues/246234
this is great - i really like the idea of labeling every (sub)section with the relevant diataxis category as a first step
22:43:09
@proofconstruction:matrix.orgproofconstructionre: the installation guide on the wiki coming up in top search engine results - this is (in my opinion) another great reason to make an actually-official one (wiki.nixos.org?) that still has community-generated content. not really sure what happened historically to yield the present state of affairs, but it's confusing and bad as everyone keeps pointing out22:46:20
@proofconstruction:matrix.orgproofconstructionthat is, community-generated in the sense of not being largely dependent on stewardship by the docs team, which is still under-resourced22:47:03
31 Jul 2023
@asymmetric:matrix.dapp.org.ukasymmetric
In reply to @fricklerhandwerk:matrix.org
It seems to mainly hinge on the page size. Good tagging and summaries of smaller pages would surely have positive impact as well.

indeed:

  • https://pagespeed.web.dev/analysis/https-nixos-org-manual-nixos-stable/0jv7c6prdy?form_factor=desktop
  • https://pagespeed.web.dev/analysis/https-nixos-wiki-wiki-NixOS_Installation_Guide/6d6uu0tx4h?form_factor=desktop
09:22:57
@pennae:matrix.eno.spacepennae looking at the meeting notes; henrik-ch: for which manual are you looking for alternatives? 15:40:40
@pennae:matrix.eno.spacepennaeor rather, what's the goal for that manual regardless of tooling15:42:13
@i97henka:matrix.orghenrik-ch Hi pennae , thank you for reaching out - when you read the meeting minutes, you may think that I am doing something or being very concrete about manual rendering alternatives, but that is not the case, rather I am being very unconcrete I would say 😀. 15:49:05
@i97henka:matrix.orghenrik-chWhat I have seen and been impressed by is https://ryantm.github.io/nixpkgs/ and I took a look to see how it's been rendered, that's all. I am still very much a beginner to all these things.15:50:22
@pennae:matrix.eno.spacepennaewe're just a little confused by the generic "alternative manual rendering" juxtaposed with a "nixpkgs" url. nixos-render-docs is itself an alternative/replacement of mmdoc because mmdoc is such a nightmare to extend15:50:58
@i97henka:matrix.orghenrik-ch
In reply to @pennae:matrix.eno.space
we're just a little confused by the generic "alternative manual rendering" juxtaposed with a "nixpkgs" url. nixos-render-docs is itself an alternative/replacement of mmdoc because mmdoc is such a nightmare to extend
You clearly know a lot more about this topic than I do! I am sorry if the statements caused confusion or concern.
15:52:04
@pennae:matrix.eno.spacepennaewe're happy to explain if you have any questions15:53:39
@ryantm:matrix.orgryantmWhat is "such a nightmare to extend" based upon?17:34:54
@ryantm:matrix.orgryantmIs merely using C as the implementation language enough to brand it as such?17:35:27

Show newer messages


Back to Room ListRoom Version: 6