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

Edited landing page and installation pages. #3716

Closed
wants to merge 1 commit into from

Conversation

dwelsch-esi
Copy link
Contributor

Edited all installation pages including quick start.
Edited landing page.
Removed legacy conf.py and CSS files as unnecessary.
Fixed parsed literal box background color.

Signed-off-by: Dave Welsch <dwelsch@expertsupport.com>
aside.toc-drawer ul ul ul ul {
display: none;
/*
* Highlight color for code segments
Copy link
Contributor

Choose a reason for hiding this comment

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

Code snippets within .. parsed-literal:: are still not changed to new background color? Have you verified this?

image


aside.toc-drawer ul ul ul ul {
Copy link
Contributor

Choose a reason for hiding this comment

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

Could you remind me why we initially included this, and why it's no longer necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This was a workaround to keep the lower-level entries from showing up in the page TOC (the one in the right-hand sidebar). I think I found a less hack-y way to do this, but I don't recall exactly what offhand.

Comment on lines -6 to -11
.toctree-l3 {
display: none;
}
/*
* Table options
*/

[for^="toctree-checkbox-"], [id^="toctree-checkbox-"] {
visibility: hidden;
Copy link
Contributor

Choose a reason for hiding this comment

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

Could you remind me why we initially included this, and why it's no longer necessary?

.. code-block:: bash

python3 -m pip install aimet-torch
Prerequisites
Copy link
Contributor

Choose a reason for hiding this comment

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

We decided to remove the prerequisites section from the quick start guide for pip install aimet-torch because these are no longer required for installing aimet-torch. The package is now compatible with all platforms by default. We only wanted to indicate that we have verified it using one specific host configuration, which is why we included that information after the pip install aimet-torch command.

So, could you please revert this change?

cc; @quic-kyunggeu

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Rather than a Prerequisites section then, how about a note laying out the test platform, but say it should work on all or most platforms?

@@ -26,19 +20,29 @@ AIMET PyTorch package has been tested using the following recommended host platf
* Nvidia GPU card (Compute capability 5.2 or later)
* Nvidia driver version 455 or later (using the latest driver is recommended; both CUDA and cuDNN are supported)

Verification
============
Installating AIMET
Copy link
Contributor

@quic-hitameht quic-hitameht Jan 8, 2025

Choose a reason for hiding this comment

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

Typo here: Installating

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oops. Fixed.

@@ -1,283 +0,0 @@
.rst-content .hideitem {
Copy link
Contributor

@quic-hitameht quic-hitameht Jan 8, 2025

Choose a reason for hiding this comment

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

Could you tell why the legacy stylesheet and conf.py file were removed? Is this impacting the rendering of the new documentation in any way?

If not, can you please revert these two files? We will eventually delete entire legacy directory.

We might need these two files if we want to build the old docs for the past releases (highly unlikely though) - we can get these two files from the git history but as I said we would to delete entire directory at some point in future.

Copy link
Contributor

@quic-hitameht quic-hitameht left a comment

Choose a reason for hiding this comment

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

Please address the requested changes. Thanks.

Comment on lines +28 to +29
.. note::
See the :doc:`glossary <../glossary>` for explanations of terms and acronyms used on this website.
Copy link
Contributor

@quic-hitameht quic-hitameht Jan 8, 2025

Choose a reason for hiding this comment

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

Would this be the ideal spot on the landing page to feature the glossary, considering it's the first thing users are likely to look at...?

How about putting after the release notes page..

@dwelsch-esi
Copy link
Contributor Author

Closing. Re-creating without the formatting and file deletions.

@dwelsch-esi
Copy link
Contributor Author

Closing.

@dwelsch-esi dwelsch-esi closed this Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants