For me it's ok, thank you

For the HTML5, in theory, if you don't tell anything to AsciiDoctor, the software is going to use HTML5 by default.
https://docs.asciidoctor.org/asciidoctor/latest/convert/available/

Same for me, I'll keep the FreeBSD name

Thanks, sorry, I changed to another job and these weeks are crazy :D
Thanks for the change

Good report :)

For me is ok.

ah, I never realized about this

Thank you so much for taking care of this

Thanks, yesterday I had a really busy day.
Thank you for fixing this.

Thanks

@ziaee, I think you can go with the commit :)

I think we can send this review to developers@ and ask for more people to accept it :)

I'll make the commit this night or tomorrow

Improvements

In D58166#1334136, @dudleyi_yahoo.com wrote:

@carlavilla this seems to be a problem spread across multiple handbook languages. I did not scrub through them all, but I am sure there are more instances of this issue.

I'm going to make the commit, thanks

In D57999#1330765, @vladlen wrote:

In D57999#1330255, @ziaee wrote:

Do you see any problems with them?

It seems you pushed this commit already and it is live on https://docs.freebsd.org/en/books/dev-model/, where the links work. However local build with cd documentation; make, the links do not work, whereas they links do work for local build in handbook. Also, the appearance is wrong for that page because there are padded spaces some places and not other places. Maybe we can do something like \[crossref:dev-model[ref-freebsd-trenches, Lehey 2002]\] for the appearance? I do not know why the links are broken in offline build though.

I will check it. I checked it locally with cd documentation; make run and
looked at it in a browser.

I tried using \[ , but the output rendered as \[ literally.

Probably we could change the link style. Links like [1] were used in old
books, and now they are mostly used in scientific articles. Square brackets
are special symbols in AsciiDoc, and we will spend more time fighting with
them than using them comfortably.

In D57999#1330089, @vladlen wrote:

In D57999#1330069, @ziaee wrote:

In D57999#1330065, @carlavilla wrote:

In D57999#1330057, @ziaee wrote:

Dude you rock! Aside from dev-model, all the changes LGTM.

if the macro is broken, I need to fix it. But I created this macros coz we have these scenarios:

• Online website (freebsd.org, docs.freebsd.org)
• Offline website
• PDFs

It works everywhere else I checked except dev-model.

This links had 2 problems:
[crossref:dev-model[freebsd-send-pr, FreeBSD, 2002D]]

1. The same, as in website - it started and finished by square bracket

and simply disappeared from output (considered as AsciiDoc command).
I fixed this, they appeared, and I saw second problem:

2. The text FreeBSD, 2002D rendered as FreeBSD, everything

after comma were ignored. I removed comma and text is renderd correctly.
This comma is only for refference style, it does not have any special meaning.
With this changes all these links work correctly at least in HTML.

Do you see any problems with them?

P.S. Original article used reference style [FreeBSD, 2002D] long before AsciiDoc
was choosen for FreeBSD documentation, and now [ and ] chars need special treatment
in adoc files, or we are free to rename all these links.

In D57725#1330090, @vladlen wrote:

In D57725#1323489, @ziaee wrote:

1. 20 is too short. Can we have 50?
2. why does this combine security and errata if we have two separate feeds for that?
3. can we please put the actual content in these?

I can make additional RSS-feed for SA and EN pages (they both have default RSS feed with 0 items),
it could be additional task, but our colleagues ask to fix this interface.
Could we proceed with it?

In D57999#1330057, @ziaee wrote:

Dude you rock! Aside from dev-model, all the changes LGTM.

is quick.toml the right name for this? -> TBH, I think no :D, maybe we can find another name
should we bring back the config directory to put both of the tomls? -> hmmm, maybe yes

My apologies then.
Can you upload again the diff with only these changes?
I want to test it in my machine.

Sorry, I cannot see the file coz it's too long.

I should also mention that I've looked at the segments and partial caches[1], and compilation time hasn't improved.

I've been looking into this.
I think the simplest solution would be:

If you do this. Will be impossible to change the theme in the future

In D57722#1323618, @vladlen wrote:

In D57722#1323579, @ziaee wrote:

Can we fix https://www.freebsd.org/status/feed.xml instead of adding a new one?

This file is the template exactly for this link. Hugo uses naming convention
[section name].[type].xml (type is 'rss')
status.xml changes RSS-feed for all '/status' pages from default template.
The link https://gohugo.io/templates/rss/#custom-templates

Other names:
status.rss.xml
rss.xml

Coz if you put in two, you will break the current """"API""""", people will complain

I cannot download the patch and build it in my local machine.
These days I am busy with personal issues.