In D57051#1310344, @ziaee wrote:

Honestly, this section was broken and is still broken, because the section is called "choosing an image" but it does not explain the images. BASIC-CI, the most FAQ, now has a disclaimer that it is not what the reader intuitively thinks is, which is a doc smell, due to the an extremely unequal weighting of information where no other VM image is even explained at all. Cloudinit images are not mentioned, and they are the hot thing right now. The difference between DVD1 vs disc1 is not explained at all, so people will still ask questions about what those are.

In D57165#1310335, @ziaee wrote:

In D57165#1310053, @carlavilla wrote:

For me is ok, the simplest, the better, but wait for more reviews please

who do you think i should get to review this and why?

@vladlen, can we move this?

For me is ok, the simplest, the better, but wait for more reviews please

Update diff with changes requested

For me is ok, if you don't mind, can we commit in this order:

• https://reviews.freebsd.org/D57051
• https://reviews.freebsd.org/D57161 (without the choosing section)
• https://reviews.freebsd.org/D57165

For the section "Choosing an Image", I prefer to go with this one: https://reviews.freebsd.org/D57051
I think the change in this review is too much.
The other changes, I am ok.

For me is ok, thanks for the improvements you are making to this tool

In D56646#1309125, @vladlen wrote:

In D56646#1299250, @ziaee wrote:

Sorry I didn't have time to review this. This is absolutely wonderful, thank you so much for doing this. I wanted this for a long time but couldn't make it myself. Could you make the links also bold to match the drivers without manuals?

@ziaee

