In D53910#1233684, @vladlen wrote:

thank you for considering my comments. Could you look into these issues:

1. Home page translation - the current version of website can be translated, it uses only i18n text. The proposed version of the home page website/themes/beastie/layouts/index.html is in English, and its content cannot be translated (at least I have not found the method yet).
2. Text of "RSS feed" links - current version is translatable - it has alt text alt={{ i18n "rssNews" }} and represented as image, In proposed version it has only English word "Feed" - not prepared for translation. Should it replace by {{ i18n "rssNews" }}.
3. List of events and press text on the home in the current version of site is displayed in choosen version (fixed in last months D53647), but proposed version display these list of events and press in English.

I think, website anyway will have some issues needed to fix. If it is published, this issues will be found and fixed, the more people can participate in bug fix.

In D53984#1233460, @carlavilla wrote:

Did you try it? I don't know if the scss variables are gonna work there. Also the structure.

Put a language link in header as per vladlen request

In D53910#1232897, @vladlen wrote:

Also comment regarding patch: file website/themes/beastie/static/images/freebsd-official.svg has '\ No newline at end of file' message in the patch file. 'patch' in my system stops processing diff after this message, next files were not applied, it silently skips the rest of the file (or reports 'garbadge found, skip the rest' in verbose mode). It took time to find way to apply this patch correctly. Could you fix this svg file? Other svg files do not have this message.

@vladlen The update should've addressed everything you raised. A lot of the issues were indeed down to i18n differences between the old site datafiles and the documentation site datafiles we used for this new version. So apologies for missing a lot of your hard work translating! It should all be back now 😄

Addressing vladlen comments. Follow up comment to come...

@vladlen thank you so much for going through all this with a fine toothed comb! You've caught some great little niggles. @dch and I are going to go through your list and see if we can capture them all now.

remove spurious i18n directory

I owe a deeper explanation for the purpose of this large drop. This is work Mark McBride, and to an extent Sergio, have been working on almost all year. The reason I have got involved is because a) I know Hugo b) it feeds the sole purpose of my job for this year — prove to the world FreeBSD is not dying or dead. There is no escaping the fact people do "judge a book by its cover", despite being told, no doubt by our parents, not to. Our 'book cover' is the website, and it says "FreeBSD is dead". It looks like it's not been touched in years, because speaking of metaphorical 'paint', it hasn't. We need to modernise the website inline with the docs site — which does look modern and loved.

In D53800#1228847, @cperciva wrote:

In D53800#1228648, @mark_freebsdfoundation.org wrote:

Colin, although I wouldn't pick KDE myself, I can't help but think since it's the desktop of choice in the upcoming addition to the installer (Alfonso's work) wouldn't it be more prudent to remove *all other* DEs/WMs from the DVD image (since they're all smaller anyway) and have just KDE on the DVD image? "You can't keep all the people happy all the time", but if we've settled on one DE [for starters] for the installer add on, I can't help thinking it would be useful for that desktop to be in the DVD image :)

If "remove GNOME in order to keep KDE" was an option I would 100% go with that.

But the the choice is actually "remove GNOME *and freebsd-doc* in order to keep KDE".

In D53800#1228729, @adamw wrote:

In D53800#1228648, @mark_freebsdfoundation.org wrote:

Colin, although I wouldn't pick KDE myself, I can't help but think since it's the desktop of choice in the upcoming addition to the installer (Alfonso's work) wouldn't it be more prudent to remove *all other* DEs/WMs from the DVD image (since they're all smaller anyway) and have just KDE on the DVD image? "You can't keep all the people happy all the time", but if we've settled on one DE [for starters] for the installer add on, I can't help thinking it would be useful for that desktop to be in the DVD image :)

Nothing in there is incorrect, but the point isn't to have fully-functional DE after installation so much as it is to give end-users a functional system from which they can bootstrap their real DE.

I'd actually advocate strongly for xfce for that reason. Save even more space; give users a fast, stable, lightweight and fully-functional environment that will work smoothly on more modest systems than gnome can; and provide the simplest way for end-users to bootstrap any other DE.

Colin, although I wouldn't pick KDE myself, I can't help but think since it's the desktop of choice in the upcoming addition to the installer (Alfonso's work) wouldn't it be more prudent to remove *all other* DEs/WMs from the DVD image (since they're all smaller anyway) and have just KDE on the DVD image? "You can't keep all the people happy all the time", but if we've settled on one DE [for starters] for the installer add on, I can't help thinking it would be useful for that desktop to be in the DVD image :)

