hi - to rephrase my earlier email, thank you for the contribution
"AryanVBW" and please, it would be nice to have an introduction. Are you
subscribed to the listserv?  How are you involved in using fineract?

I think these changes are significant enough and anyway are the "front
door" of our project :  i.e. our Website home page. So, in that way, I
think that they should be discussed first here on the listserv at least a
little bit.  I'm supportive of the changes, with a few tweaks.  I'm now
making comments on github.  So, thank you.




On Sun, Jan 12, 2025 at 9:08 AM Ádám Sághy <adamsa...@gmail.com> wrote:

> Hi
>
> Usually I dont mind any visual upgrade, but personally I really dont like
> this hover effect which moves the hovered item with a couple pixels up and
> to the right... 😵
>
> The rest looks okay to me but this hover effect makes me dizzy...😵‍💫
>
> Regards,
> Adam Saghy
>
> Sent from my iPhone
>
> On 12 Jan 2025, at 16:50, James Dailey <jdai...@apache.org> wrote:
>
> 
> Thanks for bringing this to the attention of the community.  I, for one,
> was unaware.
>
> Can the person proposing the PR send an email and explain?
>
>
> On Sun, Jan 12, 2025 at 5:52 AM Michael Vorburger
> <m...@vorburger.ch.invalid> wrote:
>
>> Hello,
>>
>> Hope you are all doing well.
>>
>> I stumbled, by coincidence, over
>> https://github.com/apache/fineract-site/pull/35.
>>
>> It "looks cool" to me, but at my current level of involvement in this
>> community I am not comfortable to "just" merge this major visual overhaul
>> of this community's https://fineract.apache.org/ homepage alone.
>>
>> Would others like to contribute to reviewing, and merge, if OK?
>>
>> Or does anyone note any objections to this overhaul?
>>
>> Tx,
>> M.
>>
>> PS: One [minor] thing this includes, other than the more important visual
>> overhaul, is drop the use of https://about.scarf.sh (with this change),
>> which given yesterday's "[NOTICE] New Content Security Policy for all ASF
>> project websites" to annou...@infra.apache.org & us...@infra.apache.org
>> might have to go anyway.
>>
>

Reply via email to