Hi Alex,
I am preparing the next fix for this script (replace '\[' to '[' , mandoc generates \[, if driver descrition has [ in the text).

I could also add the feature you are asking for.
Now hardware-notes-processor.rb generates messages to stdout and skips processing.
The current list for 15.1R is:

WARNING: The manual page man4.i386/ep does not exists

WARNING: The manual page man4.i386/ex does not exists

WARNING: The manual page man4.i386/fe does not exists

WARNING: The manual page hme does not exists

WARNING: The manual page pcn does not exists

WARNING: The manual page sf does not exists

WARNING: The manual page sn does not exists

WARNING: The manual page tl does not exists

WARNING: The manual page txp does not exists

WARNING: The manual page man4.i386/vx does not exists

WARNING: The manual page wb does not exists

WARNING: The manual page xe does not exists

WARNING: The manual page man4.i386/ce does not exists

WARNING: The manual page man4.i386/cx does not exists

WARNING: The manual page man4.i386/cp does not exists

WARNING: The manual page man4.i386/ctau does not exists

WARNING: The manual page ufintek does not exists

I have other proposal.
If line
&hwlist.man4.i386/ep;
generates this warning

WARNING: The manual page man4.i386/ep does not exists

then I can put this line again into the hardware.adoc. It can be easily found by '&hwlist' string.

1. If this driver is not supported by this release, then this line can be manually removed one time.
2. if driver supported by it does not have HARDWARE section, this line will be updated

next time, when HARDWARE section added before reease date.

3. If HARDWARE section is not added, this line will be removed day before release.

In this case hardware.adoc will be improved during every run
make generate-hardware-notes
One times to copy from template and every run to add new HARDWARE sections.

What do you think?

Do it like this by now, we will think in a final solution later

for me is ok, but the JavaScript is yours, put your name in the copyright :)

Go ahead, and also with the change in the JavaScript for the website.
I put a comment in the other review.

For me is ok, but please, put in an external javascript file and add it in the head

Put it in the header and as a separate file please.

In D57024#1307248, @fernape wrote:

Ya que decimos "porter" probablemente debamos dejar "ports".

Por cierto, ¿cómo puedo ver el resultado después de aplicar los cambios? DOC_LANG=es make run me muestra la página en inglés.

In D57024#1307248, @fernape wrote:

Ya que decimos "porter" probablemente debamos dejar "ports".

Por cierto, ¿cómo puedo ver el resultado después de aplicar los cambios? DOC_LANG=es make run me muestra la página en inglés.

In D51904#1189567, @lwhsu wrote:

The Torrents page contains both latest production and legacy release versions so we may need to mention this in both places, perhaps under the table of each -RELEASE, or putting in the "Choosing an Image" section. For the wording I suggest saying something like The magnet links to download via BitTorrent protocol are available at link:https://wiki.freebsd.org/Torrents[FreeBSD Torrents Wiki page].

In D53910#1305694, @ziaee wrote:

The new diff fixes the problems rendered in make run. Approving as myself, releng based on the discussion with @dch and @cperciva, and approving as doceng based on myself and feedback timeout. @dch on behalf of Core Team said earlier that this is fine with secteam, clusteradm said it was fine over email, #translations said no objection earlier. Afaict, we have successfully got someone from each team to sign off on it, and we can now merge this with consensus.

@carlavilla, IIUC I believe this should be committed with Mark McBride as the principal author, co-authored by you and @mark_freebsdfoundation.org, and reviewed by the appropriate teammates, and discussed with the teammates who contributed to this patch with suggestions but did not formally approve or request changes.

Let's get this in, and then I look forward to @vladlen's translation logic rewrite he proposed on GitHub. This has truly been an epic journey, tensions were high, lots of different parties coming in and quite a few even resigning. Separately from the technical improvement, I think we pulled through as team and made it happen for the Project, with many difficult compromises, and that really matters.

In D53910#1305608, @ziaee wrote:

alright. i tried building this with DOC_LANG= , public/index.html is illegible, public/en/index.html redirects to actual f.o, and make run gives a site with no header buttons except the hambuger menu.

In D53910#1305462, @mark_freebsdfoundation.org wrote:

@carlavilla The width is too much now - I only ever get the burger menu on my laptop screen, even at max width.

Good catch.
Btw, I am feeling old... I started with floppy disks and right now we're removing mentions to CD-ROM and DVD :'(

In D53910#1305141, @mark_freebsdfoundation.org wrote:

In D53910#1305134, @cperciva wrote:

Is this going to land soon? I'd really like to avoid colliding with 15.1 release engineering; I bump a lot of files when the release comes out and I don't want to deal with rebase conflicts at announcement time.

@carlavilla — ship it! 😁 I've rebased on main and sorted the words on the community section.

In D53910#1304647, @fernape wrote:

In D53910#1304417, @ziaee wrote:

Another possibility might be "For over 30 years, this grassroots project has been powered by volunteers, research institutions, and corporate supporters."

Drop "grassroot".

I changed the icons to be all the same, wait to Mark please and take a look again

I changed the descriptions to make them a bit shorter, wait for Mark to upload it or check it in my repo please

I cannot upload the diff using the web interface :'(

Sorry, I was busy these last weeks!
Thanks!

In D53910#1294228, @vladlen wrote:

@carlavilla Sergio, you send the call for remarks yesterday, here what I found:

1. page https://freebsd.fortasse.cloud/projects/newbies/ has left menu with Webresources, that point to missing page.
2. Home page in Russian and Chinese: headers of the sections "News", "Event", "Security advisories", "Errata notices" are in English. It was fixed in previous versions of the new theme (dicsussed in this review at 29-30 of November 2025), but appear again.
3. Also the discussion about the language choice was at 29 November of 2025, and icon to change the language was added in the top of the page near the search filed. It disapeared in this version of the design, but it is very important.
4. page https://freebsd.fortasse.cloud/languages/ (language choice) - English and Chinese languages names overlap each other (I tested in Safari and Chome). On mobile phone (or in browser with narrow window) language names overlap all togheter in one small area. I suppose, this section should use responsive design to react on the screen size (sorry, I did not look at that code inside yet, could not be more specific, there are only observation of the behaviour)

@mark_freebsdfoundation.org can you please upload the current changes to the server? Thanks!

Thank you so much for taking care of this :)

In D53910#1294365, @minsoochoo0122_proton.me wrote:

Two things to add:

First, if you see https://freebsd.fortasse.cloud/releases/15.0R/relnotes/, the "Important" box with red background has broken CSS.

Second, on the same page, I can see black background (missing theme) on load/refresh for the first ~0.5sec then the red theme loads.

In D53910#1293617, @christos wrote:

Many translations (e.g., German, Danish, Polish from a quick look) are actually in English.

Thanks for the path, I am going to make the commit

Ok, I let one week to developers@ to request changes.
Seems nobody really complained.

In D53910#1293441, @mark_freebsdfoundation.org wrote:

In D53910#1293398, @carlavilla wrote:

I removed the wiki from the documentation menu.
And yes please, if you can make the diff, upload it.

Btw, can you please deploy the last changes? I want to send the message today

Thanks!

Deployed to the staging site 👍

Now I just need to work out how to change this patch with 'git arc', ha! It dawned on me the tree we've been working on doesn't have the same commit message, so I'm not sure how to replace this without doing something as kludgey as rsync'ing your working GH over what I have 🤔 Any guidance on that @ziaee before I do my usual thing and ask @dch to help me dig out of the hole…

Incidentally, not for now, but once deployed — I think we ponder the front page download links. With my marketing hat on it's too confusing presenting people with three different OS downloads — there should be a single 'CTA' (which should obviously be 15.0 right now). Funnily enough this is even starker to me now because I'm currently reading the classic "Don't make me think" by Steve Krug 😄 This can wait though, we'll sort it after live. Choices for other versions can be presented on the actual download page, for example.

In D53910#1293397, @mark_freebsdfoundation.org wrote:

In D53910#1293298, @carlavilla wrote:

At any rate, would you guys update the diff in this revision so we can see the diff as well?

Sure, let me update the diff

If it's easier for me to do that @carlavilla, I can (the 'git amend' is in my history 😂)

In D53910#1293297, @ziaee wrote:

Looks pretty good on android phone and firefox desktop.

I'm not sure about the current release progression going latest, previous, next. The order is 2,1,3 with no context. I'll try to get some friends from linux take a look with a fresh set of eyes and see if they have any ideas.

Also, after spending a tremendous amount of effort to revitalize the release errata and hardware pages that most people don't know exist, I really don't like the "announcement, notes" appearing without them and hiding them. "will this run on my hardware" is an extremely popular question and i have sank hundreds of hours into the hardware notes. It's still not perfect, but people needs to know it exists.

At any rate, would you guys update the diff in this revision so we can see the diff as well?

Merged

In D53910#1293270, @mark_freebsdfoundation.org wrote:

In D53910#1293244, @carlavilla wrote:

https://github.com/sergio-carlavilla/freebsd-new-design/pull/18

Done

Just issued a PR to fix the /languages link in footer (we were missing languages.adoc in content/{en,ru,zh-tw}). There's another PR to fix the hardcoded www.freebsd.org in footer too 👍

In D53910#1293270, @mark_freebsdfoundation.org wrote:

In D53910#1293244, @carlavilla wrote:

https://github.com/sergio-carlavilla/freebsd-new-design/pull/18

Done

Just issued a PR to fix the /languages link in footer (we were missing languages.adoc in content/{en,ru,zh-tw}). There's another PR to fix the hardcoded www.freebsd.org in footer too 👍

In D53910#1293240, @mark_freebsdfoundation.org wrote:

In D53910#1293239, @mark_freebsdfoundation.org wrote:

In D53910#1293199, @mark_freebsdfoundation.org wrote:

In D53910#1293177, @carlavilla wrote:

Can you please publish the current version? I made the changes and I think we can send the message at least to developers@ and see the changes they request.

Yep! Give me 10 minutes and it’ll be sorted.

Done @carlavilla 😃

@carlavilla just issued PR 18 to fix the menus (absLangURL hard codes 'www.freebsd.org', which breaks the test site. Better to use relLangURL)

https://github.com/sergio-carlavilla/freebsd-new-design/pull/18

In D53910#1293106, @mark_freebsdfoundation.org wrote:

In D53910#1293103, @carlavilla wrote:

In D53910#1292733, @mark_freebsdfoundation.org wrote:

Hey @carlavilla I dropped a couple more PRs onto GH - quick fixes for latest versions of 14 👍

Merged.
And I am going to finish the last things.

Awesome! Thanks Sergio. If you need my help for anything over the weekend, please just ping me here and I’ll get onto it 👍

In D53910#1292733, @mark_freebsdfoundation.org wrote:

Hey @carlavilla I dropped a couple more PRs onto GH - quick fixes for latest versions of 14 👍

In D56430#1292349, @ziaee wrote:

I don't really understand how the .po files work, @ebrandi usually regenerates them all at once every few months.

If you move this to an article.
Please after putting it in production, remember to ask clusteradm@ to create a redirect in nginx

In D53910#1291161, @mark_freebsdfoundation.org wrote:

In D53910#1291146, @carlavilla wrote:

In D53910#1291144, @mark_freebsdfoundation.org wrote:

Hola @carlavilla — @grahamperrin pinged me some helpful proofreading bits late last night, which I've put into a PR to the repo this morning 👍

Done. Thanks to both.
For me, one of the things we need to improve is the where page (downloads).
I think we can take the design from the design made by Mark

👍 Have you got the time this week to look at it?

In D53910#1291144, @mark_freebsdfoundation.org wrote:

Hola @carlavilla — @grahamperrin pinged me some helpful proofreading bits late last night, which I've put into a PR to the repo this morning 👍

In D53910#1290819, @mark_freebsdfoundation.org wrote:

In D53910#1290817, @carlavilla wrote:

This is the problem; everywhere this is used for images absLangURL ($.Site.BaseURL) we should use {{ "link/to/file" | relURL }}.

Let me sort them out and issue PRs @carlavilla 😄

YEs, about this you are right, sorry for that :(

No apology necessary my good man! It's a complicated site and it's easy to miss 😊

Here you go, this should sort these few images… https://github.com/sergio-carlavilla/freebsd-new-design/pull/12

In D53910#1290813, @mark_freebsdfoundation.org wrote:

In D53910#1290802, @mark_freebsdfoundation.org wrote:

Thanks for merging the PRs @carlavilla . The reason the staging server is "missing" some images is because the code is using full URLs, which we shouldn't be doing…

{F152372940}

I'll take a look and issue a PR 👍

This is the problem; everywhere this is used for images absLangURL ($.Site.BaseURL) we should use {{ "link/to/file" | relURL }}.

I fixed all this in this Phab a long time ago. It's a pity we're going over the same work again now, really. There are a lot of 'old' Hugo'isms that need modernising, which was a lot of what I had been doing on top of Mark McB's 'paint'.

Let me sort them out and issue PRs @carlavilla 😄

In D53910#1290761, @mark_freebsdfoundation.org wrote:

In D53910#1290735, @carlavilla wrote:

WARN  deprecated: .Site.Data was deprecated in Hugo v0.156.0 and will be removed in a future release. Use hugo.Data instead.
WARN  deprecated: .Site.Sites and .Page.Sites was deprecated in Hugo v0.156.0 and will be removed in a future release. Use hugo.Sites instead.

I'm really happy to see this moving again! Let's get it deployed soon, so the world stops thinking we're a dying project. We're anything but 👏

Yes, about the warning I know, fernape@ fixed it but for some reason he reverted the change.

I just took a look and for some reason, some strings are not translated, don't know why, and the same for some icons.
Also, can you deploy the minified version?

What's not minified @carlavilla? I did a make clean && make build && rsync public which AFAIK means Hugo builds minified CSS etc.

fetch -o- https://freebsd.fortasse.cloud/styles/main.min.css looks pretty minified to me. What am I missing? 🤔

@fernape do you know what version of Hugo is on the CI server?

In D53910#1290759, @fernape wrote:

In D53910#1290735, @carlavilla wrote:

In D53910#1290734, @mark_freebsdfoundation.org wrote:

In D53910#1290526, @bz wrote:

I just looked at the staging site. My initial comment was: that's the next level of losing links to what is available on www.freebsd.org in information and this time we are avoiding the fact that monitors are WIDE and not 4:3 anymore for 1.5 decades. 70% of the landing page is white space and if you look at the generated page we are serving blank lines of HTML and little content in vertical scrolling. Please bring SGML back. *cry*

You need to update https://freebsd.fortasse.cloud/internal/about/ to which I have no idea to get to anymore if I wouldn't know /internal/ existed. Probably a fault of the previous (current) version already.

The sidebar on /security/ is unreadable with some items spanning 2-3 lines.

The footer uses more vertical space than content on some of the menu-accessible pages.

The 5 columns under the marketing which have information have become tiny unreadable here.

Firefox on a FreeBSD Laptop.

@carlavilla latest version is now up on https://freebsd.fortasse.cloud — please take a look at that @bz 👍 You may have to hard refresh the page to get all the components. It should look like the screen shot posted yesterday, i.e. with the yellow download buttons.

Regarding whitespace and screen widths. There has been lots of research into this, and long story short, it's all led by the way we humans read. For a more skilled and lengthy overview, this is worth a watch… https://youtu.be/Jf0cjocP8Wk

Lastly, @carlavilla there is the Hugo deprecation notice in your latest work. I fixed it in this Phab the other day, I'll do it against your repo and issue a PR later today 👍 The notice looks like this on build:

WARN  deprecated: .Site.Data was deprecated in Hugo v0.156.0 and will be removed in a future release. Use hugo.Data instead.
WARN  deprecated: .Site.Sites and .Page.Sites was deprecated in Hugo v0.156.0 and will be removed in a future release. Use hugo.Sites instead.

I'm really happy to see this moving again! Let's get it deployed soon, so the world stops thinking we're a dying project. We're anything but 👏

Yes, about the warning I know, fernape@ fixed it but for some reason he reverted the change.

It was failing to build in the CI for some reason. I could not reproduce it locally, where it worked.

I just took a look and for some reason, some strings are not translated, don't know why, and the same for some icons.
Also, can you deploy the minified version?

In D53910#1290734, @mark_freebsdfoundation.org wrote:

In D53910#1290526, @bz wrote:

I just looked at the staging site. My initial comment was: that's the next level of losing links to what is available on www.freebsd.org in information and this time we are avoiding the fact that monitors are WIDE and not 4:3 anymore for 1.5 decades. 70% of the landing page is white space and if you look at the generated page we are serving blank lines of HTML and little content in vertical scrolling. Please bring SGML back. *cry*

You need to update https://freebsd.fortasse.cloud/internal/about/ to which I have no idea to get to anymore if I wouldn't know /internal/ existed. Probably a fault of the previous (current) version already.

The sidebar on /security/ is unreadable with some items spanning 2-3 lines.

The footer uses more vertical space than content on some of the menu-accessible pages.

The 5 columns under the marketing which have information have become tiny unreadable here.

Firefox on a FreeBSD Laptop.

@carlavilla latest version is now up on https://freebsd.fortasse.cloud — please take a look at that @bz 👍 You may have to hard refresh the page to get all the components. It should look like the screen shot posted yesterday, i.e. with the yellow download buttons.

Regarding whitespace and screen widths. There has been lots of research into this, and long story short, it's all led by the way we humans read. For a more skilled and lengthy overview, this is worth a watch… https://youtu.be/Jf0cjocP8Wk

Lastly, @carlavilla there is the Hugo deprecation notice in your latest work. I fixed it in this Phab the other day, I'll do it against your repo and issue a PR later today 👍 The notice looks like this on build:

WARN  deprecated: .Site.Data was deprecated in Hugo v0.156.0 and will be removed in a future release. Use hugo.Data instead.
WARN  deprecated: .Site.Sites and .Page.Sites was deprecated in Hugo v0.156.0 and will be removed in a future release. Use hugo.Sites instead.

I'm really happy to see this moving again! Let's get it deployed soon, so the world stops thinking we're a dying project. We're anything but 👏

In D32450#1290609, @ziaee wrote:

In D32450#1290560, @emaste wrote:

OBE. I'd still like us to provide some more clarity on releases -- right now 15.0 and 14.4 are "Production Releases" with no advice on how to pick one or the other. But the specific issue related to this review is gone.

I agree. I tried proposing "Production Release" and "Maintenance Release", but some people hated it. This is a hard problem.

As you said, we made this change in docs too

In D53910#1290526, @bz wrote:

I just looked at the staging site. My initial comment was: that's the next level of losing links to what is available on www.freebsd.org in information and this time we are avoiding the fact that monitors are WIDE and not 4:3 anymore for 1.5 decades. 70% of the landing page is white space and if you look at the generated page we are serving blank lines of HTML and little content in vertical scrolling. Please bring SGML back. *cry*

You need to update https://freebsd.fortasse.cloud/internal/about/ to which I have no idea to get to anymore if I wouldn't know /internal/ existed. Probably a fault of the previous (current) version already.

The sidebar on /security/ is unreadable with some items spanning 2-3 lines.

The footer uses more vertical space than content on some of the menu-accessible pages.

The 5 columns under the marketing which have information have become tiny unreadable here.

Firefox on a FreeBSD Laptop.

In D53910#1290526, @bz wrote:

I just looked at the staging site. My initial comment was: that's the next level of losing links to what is available on www.freebsd.org in information and this time we are avoiding the fact that monitors are WIDE and not 4:3 anymore for 1.5 decades. 70% of the landing page is white space and if you look at the generated page we are serving blank lines of HTML and little content in vertical scrolling. Please bring SGML back. *cry*

You need to update https://freebsd.fortasse.cloud/internal/about/ to which I have no idea to get to anymore if I wouldn't know /internal/ existed. Probably a fault of the previous (current) version already.

The sidebar on /security/ is unreadable with some items spanning 2-3 lines.

The footer uses more vertical space than content on some of the menu-accessible pages.

The 5 columns under the marketing which have information have become tiny unreadable here.

Firefox on a FreeBSD Laptop.

I need to improve the header menu and add more options, I know this issue.

In D53910#1290455, @mark_freebsdfoundation.org wrote:

Looking peachy @carlavilla ! 👌 Could I push this version to the 'staging' server at https://freebsd.fortasse.cloud? It would be good for folks to view it there.

{F152245894}

In D53910#1290445, @cperciva wrote:

@carlavilla Can you try to get your changes merged so this can get committed soon? The 15.1 release cycle is about to get underway and I'm worried about this landing at a time when I'm doing a bunch of commits, especially since I stage them ahead of time and then push out when announcements are ready to go -- I don't want to have rebase problems show up at the wrong moment.

In D53910#1290350, @mark_freebsdfoundation.org wrote:

In D53910#1289152, @carlavilla wrote:

I saw the PR to my repo. I'll take a look this weekend.
The main page is finished.
We need to finish the others: events, news, 404, etc
And for sure, we cannot make the commit without core@ and doceng@ approval

We're good to go Sergio. This has been going on a long time with many discussions 😊 @dch just signed off on it.