oops! s/process/project/ On Tue, Jan 6, 2015 at 12:57 PM, Tony Kurc <[email protected]> wrote:
> Hey! It looks awesome! The existing site was put together a placeholder > and we went with a very generic layout that worked well with Apache CMS and > contained all the information expected of an apache process. > > This is a big improvement! For people new to the project, it gives a nice > upfront screenshot, with big fat links for things I care about people > seeing! > > Some things I didn't like about the existing site are the glyphicon links > to "external" sites on the menu. I used "link", but I think it was meant to > be used for "permalink". Also, we kind of took a best guess about what > should go in each dropdown in the menu. I'm pretty sure it could be better > organized. I'd also like to see the awesome guides that people wrote have a > consistent theme with the website and maybe have pdfs so old-school folks > can print them out (which may be a dumb idea ;) ) A pet peeve of mine of > projects is having a hard time finding the documentation I need, like > javadocs or specifications - and keeping around the older versions of the > documentation. I think we're still working on these - since you retained > the menu up top it should be straightforward to have a robust documentation > dropdown. > > The blue you used is more of a reddish or purplish blue - the blue used in > the app is more of a greenish blue. I'm kind of curious what a greener blue > would look like ... did you mock one up and it looked bad? Or maybe a more > fundamental question, should the website evoke the theme of the app? I > don't know how I feel. > > Tony > > > > > > On Tue, Jan 6, 2015 at 11:59 AM, Joe Witt <[email protected]> wrote: > >> I'd say the two sides of the spectrum as examples are: >> >> http://kafka.apache.org/ [super minimalist] >> http://aurora.incubator.apache.org/ [ quite fancy looking ] >> >> Both in my opinion are beautifully done and make it easy to get the >> content >> needed. >> >> I think these (and others) provide great examples that both sides of the >> spectrum have merit. >> >> What is most important to me is that we as a community rally behind those >> with the expertise and willingness to contribute in this space. >> >> Thanks >> Joe >> >> On Tue, Jan 6, 2015 at 11:34 AM, Joe Witt <[email protected]> wrote: >> >> > Both are bootstrap based. Each is an iterative improvement. And we >> just >> > keep iterating as folks have time, willingness, and expertise to do so. >> > >> > I agree that this new look does not distinguish a brand. But we're not >> > mature enough to worry about that yet. We just need enough of the right >> > info laid out enough to help grow a community and get folks the info >> they >> > need. We need it laid out in a way that multiple folks can contribute. >> > Once we have a release, recruit some committers, demonstrate progress on >> > the Apache Way and grow then perhaps branding becomes a bigger deal. >> > >> > ..this motivates me to spawn another thread about the type of community >> we >> > want to be... >> > >> > Thanks >> > Joe >> > >> > >> > On Tue, Jan 6, 2015 at 11:13 AM, Adam Taft <[email protected]> wrote: >> > >> >> This isn't a downvote -- I think it indeed looks good. But in terms of >> >> constructive criticism... >> >> >> >> I think the mockup looks like a very generic "bootstrap" site, similar >> to >> >> a >> >> million other bootstrap based sites. I'd personally almost prefer the >> >> existing utilitarian website over a bootstrap theme, simply because it >> >> doesn't try to be anything more than what it is. >> >> >> >> This approach might be an acceptable tradeoff for the project; having >> the >> >> bootstrap look & feel is obviously a resource savings and available at >> the >> >> right price point. But the site mockup definitely doesn't distinguish >> the >> >> Apache NiFi "brand" in anyway. In fact the opposite, the brand gets >> >> watered >> >> down with this look. >> >> >> >> As a funny side note, humorously for me, this was the first thought in >> my >> >> head when I saw the site: http://dilbert.com/strips/comic/2010-04-01/ >> >> >> >> Adam >> >> >> >> >> >> On Mon, Jan 5, 2015 at 7:39 PM, Aldrin Piri <[email protected]> >> wrote: >> >> >> >> > In partial fulfillment of the goals of NIFI-162, I set some time >> aside >> >> to >> >> > put together something a bit more visually appealing as a face for >> the >> >> > project. >> >> > >> >> > My work can be found at: https://github.com/apiri/apache-nifi-site >> >> > >> >> > Currently, work focused around the homepage, but similar styles >> would be >> >> > applied to more content driven pages minus the large headlining >> >> sections. >> >> > >> >> > The relevant technology colophon is provided in the README on Github >> >> but is >> >> > primarily driven by Bootstrap, existing image resources included with >> >> the >> >> > project and current site, and other "artwork" which I created myself. >> >> > >> >> > I am neither a UX expert nor am I a renowned front end designer, so >> all >> >> > input is welcome. As a "version 1.1" I would like to adjust the >> site to >> >> > converge more with the application. Ideas for this are inclusive of >> >> points >> >> > such as bringing the toolbar styling and color scheme from the >> >> application >> >> > to the site. >> >> > >> >> > If this seems like a reasonable path forward and there is sufficient >> >> > support, I can look at the next steps to get this integrated with the >> >> > project, optimization, and integration with the application itself. >> >> > >> >> > To aid in showing the intangibles that can't be seen from an image, I >> >> have >> >> > a copy of this design hosted at http://aldrinpiri.com/apache-nifi/. >> The >> >> > links are currently nonfunctional as they were taken from the current >> >> site. >> >> > >> >> > Thanks! >> >> > >> >> > --Aldrin >> >> > >> >> >> > >> > >> > >
