-
-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frontpage re-design #800
Comments
Why can't recent blog post be just... last blog post? |
Although I'm a big fan personally, I'm starting to think that having a slideshow/art-gallery isn't entirely a good idea. It can become too much a matter of personal opinion and taste, and the people who comment may be outliers (be they minimalists or lovers of the baroque), some want a Julia set, others hate background graphics... The most economical SVGs I can make are linear gradients - you can easily get this beauty for 727 bytes: but as soon as I try to add a handful of straight lines it creeps up to 30K or so. This might be something to do with how Cairo outputs SVG - probably not very efficiently. Funny how high quality SVGs start to get as big as low quality PNGs... |
Sorry this is exactly what I meant, but it's not the case at the moment. You may know that stuff went from a Hugo backend to Franklin backend, I ported most of the functionality but there's a few things missing, one was the auto generation of the list of blogs (now done) and another one which I realised when writing the list here is the list of few X recent blog posts. It's an easy fix that I'll do, I just added it to the list to not forget. @cormullion I think 30K is still ok. And IMO the linear gradient is not bad! (I just look at the 27000 and it makes me happy so...) maybe it could be a semi-transparent overlay over some actual Julia code? |
|
1: yes so this: would be removed from the front page and arrive in some form on the community page instead (that's a suggestion). In any case it loads some massive gifs which don't really serve a purpose, and that should be removed. The Editor/Tools stuff should go, I think, on a /tools/ page which could be linked to here: 2: this (note: you may have it blocked if you use uBlock or similar) I think it's potentially a good idea to have a youtube link here but it shouldn't be as big |
Can you add text as a background using HTML and CSS? - I find text tricky in SVG - either it gets converted to thousands of curves (-> big files) or it stays as text inside the SVG, then needs to be styled somehow with available fonts. |
|
@cormullion You just make SVG image without text and put it as background of the .jumbotron div, like the way it is now. |
Right, so the key message is that there's lots of packages right? there's already that "Packages" section which is quite good? The tabs as they are now are all outdated anyway, what we could have instead is something that looks like it with some simple code on the left and the output on the right showcasing "nice examples" of how Package X can be used to do Y. This is what I suggested in the list except that I suggested it be in "community" but I agree it could be on the front page. Packages that could be shown there could be:
There could maybe also be a list of the 10 most starred packages and what they do? |
@tlienart That's right. Packages and Ecosystem sections should be merged, somewhere along the lines of what you've proposed. Drop GIFs (maybe replace them with plain images) and update the lists of packages. But it seems that you'd arrive at something very similar to the current Ecosystem section, so why not just improve it and drop the packages one? What do you think about dropping the JuliaCon section though? There's already a link to YouTube channel. |
Yeah I think I'm favourable to that. In any case we should do this in chunks of work so that we don't change everything at once and can get feedback on stuff. In order to not clash on things would you be interested in one of those items? |
I am interested. I'd go with removing JuliaCon section first (from the front-page). It maybe should be linked somewhere else. |
well it's already linked in the banner... |
also bootstrap |
@tlienart Users should be able to close the banner, though (and to have that preference stored in localStorage). It's a bit distracting to be displayed every time. |
@tlienart I uploaded a few SVG banner-type images here. I'm not saying you should use any of these in particular, just they're the kind of image I can make for around 50kb or so. They've all been optimized so are probably as small as they can get. Whether they're too dull or too eye-catching is another matter altogether... :) 🤣 |
Let's open separate issues for redesign of other pages. I also have some graphics I use in my slides that have logos of universities and books that I can add. |
@ViralBShah yes I think here I added "community" because some content would potentially be shifted over to that page but I agree that could be done in a second phase. |
Just taking a step back here. I think the point of the front page redesign should not to be minimal or lighter to load, but to get a newcomer to the project excited about Julia and find the things they need quickly. Within that experience, we certainly want a lighter / fast loading page. |
The main thing I wanted to do is a revamp of that ecosystem thing on the front page which would highlight top packages, maybe show some key code / plots |
@tlienart I added a few more versions of the Bowyer–Watson/Delaunay triangulation background image with varying opacities and with correct graph coloring here (since someone commented that adjacent triangles had the same color... :) But perhaps it would be simpler to just have a plain colored background...🤣 |
@JeffreySarnoff Is that really such an issue? It does very well if it's not just a few words left over, like here: Anyway, that section will be redesigned per the points mentioned above, so a better design may be implemented. |
It is possible to have the best of both, extending the box when the excess is small and overlaying below the image otherwise. The hanging phrase looks unprofessional to me. |
Anecdata: I really like the plots gifs and they were one of the reasons why I started using Julia. You could make them |
not sure webm is supported on Apple mobile devices... |
They support MP4, which would probably still be an improvement.
…On Mon, 18 May 2020, 19:03 cormullion, ***@***.***> wrote:
not sure webm is supported on Apple mobile devices...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#800 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNZA6KOBSBOTCCDMR4EFY3RSFZ67ANCNFSM4M7QOEZQ>
.
|
@tlienart Last two items from "front-page specific" should be checked. |
I think a major next step is to overhaul the ecosystems. People (newcomers) often want to know what is a good set of well-tested robust packages for basic capabilities. And the ecosystems needs to point to that. I think on the main page, this should translate into a collection of org logos, which when clicked take one to a page in |
[reply to now deleted comment] Minimalist designs are cool and can be fun, but the downside is the challenges they pose for accessibility and discovery. Hover text can be difficult to get right on both desktop and mobile. The tiny images are good, but bigger downloads are just around the corner, so it may not save much bandwidth in the long run. A change in branding would be a fun discussion! 😃 I think the use of those four coloured dots in a row is getting interestingly close to Julia Computing's branding... |
[reply to now deleted comment] I think those are possibly the dullest web pages I've ever seen. 😂 Probably not the sort of thing to get people excited about Julia... |
Following #791 and a discussion on Slack, here are some actionable things we could work on to make some pages more ergonomic and lighter to load.
Front page specific
Misc
4.3.x
which is (I believe) jQuery freeThoughts & actionable points are welcome. Please bear in mind that at some point someone will have to do it so if you want us to do large changes (e.g. change framework) please provide a full working POC otherwise we will likely not do it.
I'll try to tackle some of these over the weekend but will likely need help for things like
The text was updated successfully, but these errors were encountered: