ging is implied at this step.
>> >>> > > > >
>> >>> > > >
>> >>> > > > The "homepage structure" is detailed in the PIP and composed of:
>> >>> > > >
>> >>> > > >- Ne
; >
> >>> > > > The "homepage structure" is detailed in the PIP and composed of:
> >>> > > >
> >>> > > >- News banner
> >>> > > >- Testimonials
> >>> > > >- Menu
>
uture steps.
>>> > > >
>>> > > >
>>> > > >
>>> > > > On Fri, Feb 24, 2023 at 4:51 PM Kiryl Valkovich
>>> > >
>>> > > > wrote:
>>> > > >
>>> > > > > Asaf, okay
; > On Fri, Feb 24, 2023 at 4:51 PM Kiryl Valkovich
>> > >
>> > > > wrote:
>> > > >
>> > > > > Asaf, okay. I see you have some plan.
>> > > > >
>> > > > > I’m just a bit confused with the steps ordering
d with the steps ordering.
> > > > > Usually, such work starts with “What content do we want to show?”
> > That
> > > > > implies content changes.
> > > > > Then “How can we display this content in the best way?”. That
> implies
> > >
content adjustment.
> > > > Of course, this order is not mandatory, but it usually allows to save
> > time
> > > > on the number of iterations.
> > > > The “Homepage structure” point is defined in the PIP’s scope, so I
> > thought
> > > > it
> > > **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.
> > &g
save time
> > on the number of iterations.
> > The “Homepage structure” point is defined in the PIP’s scope, so I thought
> > it meant content changing is implied at this step.
> > Waiting for the finished site. :)
> > By the way, does someone have any more opinions on
> > > 🤔 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 q
On Fri, Feb 24, 2023 at 5:31 PM Dave Fisher wrote:
> Hi -
>
> While I like this design effort so far -
>
> 1. The design needs to show how the site looks on smaller @media like
> iPhones.
>
The PIP is mainly about the design concepts as displayed in the PIP, before
proceeding with the heavy lift
Hi -
While I like this design effort so far -
1. The design needs to show how the site looks on smaller @media like iPhones.
2. The horizontal carousel at the bottom looks a little awkward. Will it
automatically shift?
3. The website design was refreshed in 2021-2022. It was a difficult and
l
have any more opinions on the topic?
From: Asaf Mesika
Date: Friday, February 24, 2023 at 3:06 PM
To: dev@pulsar.apache.org
Subject: Re: [DISCUSS] PIP-249: Pulsar website redesign
I totally agree with your point Kyril, and as I wrote in the welcome email
- I want to do all you wrote, but it has to
ns.
>
> ---
>
> ## 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
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
Date: Friday, February 24, 2023 at
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 illustr
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
16 matches
Mail list logo
