Antora UI Updates

[julioest]

Description

This PR is meant to be first iteration of boost doc styling update, giving it a previous look-and-feel ui

Notes

• Modern sans-serif font fallback stack
• Standard font size across elements and components
• Fixes https://github.com/boostorg/website-v2-docs/issues/161

[cppalliance-bot]

An automated preview of the documentation is available at https://204.site-docs.prtest2.cppalliance.org/contributor-guide/index.html

[vinniefalco]

its antora-ui not boost-ui

[vinniefalco]

This isn't going to actually be merged right? Because the playbook references a personal repository.

[alandefreitas]

personal repository

Should we move this to a cppalliance repo for now or already a boostorg repository?

its antora-ui not boost-ui

I think the idea is that boost-ui is what we're going to use for boostorg/website-v2-docs and antora-ui is storing a backup of the work the other guys did on that other ui bundle for the cppalliance (the other font, the original admonition, etc...).

[alandefreitas]

Also, the fonts still look different over here.

The UI bundle:

Boost.URL documentation:

[vinniefalco]

as far as I can tell we only need one UI not two.... or am I missing something?

[alandefreitas]

as far as I can tell we only need one UI not two.... or am I missing something?

Yes. We just need one.

I think you mentioned other UIs for standalone projects such as MrDocs in the past but I think bundles related to the C++ alliance only are outside the context of this discussion.

At some point, I told Julio I thought it could be a good idea to back up what we had before just in case. I'm not sure we really need it because we can just go back in history but anyway...

In any case, all the work is going into a single UI bundle.

[julioest]

@alandefreitas want me to port over the changes from my personal repo to my fork?

Disregard. This is not needed.

[alandefreitas]

This PR also needs to remove the antora-ui directory and update the bash scripts to stop building the UI bundle in antora-ui (that's going to happen in https://github.com/julioest/boost-ui (or whatever it becomes) now

[vinniefalco]

What does the User's Guide look like now?

[alandefreitas]

What does the User's Guide look like now?

https://204.site-docs.prtest2.cppalliance.org/user-guide/index.html

[cppalliance-bot]

An automated preview of the documentation is available at https://204.site-docs.prtest2.cppalliance.org/contributor-guide/index.html

[vinniefalco]

What is this "Merge branch 'boostorg:develop' into develop?" It looks like a merge commit... please fix the commit log for this pull request to be linear.

[cppalliance-bot]

An automated preview of the documentation is available at https://204.site-docs.prtest2.cppalliance.org/contributor-guide/index.html

[julioest]

This isn't going to actually be merged right? Because the playbook references a personal repository.

@vinniefalco, in this case, could we get a dedicated repo for Antora UI updates? Thanks!

[vinniefalco]

No, it is better to put the UI in the same repository as the documentation. We had it in a separate repository and it was annoying, if for no other reason that now there is one more different place to report GitHub issues.

[julioest]

Roger that. I'll make the necessary changes

[cppalliance-bot]

An automated preview of the documentation is available at https://204.site-docs.prtest2.cppalliance.org/contributor-guide/index.html

[cppalliance-bot]

An automated preview of the documentation is available at https://204.site-docs.prtest2.cppalliance.org/contributor-guide/index.html

[julioest]

This PR didn't follow the proper Git workflow, so closing it. A new PR with the correct process will be up soon. Thanks!