enh: adhere to style guide and reorg landing #598
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lwasser
commented
Dec 13, 2025
| --pyos-color-secondary-highlight: #591bc2; | ||
| --pyos-color-tertiary: #a66c98; | ||
| --pyos-color-dark: #542568; | ||
| --pyos-color-dark: #33205c; /* Brand dark purple - #33205c */ |
Member
Author
There was a problem hiding this comment.
We should use our brand palette and stick to the purple tones for a more on brand and consistent vibe.
lwasser
commented
Dec 13, 2025
| --pst-font-family-heading: "Poppins", sans-serif; | ||
| --pst-font-family-base: "Poppins", sans-serif; | ||
| --pyos-font-family-h1: "Itim", serif; | ||
| --pst-font-family-base: "NunitoSans", sans-serif; |
Member
Author
There was a problem hiding this comment.
Align with website fonts!
lwasser
commented
Dec 13, 2025
| have a few simple extensions in another language such as C or C++. | ||
|
|
||
| In the future, we want to provide resources for packaging workflows that require more complex builds. If you have questions about these types of package, please [add a question to our discourse](https://pyopensci.discourse.group/) or open an [issue about this guide specifically in the GitHub repo for this guide](https://github.com/pyOpenSci/python-package-guide/issues). There are many nuances to building and distributing Python packages that have compiled extensions requiring non-Python dependencies at build time. For an overview and thorough discussion of these nuances, please see [this site.](https://pypackaging-native.github.io/) | ||
| For comprehensive guidance on packaging compiled projects with C/C++/Fortran/Rust extensions, see the [Scientific Python Development Guide on compiled packaging](https://learn.scientific-python.org/development/guides/packaging-compiled/). This is the best reference for complex builds and covers scikit-build-core, meson-python, maturin, and other modern build backends. |
Member
Author
There was a problem hiding this comment.
Really, Henry's guide is the best here, so I'd prefer to link to them!
lwasser
commented
Dec 13, 2025
Member
Author
|
One target is not working, and I'm not sure why, as it clearly exists. i am going to merge this so our branding and the intro reorg sticks and we can fix the link at a later time. I've triple-checked that it's there and works. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Style realignment + color tweaks to align branding better. I also reorganized the landing page so it's a bit cleaner.