If you want content suggestions, a list of things/tools/links that ingest Avro (python, map reduce, drill, Azure data factory, Aws Athenea/Redshift/Glue, Spark, Google Cloud/BigQuery, Hadoop, Kafka etc.) helps make the case that your avro producing whatever will have wide support.
On Fri, Oct 29, 2021 at 9:58 AM Lee Hambley <[email protected]> wrote: > > Kudos on the new site, looks really nice. > > If I may offer some advice: > > - lots of unused space above the fold on desktop, I think msgpack has a great > above-the-fold demo here, showing what msgpack is with a solid example > > Regarding what Avro "is" to me, the only binary serialization format with a > good story with forward/backward compatibility, usable as serialization, > cold-storage (record object format) and IPC. The schema canonical form, > schema registry, and the strong guarantees the tool offers for building > future proofing into your APIs is really amazing. I know that's not > 1000%out-of-the-box without getting a 3rd party schema registry, but it's > really what makes Avro Avro in my eyes. > > Highlighting some of these amazing use-cases prominently on the website would > be quite amazing, I think, as often times the Eureka! moment about these key > distinguishing features only arises on deep inspection of the doc and specs, > nothing that most people have time for browsing the web. > > Ahoy, good weekend, and good work! > > Lee Hambley > http://lee.hambley.name/ > +49 (0) 170 298 5667 > > > On Thu, 28 Oct 2021 at 15:42, Martin Grigorov <[email protected]> wrote: >> >> Hi Niels, >> >> On Thu, Oct 28, 2021 at 2:29 PM Niels Basjes <[email protected]> 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 any input on this right now. >>> >>> What I am thinking about are things like: >>> Where do we want to host this one? >>> - On the existing Apache infrastructure? >> >> >> Using exisitng Apache infrastructure should work! Other projects also use >> Hugo, e.g. Apache Airflow. >> >>> >>> - Using Github pages? This would make it possible to automatically >>> regenerate the site on a push to the master/main branch. >>> - Somewhere else like the netlify this demo is hosted on? >> >> >> I had a small issue with Netlify - it does not use `--recursive-modules` for >> cloning and thus does not have the Docsy theme. >> I didn't spend time in debugging it. >> But if Avro team prefers Netlify then we could add the theme resources >> directly, i.e. not use Git modules. >> >>> >>> >>> Also: >>> Do we want this to be a separate repository? >>> Or do we want this to be part of the main code repository? >> >> >> I don't see problems with any of these. >> Maybe it will be one idea easier if it is in the same repo. This way >> "build.sh dist" could copy the C/C++/C# docs in the same Git repo. >> >> Regards, >> Martin >> >>> >>> >>> Niels >>> >>> >>> >>> On Thu, Oct 28, 2021 at 10:44 AM Martin Grigorov <[email protected]> >>> wrote: >>>> >>>> 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/browse/AVRO-2175 >>>> >>>> I am not web designer, so some things may look not finished. >>>> I've just copied the HTML content from the old site ( >>>> https://avro.apache.org/) and converted it to Markdown for Hugo. >>>> >>>> Any feedback is welcome! With Pull Requests would be awesome! >>>> >>>> Regards, >>>> Martin >>> >>> >>> >>> -- >>> Best regards / Met vriendelijke groeten, >>> >>> Niels Basjes
