User talk:Vater

From NixOS Wiki

wiki.nixos.org to do

information about getting nix merch

How to get merch (about (Nix or) NixOS) for free (or cheap) to support an event with Nix topics?

The Marketing Team (or someone else) should provide a list where (and how) to get stuff. There are companies out there that give away free "promotional merchandise" to conferences (for example, even trade shows or events like that). A lot of them are having very Nix(OS) focused stuff. Some of those are having a (smaller or bigger) branding of the company. But there are a lot of articles that are absolutely branding free. NixOS logo stickers are an example for that. Which companies are interested to send merch to organizers and how to order them?

--Vater (talk) 23:41, 9 September 2023 (UTC)Reply[reply]

Homepage

Hi, this comment was removed by one of your edits:

NOTE: Please don't change the layout/categorizing without first coordinating with the other editors.

https://wiki.nixos.org/w/index.php?title=NixOS_Wiki&diff=prev&oldid=12364

And, relatedly, maybe I missed it, but was there an attempt at coordinating with the other editors? I see you have severely changed the page, while causing new design issues (especially with regard to responsiveness), and changed the content in drastic ways.

I'll be reverting many of the changes. samueldr (talk) 19:28, 9 May 2024 (UTC)Reply[reply]

Sorry for (maybe) breaking things. What wasn't working anymore? (What works better now?)
@Samueldr
How to coordinate “with the other editors”?
My approach was (just the) wikipedia:en:KISS-principle. (From my point of view, the use of HTML syntax instead of Wiki syntax is wrong (in a Wiki).)
Using <b> instead of ''' (or “useless” <span> and so on) seems bad style to me. Vater (talk) 00:42, 14 May 2024 (UTC)Reply[reply]

Sorry for (maybe) breaking things. What wasn't working anymore? (What works better now?)

This list is not meant to be a dunk, but a list of what issues it caused.
  • The two-columns layout didn't flow in a single-column layout on narrow (e.g. mobile) viewports.
  • The headers had broken margin/padding (way too much at the top).
  • The headers gained an unexpected line under themselves.
  • The semantics of table-as-a-stylistic-tool meant the columns ratio was automatically guessed by the browser, and disrupted the weight of the columns.
  • The headers broke due to automatic insertion of links when logged-in.
  • The added contrast from the default wikitable styles was a lot, visually speaking.
In addition, removing the special pages box outright was problematic as (outside one link) they were links to special pages that are often useful, but not part of the sidebar menu. So this actually removed information not found otherwise.

From my point of view, the use of HTML syntax instead of Wiki syntax is wrong (in a Wiki).)

I would agree for “contentful” pages. The main page, though, is a special case.
Similarly, templates that abstract the markup for visual purposes is a good thin to use, whether it's HTML or wikimarkup. The template exists to provide semantics, and package it visually.
The “KISS” principle agrees with using templates, as instead of repeating cumbersome markup for the layout (whether it is HTML or wikitables) you are simply describing the thing you are making: boxes for the homepage.
Finally, though you would only have known if you had coordinated beforehand, the implementation of the main page is not necessarily the final way it will appear, but only how it is to get the new wiki going. First, it's not even decided if the default theme will be kept, and what an appropriate theme would be if it is not. This would likely affect the main page's templating. Second, as this is the main entry point for the whole wiki, the wiki team hasn't yet discussed what to do with the frontpage, whether it's kept from the old wiki, or if we decide on a new approach. samueldr (talk) 02:40, 14 May 2024 (UTC)Reply[reply]

notes for (testing) CSS MediaWiki style

mediawikiwiki:Manual:Interface/Stylesheets Vater (talk) 12:50, 14 May 2024 (UTC)Reply[reply]