While I find the proposed visual changes okay, I'm unsure about the homepage structure.
I'd add one obvious point to the Goal section that can be formulated differently, but eventually is: - **The goal is to get more companies to start using Pulsar.** In other words, the landing page should **sell** the project to potential users. The defined scope of this PIP includes the "Homepage structure" point. I will try to express my thoughts on this. ## Add "Trusted by" or "Used in production" section One of the best hooks to attract new customers is to show that their peers or more prominent players use it. This is why I think it's essential to show the list of companies that use Pulsar as closer to the page top, as possible. *Kafka in some form has this info on the first screen* <img width="1276" alt="Screenshot 2023-02-24 at 8 18 35 AM" src=https://user-images.githubusercontent.com/9302460/221116492-b77cb8e9-eca1-46bd-b457-6889f4e708b6.png> *Confluent has it on the second screen* <img width="1423" alt="Screenshot 2023-02-24 at 8 08 06 AM" src=https://user-images.githubusercontent.com/9302460/221114783-4f22394e-d1fd-4640-8264-3b137f44e2a1.png> *StreamNative has it on the second screen* <img width="1425" alt="Screenshot 2023-02-24 at 8 19 35 AM" src=https://user-images.githubusercontent.com/9302460/221116665-6749212f-749f-4221-b175-07261a6d2ed5.png> *Redpanda has it on the second screen* <img width="1391" alt="Screenshot 2023-02-24 at 8 27 40 AM" src=https://user-images.githubusercontent.com/9302460/221118114-aabaee99-f6ef-4586-b7df-02c5ca3b24a6.png> The homepage structure proposed in the PIP doesn't have a list of the companies on the page itself. Instead, it has a testimonials list at the **bottom** of the page with a link to case-studies. ## Too much text on the second screen Users don't like to read long texts on landing pages. They'll just skip it. Show the same or similar text in a bullet-point-like style would be better. <img width="838" alt="Screenshot 2023-02-24 at 8 33 50 AM" src=https://user-images.githubusercontent.com/9302460/221119160-5a39c7c9-ad68-4332-961a-e941f3a76693.png> ## The Pulsar Features section Questions the potential user implicitly asks when they scroll the landing page sound like: > 🤔 How can this project help me to solve my pain points? > 🤔 Why should I "buy" this? The answers to this question aren't limited to the technical features list. The current PIP doesn't seem to answer these questions. --- ## Alternative page structure proposal 🥑 Here it is: https://pulsar-site-three.vercel.app/ I would be happy to work with the designer if most users prefer the PIP's visual style. My goal is not to compete here "just for fun". My company works on a product for Pulsar users, so I'm in some kind of dependent on a wider Pulsar adoption. Thank you. From: Yu <li...@apache.org> Date: Friday, February 24, 2023 at 3:55 AM To: dev@pulsar.apache.org <dev@pulsar.apache.org> Subject: Re: [DISCUSS] PIP-249: Pulsar website redesign Hi @asafm and @emidio-cardeira thanks for your great work! You've contributed new designs (with colors/elements/... that have not been used) for Pulsar, which is a big step for the community. Preiviously we've collected some rules at Pulsar Design Style Guide [1], which are used to create illustrations in docs. If this new look is accepted, can you document the design rules/best practice? They should be available in the Contribution Guide [2]. In this way, other contributors can follow and create designs in high quality and consistent style. Thanks! ~~~~~ [1] https://docs.google.com/document/d/16Hp7Sc86MQtL0m8fc2w_TrcKXAuglwRwHmdmwfk00mI/edit#heading=h.b8ogodj5sj [2] https://pulsar.apache.org/contribute/ On Fri, Feb 24, 2023 at 5:27 AM Asaf Mesika <asaf.mes...@gmail.com> wrote: > Hi, > > PIP issue: https://github.com/apache/pulsar/issues/19611 > > One of the key elements that attracted me to Pulsar was how awesome it is - > built in 2012 yet fits the new strategy of being cloud-native - simply > incredible. It's not only that - it has so many outstanding features, > making it a cutting edge, modern powerhouse in the messaging system > category. > > Yet, its site does not reflect that. > It does the opposite. > People new to Pulsar, not knowing it as we do in the community, would think > it's an old, unmaintained technology, and maybe not even bother reading the > landing page. > > This is why I embarked on a journey to improve Pulsar web-site, in bite > sizes. My first step was improving the landing page copy for the elevator > pitch, opening paragraph, and the feature descriptions (In this PR > <https://github.com/apache/pulsar-site/pull/349>) > > Today, together with my friend, co-worker and designer Emidio, I would like > to propose the second step: revamp the landing page structure and most > importantly - the website look and feel. > > The PIP <https://github.com/apache/pulsar/issues/19611> contains: > * The screenshots for it > * A "live" Figma view for it > * Detailed explanation of what was changed and why. > > I think you'll love it. > > Happy to hear your thoughts. > > > Asaf Mesika >