Thank you for the pragmatism @bcr 👍 🙏

@bcr I'm going to politely disagree with you 😄 Look at the page as it stands now … https://www.freebsd.org/community/ full of 'you'. I actually think in this context it is _correct_ to refer to the reader, it's more personal and _welcoming_, which is surely the point of a community…

@bcr is that a stylistic choice we make across the site?

Yep @jrm, good catch on the channel link, thank you. Fixed. I'm ignoring the nit picking — even my grammar checker (ProWritingAid) thinks that's wrong. You're highlighting a reading stylistic choice, which is fine, but is left to the reader. Grammatically it's incorrect. My edit stands 😊

Update to link for main channel.

Super. Many thanks @carlavilla 🙏

Removed po files as per carlavilla comment.

Actually @carlavilla — in this instance, because it's just a one-letter change to a surname, is it not acceptable for me to change _all_ the language files in the interests of saving other people's time? If it was a translatable word I'd see the point, but in this instance I can't help thinking it's more expedient to do all the language files in one go. Thoughts?

Thanks Sergio! Let me fix that and present a new version.

Are you able to commit it please @bcr? (naturally I cannot 😂)

@cperciva Just tested install of ALPHA3 on the Framework 13, and all is good 👍

In D52402#1201557, @cperciva wrote:

In D52402#1201553, @mark_freebsdfoundation.org wrote:

Sorry @cperciva, I've been a bit slow to see this update. I did the install from the 'disc1' image. I've since done a pkg upgrade, so I'm guessing the second question might not be answerable?

Ok, well, I'm not sure exactly what happened then, but can you test with ALPHA3 over the weekend and confirm that the problem is gone there?

@bcr @jrm I should have fixed those couple of niggles. Hopefully. Ran it through 'tombi' linter before committing, and it didn't moan at least :)

Fix missing quote and add description

Sorry @cperciva, I've been a bit slow to see this update. I did the install from the 'disc1' image. I've since done a pkg upgrade, so I'm guessing the second question might not be answerable?

Oh good grief, I really shouldn't submit things when I'm not well *face palm* Well spotted @bcr. @jrm I'll do a new PR tomorrow when I'm, hopefully, feeling a little more human.

Hmm, I've just installed 15-ALPHA2 - and the installer correctly didn't use these slow, large, fonts on my Framework 13 AMD test machine. But once installed the system is back to using these infuriatingly slow fonts.

This has fixed the painfully slow boot on my Framework 13 AMD too. Thanks @jrm !

Hey folks. I was wondering when this commit might happen? It's a blocker to the site redesign work that @carlavilla is putting a lot of time into 😄 I'd love for this bit to drop so we can progress with the goal of 'new paint' by the time 15 drops. Thanks!

Renders correctly for me with local test too.

In D49773#1153892, @bz wrote:

Yes, you have vht80p80 supported apparently. That is 160Mhz on two non-consecutive channels. I have an open TODO here to get back to you to see as-to why that is not selected but given you are the only one so far I have noticed seeing this.

I've also tested it today, and things are much the same as they were. I'm finding conflicting information as to whether the base station I'm connected to supports 160 wide channels or not. Some resources I find say yes, some say no (it's a TP-Link Deco M9Plus - which is 'AC2200' it says). Either way, I'm not getting a 160 connection, and ifconfig still shows -vht160:

Suggestions as per jrm guidance

Insert newline, as per lwhsu.

OK, it's not a binary, phab thinks it is. Discussed with @dch.

Does this look better? 8859 -> UTF8 conversion It is NOT a binary, despite
what phab thinks. cc dch

Weird! I did notice on the diff that vim had replaced some none printing characters with correct versions - I presume because UTF8 support now versus when the file was probably submitted in 2016? Why it’s saying it’s a binary is beyond me though. Let me try redoing it, and see if I can convince vim to ignore changing characters.

We could add SRI hash (as I do with my own site, running Hugo) — which requires monitoring for changes. I have that in place on my site (cronjob, perl — I'm old — checker) and would be happy to monitor it here too. Extra work, but I've no problem 'owning' that.

Hey folks. This is the stats I'd like to add to the website in the simplest and quickest way possible. With a couple of upcoming blog series we have planned, it would be fantastic to see how they land across the main, doc and foundation websites. Thanks!