1 files changed, 24 insertions, 25 deletions

diff --git a/documentation/content/en/articles/building-products/_index.adoc b/documentation/content/en/articles/building-products/_index.adoc
index 29fca86847..e3bcb2f895 100644
--- a/documentation/content/en/articles/building-products/_index.adoc
+++ b/documentation/content/en/articles/building-products/_index.adoc
@@ -19,27 +19,26 @@ tags: ["FreeBSD", "FreeBSD as base for your product"]
 :sectnumlevels: 6
 :source-highlighter: rouge
 :experimental:
+:images-path: articles/building-products/
 
-
-ifeval::["{backend}" == "html5"]
+ifdef::env-beastie[]
+ifdef::backend-html5[]
+include::shared/authors.adoc[]
+include::shared/mirrors.adoc[]
 include::shared/releases.adoc[]
-include::shared/en/mailing-lists.adoc[]
-include::shared/en/urls.adoc[]
-:imagesdir: ../../../images/articles/building-products/
+include::shared/attributes/attributes-{{% lang %}}.adoc[]
+include::shared/{{% lang %}}/teams.adoc[]
+include::shared/{{% lang %}}/mailing-lists.adoc[]
+include::shared/{{% lang %}}/urls.adoc[]
+:imagesdir: ../../../images/{images-path}
+endif::[]
+ifdef::backend-pdf,backend-epub3[]
+include::../../../../shared/asciidoctor.adoc[]
 endif::[]
-
-ifeval::["{backend}" == "pdf"]
-include::../../../../shared/releases.adoc[]
-include::../../../../shared/en/mailing-lists.adoc[]
-include::../../../../shared/en/urls.adoc[]
-:imagesdir: ../../../../static/images/articles/building-products/
 endif::[]
 
-ifeval::["{backend}" == "epub3"]
-include::../../../../shared/releases.adoc[]
-include::../../../../shared/en/mailing-lists.adoc[]
-include::../../../../shared/en/urls.adoc[]
-:imagesdir: ../../../../static/images/articles/building-products/
+ifndef::env-beastie[]
+include::../../../../../shared/asciidoctor.adoc[]
 endif::[]
 
 [.abstract-title]
@@ -180,7 +179,7 @@ Conflict resolution is performed by a nine member "Core Team" that is elected fr
 
 FreeBSD does not have "corporate" committers.
 Individual committers are required to take responsibility for the changes they introduce to the code.
