Hello all, it's been a few days, and we've been busy ourselves with other work, but I was wondering if anyone is willing to share particular feedback on this iteration / prototype of the landing page for airflow?
We're looking for feedback on the following areas: 1. Look and feel 2. Organization (header elements, linking to ReadTheDocs documentation), etc. 3. If this is in a mostly-reasonable direction, perhaps we'll start working on a PR where we can take more direct feedback on the integration of the code, the changs to continuous integration (travis), and other important considerations. Something good about the tools we used is that continuous integration for this website would be quite easy to setup. Jekyll supports a number of tests to ensure quality (broken links, misspellings, etc) Something we haven't thought about: - Whether we want to move towards sharing styling between website and docs (as brought up by Kamil earlier). Thanks! -P. On Thu, Mar 21, 2019 at 12:38 AM Kamil Breguła <kamil.breg...@polidea.com> wrote: > Gatsby is awesome. I use it in my company (Polidea) to create our > website. I can help with moving the site if we want to use it. This is > useful for us because it will allow you to build a website based on various > data sources. > > I only warn you about using "CSS in JS" library. This results in the > closure of our project to one technology - React. It will not be possible > to use the same CSS code to build documentation. SQL Alchemy builds the > website and documentation separately, but shares one theme - > https://www.sqlalchemy.org/ > > I will look more closely and provide feedback in the near future. However, > this is a good start to development. > > On Tue, Mar 19, 2019 at 1:32 AM Maxime Beauchemin < > maximebeauche...@gmail.com> wrote: > > > I'm curious to see the source, do you mind sharing the repo? > > > > Side note: I used Gatsby recently and thought it was pretty amazing for > > building static sites and beyond. > > > > Quick nit-picky comments: > > * logo is too small height:50px (along with margin-top: -10px) looks much > > better > > * dark footer needs padding > > > > Max > > > > On Mon, Mar 18, 2019 at 4:57 PM Aizhamal Nurmamat kyzy > > <aizha...@google.com.invalid> wrote: > > > > > Hello all, > > > > > > As suggested previously > > > < > > > > > > https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-11+Create+a+Landing+Page+for+Apache+Airflow > > > >, > > > I have been working with Pablo (ccd) on the landing page for Apache > > > Airflow. The site is ready and you can see at > > > https://aijamalnk.github.io/airflow-website/ > > > > > > I would love to hear your thoughts on it, and suggestions for > > improvement. > > > > > > FYI, I have tried using both Jekyll and Hugo for building a new > template > > > for Airflow, but it was taking too much time and the progress was slow. > > > Then I decided to try out Beam’s website code as a template, and it > > suited > > > well for Airflow as open source projects have similar information > > > architecture, eg Documentation, Community, Roadmap, etc. We made sure > to > > > give it a unique look-and-feel for Airflow. I also added some content > > into > > > new pages, like Get Started, Community, Blog. > > > > > > I would love to hear feedback from the community as to whether this > seems > > > like a good landing page for Airflow; and if it does, I’d prepare a > plan > > to > > > bring the landing page into a feature branch of the Airflow repository, > > and > > > work to productionize it. > > > > > > Main areas where I’d like feedback: > > > > > > - > > > > > > Look and feel > > > - > > > > > > Organization of the site > > > - > > > > > > Interface with the existing user docs, and the wiki (see > Documentation > > > section) > > > - > > > > > > How much of the existing documentation is worth moving to a landing > > > page, and how much is worth keeping in ReadTheDocs > > > - > > > > > > If you think the page is on the right track, thoughts on moving > > forward > > > > > > > > > Thanks, > > > > > > Aizhamal > > > > > > > > -- > > Kamil Breguła > Polidea <https://www.polidea.com/> | Software Engineer > > M: +48 505 458 451 <+48505458451> > E: kamil.breg...@polidea.com > [image: Polidea] <https://www.polidea.com/> > > We create human & business stories through technology. > Check out our projects! <https://www.polidea.com/our-work> > [image: Github] <https://github.com/Polidea> [image: Facebook] > <https://www.facebook.com/Polidea.Software> [image: Twitter] > <https://twitter.com/polidea> [image: Linkedin] > <https://www.linkedin.com/company/polidea> [image: Instagram] > <https://instagram.com/polidea> [image: Behance] > <https://www.behance.net/polidea> >
