-
Notifications
You must be signed in to change notification settings - Fork 60
Redesign and clean project homepage #113
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
base: main
Are you sure you want to change the base?
Conversation
|
Love the new look! In terms of flow, I wonder if there shouldn't be like a 3-line hello-world example directly after the heading. The current example which comes a bit later feels a bit heavy. |
|
I really liked how clean and streamlined the page used to be
https://archive.ph/xi0Gl
This PR is a great step in that direction. I second having a shorter
example and shorter motivation section
…On Fri, 26 Dec 2025, 21:54 Chris Fonnesbeck, ***@***.***> wrote:
*fonnesbeck* left a comment (pymc-devs/pymc.io#113)
<#113 (comment)>
Maybe an engaging plot in the upper right corner here?
image.png (view on web)
<https://github.com/user-attachments/assets/b0a3867a-6061-4d0c-bd6e-08b132a1fbd4>
—
Reply to this email directly, view it on GitHub
<#113 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACCUIS7AZWOV57L4EUU2D4DWOBNAVCNFSM6AAAAACP7V7TAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOJTGM2TMMRVGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
I am currently leaning towards not having any code on the landing page, but I could be easily convinced otherwise. My reasoning is the people reading this landing page will mostly be people who don't know what PyMC is and are probably not very technical. Users will directly click somewhere on the navbar (if they don't directly go there), more technical people will probably either land on github or quickly go to the "getting started" button or examples nabvar section. If we add a full fledged example like we have now it will be too much and discourage people looking for a conceptual high level intro from going over the landing page. If we add a simple code example I think it will be skipped by people not interested in it but also won't really be valuable for people looking for a code-first intro either.
I also agree it is an improvement over the current state. However, it also feels more like a github readme than an actual landing page for a project website. It still feels a bit too cramped, with a lot of small font text and the badges would clash with the style/aesthetic of the page if we added them back.
I agree it is a bit too empty and simple right now (no image, no changing background between "rows", no animation). |
|
My 2 cents is you dont need code on the front page anymore either. Most sense is most people building a pymc model these days is likely using a AI model of some sort and the need for basic starter code like this is going away |
|
Putting myself into the shoes of a user, I'd like to really just see any line of code to get a rough idea of the direction this is going. Maybe it's literally just |

My idea is to improve the homepage so it acts as a landing page for the project and library,
for now I have still kept the example code, but I think it is probably better to convert
that into a "getting started" page instead. I think we should also think about a different
view for the ecosystem section, open to ideas and to keeping only a handful of libraries
as a highlight.
The main inspirations have been the arviz and the polars pages,
but most landing pages nowadays have a similar feel of large column layout with ~screen size
rows of content with little text and grids/icons.