-The link:{committers-guide}[FreeBSD Committer's guide] <<ComGuide>> documents the rules and responsibilities for committers.
+The extref:{committers-guide}[FreeBSD Committer's guide] <<ComGuide>> documents the rules and responsibilities for committers.
 
 FreeBSD's project model is examined in detail in <<Nik2005>>.
 
@@ -200,7 +199,7 @@ image::freebsd-branches.png[]
 Code lines are kept alive for as long as there is user and developer interest in them.
 
 Machine architectures are grouped into "tiers"; _Tier 1_ architectures are fully supported by the project's release engineering and security teams, _Tier 2_ architectures are supported on a best effort basis, and experimental architectures comprise _Tier 3_.
-The list of link:{committers-guide}#archs[supported architectures] is part of the FreeBSD documentation collection.
+The list of extref:{committers-guide}[supported architectures, archs] is part of the FreeBSD documentation collection.
 
 The release engineering team publishes a link:https://www.FreeBSD.org/releng/[road map] for future releases of FreeBSD on the project's web site.
 The dates laid down in the road map are not deadlines; FreeBSD is released when its code and documentation are ready.
@@ -280,7 +279,7 @@ Plan for the long term::
 Setup processes that help in tracking the development of FreeBSD.
 For example:
 +
-*Track FreeBSD source code.* The project makes it easy to mirror its SVN repository using link:{committers-guide}#svn-advanced-use-setting-up-svnsync[svnsync]. Having the complete history of the source is useful when debugging complex problems and offers valuable insight into the intentions of the original developers. Use a capable source control system that allows you to easily merge changes between the upstream FreeBSD code base and your own in-house code.
+*Track FreeBSD source code.* The project makes it easy to mirror its SVN repository using extref:{committers-guide}[svnsync, svn-advanced-use-setting-up-svnsync]. Having the complete history of the source is useful when debugging complex problems and offers valuable insight into the intentions of the original developers. Use a capable source control system that allows you to easily merge changes between the upstream FreeBSD code base and your own in-house code.
 +
 <<fig-svn-blame, An annotated source listing generated using `svn blame`>> shows a portion of an annotated listing of the file referenced by the change log in <<fig-change-log, A sample change log entry>>.
 The ancestry of each line of the source is clearly visible.
@@ -340,7 +339,7 @@ In some countries, donations to the FreeBSD project enjoy tax benefits.
 The project has a dedicated link:https://www.FreeBSD.org/donations/[donations liaison] to assist donors.
 The project also maintains a web page where developers link:https://www.FreeBSD.org/donations/wantlist/[list their needs]. 
 +
-As a policy the FreeBSD project link:{contributors}[acknowledges] all contributions received on its web site.
+As a policy the FreeBSD project extref:{contributors}[acknowledges] all contributions received on its web site.
 
 [[conclusion]]
 == Conclusion
@@ -359,19 +358,19 @@ The article concluded with a list of best-practices that could help organization
 
 [[Carp1996]] [Carp1996] http://www.ietf.org/rfc/rfc1958.txt[The Architectural Principles of the Internet] B. Carpenter. The Internet Architecture Board.The Internet Architecture Board. Copyright(R) 1996.
 
-[[ComGuide]] [ComGuide] link:{committers-guide}[Committer's Guide] The FreeBSD Project. Copyright(R) 2005.
+[[ComGuide]] [ComGuide] extref:{committers-guide}[Committer's Guide] The FreeBSD Project. Copyright(R) 2005.
 
 [[GoldGab2005]] [GoldGab2005] http://dreamsongs.com/IHE/IHE.html[Innovation Happens Elsewhere: Open Source as Business Strategy] Ron Goldman. Richard Gabriel. Copyright(R) 2005. Morgan-Kaufmann.
 
-[[Hub1994]] [Hub1994] link:{contributing}[Contributing to the FreeBSD Project] Jordan Hubbard. Copyright(R) 1994-2005. The FreeBSD Project.
+[[Hub1994]] [Hub1994] extref:{contributing}[Contributing to the FreeBSD Project] Jordan Hubbard. Copyright(R) 1994-2005. The FreeBSD Project.
 
 [[McKu1999]] [McKu1999] http://www.usenix.org/publications/library/proceedings/usenix99/mckusick.html[Soft Updates: A Technique for Eliminating Most Synchronous Writes in the Fast Filesystem] Kirk McKusick. Gregory Ganger. Copyright(R) 1999.
 
 [[McKu1999-1]] [McKu1999-1] http://www.oreilly.com/catalog/opensources/book/kirkmck.html[Twenty Years of Berkeley Unix: From AT&T-Owned to Freely Redistributable] Marshall Kirk McKusick. http://www.oreilly.com/catalog/opensources/book/toc.html[Open Sources: Voices from the Open Source Revolution] O'Reilly Inc.. Copyright(R) 1993.
 
-[[Mon2005]] [Mon2005] link:{bsdl-gpl}[Why you should use a BSD style license for your Open Source Project] Bruce Montague. The FreeBSD Project. Copyright(R) 2005.
+[[Mon2005]] [Mon2005] extref{bsdl-gpl}[Why you should use a BSD style license for your Open Source Project] Bruce Montague. The FreeBSD Project. Copyright(R) 2005.
 
-[[Nik2005]] [Nik2005] link:{dev-model}[A project model for the FreeBSD Project] Niklas Saers. Copyright(R) 2005. The FreeBSD Project.
+[[Nik2005]] [Nik2005] extref:{dev-model}[A project model for the FreeBSD Project] Niklas Saers. Copyright(R) 2005. The FreeBSD Project.
 
 [[Nor1993]] [Nor1993] http://www.norvig.com/luv-slides.ps[Tutorial on Good Lisp Programming Style] Peter Norvig. Kent Pitman. Copyright(R) 1993.
 
@@ -379,4 +378,4 @@ The article concluded with a list of best-practices that could help organization
 
 [[Ray2004]] [Ray2004] http://www.catb.org/~esr/faqs/smart-questions.html[How to ask questions the smart way] Eric Steven Raymond. Copyright(R) 2004.
 
-[[RelEngDoc]] [RelEngDoc] link:{releng}[FreeBSD Release Engineering] Murray Stokely. Copyright(R) 2001. The FreeBSD Project.
+[[RelEngDoc]] [RelEngDoc] extref:{releng}[FreeBSD Release Engineering] Murray Stokely. Copyright(R) 2001. The FreeBSD Project.