Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refresh installation instructions #302

Merged
merged 2 commits into from
Oct 21, 2024
Merged

Conversation

chiphogg
Copy link
Contributor

The old flow of the page dates from the first open source release, when
only bazel was fully supported, and we provided the single-file
packaging as the "lowest common denominator" fallback that worked with
everybody. This summer, we added official CMake support, and just last
week, the community also added support for both conan and vcpkg. This
radically changes and simplifies the recommended installation approach:
now "full install" is the right choice for almost everyone! Accordingly,
it's time to refresh our instructions.

  • Make up-front guidance simpler and more direct
  • Rearrange the table: put Full Install first; unify Full Install
    columns; clean up and explain some text
  • Remove decision flowchart: things are much simpler now, and we don't
    really need it
  • Refresh the bazel instructions to mention 0.3.5 (might as well)
  • Add links and instructions for installing with package managers
  • Move the single-file section after the full install one

I used "checkpoint commits" for this PR, so this last change is in a
separate "pure-move" commit within the PR, to make this easier to
review.

The reviewer can also run au-docs-serve and do A/B comparison between
two tabs:

Fixes #301.

The old flow of the page dates from the first open source release, when
only bazel was fully supported, and we provided the single-file
packaging as the "lowest common denominator" fallback that worked with
everybody.  This summer, we added official CMake support, and just last
week, the community also added support for both conan and vcpkg.  This
radically changes and simplifies the recommended installation approach:
now "full install" is the right choice for almost everyone!
Accordingly, it's time to refresh our instructions.

- Make up-front guidance simpler and more direct
- Rearrange the table: put Full Install first; unify Full Install
  columns; clean up and explain some text
- Remove decision flowchart: things are much simpler now, and we don't
  really need it
- Refresh the bazel instructions to mention 0.3.5 (might as well)
- Add links and instructions for installing with package managers
- Move the single-file section _after_ the full install one

I used "checkpoint commits" for this PR, so this last change is in a
separate "pure-move" commit within the PR, to make this easier to
review.

The reviewer can also run `au-docs-serve` and do A/B comparison between
two tabs:
- https://aurora-opensource.github.io/au/main/install/
- http://127.0.0.1:8000/au/install/

Fixes #301.
@chiphogg chiphogg added the release notes: 📝 documentation PR affecting library documentation label Oct 20, 2024
@chiphogg chiphogg marked this pull request as ready for review October 20, 2024 19:18
@chiphogg chiphogg requested a review from geoffviola October 20, 2024 19:18
Copy link
Contributor

@geoffviola geoffviola left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for keeping the documentation up to date.

Nit: We might want to use some autoformatter like markdownlint + prettier.


Each package manager contains setup instructions on its page for Au. Here are the packages:

- **Conan:** [au](https://conan.io/center/recipes/au)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

Each package manager contains setup instructions on its page for Au. Here are the packages:

- **Conan:** [au](https://conan.io/center/recipes/au)
- **vcpkg:** [aurora-au](https://vcpkg.link/ports/aurora-au)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

- A base dimensionless unit (`unos`)

!!! note
_How_ do you go about constructing other units from these? By **composing** them. For example,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I'm not sure why github doesn't like this character. It might want an escape character in front of it. The rendering looks fine.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think github is just off base here in its syntax highlighting. I'm pretty confident the contents are just fine.

@chiphogg chiphogg merged commit 06b074c into main Oct 21, 2024
10 checks passed
@chiphogg chiphogg deleted the chiphogg/install-refresh#301 branch October 21, 2024 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release notes: 📝 documentation PR affecting library documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document vcpkg install
2 participants