Hi all,
Please check the new candidate for Apache Avro website:
https://avro-website.netlify.app/
It is based on Hugo and uses Docsy theme.
Its source code and instructions how to build could be found at
https://github.com/martin-g/avro-website.
The JIRA ticket is: https://issues.apache.org/jira/
Hi,
To me this already looks a lot better than the default website, especially
because now it also supports mobile devices.
The exact look and feel for sites like this is always a discussion thing
as a step 1: I don't have any input on this right now.
What I am thinking about are things like:
Whe
Hi Niels,
On Thu, Oct 28, 2021 at 2:29 PM Niels Basjes wrote:
> Hi,
>
> To me this already looks a lot better than the default website, especially
> because now it also supports mobile devices.
> The exact look and feel for sites like this is always a discussion thing
> as a step 1: I don't have
Hi,
This is a huge improvement. Responsive, excellent navigation, syntax
highlighting, ...
The only downside I see was already mentioned by Lee: the landing page is
too empty (also in a mobile browser).
I think we could really benefit from mentioning the unique selling point of
Avro here: "Your D
Hi,
Anyone willing to send a PR with the suggested improvement?
Or at least open an issue with the well formulated text and I will add it!
Regards,
Martin
On Tue, Nov 2, 2021, 18:08 Oscar Westra van Holthe - Kind <
os...@westravanholthe.nl> wrote:
> Hi,
>
> This is a huge improvement. Responsiv
Wow this is pretty neat ! Nice job Martin! A modern website can
encourage more contributions.
I am more interested on content than aesthetics first. Is everything
already migrated? Anything missing? Any issue to report?
On Tue, Nov 2, 2021 at 7:01 PM Martin Grigorov wrote:
>
> Hi,
>
> Anyone wil
On Thu, Nov 4, 2021 at 5:04 PM Ismaël Mejía wrote:
> Wow this is pretty neat ! Nice job Martin! A modern website can
> encourage more contributions.
> I am more interested on content than aesthetics first. Is everything
> already migrated? Anything missing? Any issue to report?
>
Everything is m
Hello!
I realized that I haven't commented on this mailing list thread -- I
made some comments on https://issues.apache.org/jira/browse/AVRO-2175
This looks amazing and we should merge it very soon :D It's not
perfect, but it's really a great improvement and definitely not worst
than the existin
Hi Ryan,
On Sun, Dec 12, 2021 at 1:36 PM Ryan Skraba wrote:
> Hello!
>
> I realized that I haven't commented on this mailing list thread -- I
> made some comments on https://issues.apache.org/jira/browse/AVRO-2175
>
> This looks amazing and we should merge it very soon :D It's not
> perfect, bu
On Mon, Dec 13, 2021 at 9:38 AM Martin Grigorov
wrote:
> Hi Ryan,
>
> On Sun, Dec 12, 2021 at 1:36 PM Ryan Skraba wrote:
>
>> Hello!
>>
>> I realized that I haven't commented on this mailing list thread -- I
>> made some comments on https://issues.apache.org/jira/browse/AVRO-2175
>>
>> This look
Hi,
Shall we replace the old website with the new one ?
I will have time to work on it next week, so if we decide what to do then I
could do it all by myself with my new superpowers (committership!)
Martin
On Mon, Dec 13, 2021 at 1:51 PM Martin Grigorov
wrote:
>
>
> On Mon, Dec 13, 2021 at 9:
Hi all,
+1 from me for moving to the new website
You've done a great job!
--
Oscar Westra van Holthe - Kind
Op di 25 jan. 2022 08:36 schreef Martin Grigorov :
> Hi,
>
> Shall we replace the old website with the new one ?
>
> I will have time to work on it next week, so
rowse/AVRO-3264
On Tue, Jan 25, 2022 at 9:31 AM Oscar Westra van Holthe - Kind
wrote:
>
> Hi all,
>
> +1 from me for moving to the new website
>
> You've done a great job!
>
>
> --
> Oscar Westra van Holthe - Kind
>
> Op di 25 jan. 2022 08:36 schreef Martin
t; related to deciding where and how to put things:
>
> 1) Ensure that we don't break existing links during the migration.
>
> For example https://avro.apache.org/releases.html versus
> https://avro-website.netlify.app/project/download/
The new website has a special page for ne
Here are the things that I'd like to see before the switch, almost all
>> related to deciding where and how to put things:
>>
>> 1) Ensure that we don't break existing links during the migration.
>>
>> For example https://avro.apache.org/releases.html versus
>&
access to my ASF account at the moment, so I won't be able to
> > update the tickets this week.
> >
> >
> >> Here are the things that I'd like to see before the switch, almost all
> >> related to deciding where and how to put things:
> >>
>
RyanSkraba merged pull request #1592:
URL: https://github.com/apache/avro/pull/1592
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr..
olved.html#category-x).
### Tests
- [X] My PR does not need testing for this extremely good reason: manually
verified on the new website.
### Commits
- [X] My commits all reference Jira issues in their subject lines. In
addition, my commits follow the guidelines fro
18 matches
Mail list logo
