Refresh the Website! #261
Comments
|
Put it on tweeter too ;-) |
|
@piranna don't you own the NodeOS twitter account? or is that @groundwater (who I never see around :( ) |
|
It was created by @groundwater (that started the project and now is working
|
|
What about doing it using BOOTSTRA.386? :-P |
|
XD well, it's an option! I don't know how many people will be fond of it but it's an idea! Let's keep the ideas going! |
|
@lite20 Hey! Are you guys just looking for ideas for the website, or are you looking for front-end web developer? If so, I'd be happy to help 😄 |
|
@AkiraLaine both ideas and developers and we'd love to have your help! (Tell your friends too hahaa). The repository for the website is https://github.com/NodeOS/nodeos.github.io I have a few ideas I will upload here in a second but if you have any, please feel free to dump them here! (Photo's, sketches, links, anything!) |
|
Put some ideas and concepts, would love to see them and maybe make them come true :) |
|
Please ignore the blank space at the bottom, here's an idea I whipped together graphically, focusing on the header. However we organize the internal content may vary.
|
|
I tried using the same colors as the logo, but we could easily swap colors for something nicer. |
|
The nav links are also just template. We'd probably want one for the blog too (and rss?) |
|
Thanks to the nature of NodeOS's logo, it's easy to convert it to any color. So, the header: This would be easy to do unless you want hexagons to be randomly generated. |
I think making a tileable SVG version of the hexagons is probably the best way to go, that way it stays responsive. The table is one way of doing it. We could also pull in bootstrap and use it's rows and columns so that it's responsive. I was however hoping we could find an even nicer way to present the details about NodeOS, maybe in creating a carousel or something of sorts? I never did show the footer in the prototype image, but if we were to make a footer we could simply create a vertically flipped version of the headers background. In the footer we would include the "subscribe for email" and a link to our social media (twitter, and gitter if that counts) from the original site. |
|
Will give it a shot tonight/tomorrow. Where should I put results? |
|
go ahead and fork the site repo and place your files in a folder with your username. I'll create the SVG header image as I already have it, and I'll paste it somewhere for you to grab. If you can, you can create one too, but you don't have to spend too much time on it. |
|
https://github.com/iDentity1337/nodeos.github.io I'll put stuff there under a specific folder |
|
@lite20 Hey! I'm starting to re-do the website (want to experiment with some stuff). I'm using Bulma, a really cool CSS Framework (changes from using Bootstrap all the time :P ). If you have any graphics or things that you want implemented in the website - could you include them somewhere? https://github.com/AkiraLaine/nodeos.github.io (AkiraLaine folder) |
|
@lite20 Here's a quick mockup of what the home page could look like? |
|
Wow thats looks really nice keep up level |
|
@AkiraLaine excellent! I love the clean matte style. Is it responsive? There's a lot of blank white space that I'll play with to see if I can get a good back scene. |
|
@AkiraLaine nice. Is Bulma a good framework to work with? |
|
@AkiraLaine I've uploaded the hex svg to my fork here. I like what you did with the info on the side. I'm curious of swapping out the computer screen section with a carousel for graphic representation's of the blog posts. we could even make the computer screen the carousel... :P |
|
@lite20 now i can work on mine, thanks for svg :P |
|
@iDentity1337 they have a nice website which displays it to be a lot like bootstrap, but smaller giving only essentials for organizing a page (things like columns and such). It also doesn't use JS from the look of things. It's pleasingly smaller than bootstrap at only 98 kb compared to bootstraps 121 neither are very large. TLDR; it looks good!
Haha yeah no problem! Excited to see what you create! |
|
Which is better, 1st or second? 1st image has a line in the middle of hexes since it's 2 svg's with 2nd one being flipped, while the 2nd image is one svg but it's big as mosque. |
|
I like the first a bit more. In the second he header seems rather oversized. |
I agree, not only seems to be very advanced and almost ready for release, but also Jekyll is somewhat easy to use (it's just markdown). As I said before, problem is to find where's the current location of the update and ask the contributor to do a pull-request to review them. Maybe @AkiraLaine, @lite20, @iDentity1337 & @joshgarde can help here? So far, seems the current status is available at NodeOS website v2 branch according to project network, being joshgarde fork the most advanced with support for the CiBlog, so I think it would be a good idea to show the changes somewhere for trial and discussion, or maybe directly just publish them on the master branch and do the changes in production, how do you see it? |
|
By the way, there are some minor pending branches of @lite20, @rakannimer and @PhillippBosch, maybe you would like to review them too... |
|
Ok, I've downloaded the @joshgarde v2 branch, merged it with master in a custom repo, and published it with Github Pages for testing purposses and discussion at https://piranna.github.io/nodeos.github.io/. Honestly, looks really nice, I really love and I'm very proud of the work you have done toguether :-) Ok, let's start with the discussion. I've seen some minor flaws and things that we could move forward:
|
|
Just pushed my v2 branch to the main v2 branch along with my "bi-monthly (sorry, not dead, just really bad at time management) update" - It adds docs Answering the issues in order:
|
Don't worry, we are lately everybody busy here... :-/
The link doesn't show on the main page. Also we need to decide if we want them centered at top or at the right side. I find them nicer center at top.
Maybe it's copypaste. I vote to remove it if we don't have plans to use it.
Download button doesn't work for me, and blog has some minor absolute path issues. I have just updated the test site with the new content. |
|
I have the site running on my own repo on GitHub Pages for testing with absolute paths - The download button with releases is broken, but everything else seems to work. |
|
The release downloads work on my box, but I'm not really sure why it's not working on GitHub Pages. It might be that our testing sites don't belong to the same owner as the NodeOS releases - some kind of security feature? It might work when it's published on the official site |
I don't think so, the releases link is pointing to the website project itself instead of NodeOS repo, we'll need to put full paths here. |
Hm. I wonder why it's not working. I'm using the official github-metadata Jekyll plugin to fetch the latest release. I just pushed some new stuff to the v2 branch.
|
|
Live test: https://joshgarde.github.io/ |
|
@joshgarde looks gorgeous! Y'all did a wonderful job. I guess I pitched in a little but you guys shouldered a lot more than I did.
Huh. Well that's my vector so I guess I ought to take a look at it. I'll inspect the file Tuesday evening. If I don't reply, I couldn't fix it fast enough. (I'm out of town for the days that follow until Saturday). |
I've already patched the SVG in the latest commit, but you're welcome to tidy it up if you want |
I'm with @lite20, looks really nice :-) But the "latest release" button is still failling, it just reload the page... :-/ Why instead of navigate with Javascript don't use just a URL? The same for the releases link, it works but it goes to the website repo releases instead of NodeOS ones...
I was going to say that :-P Yeah, now it doesn't have problems, and in fact it scale horizontally :-) |
The site doesn't use any Javascript. github-metadata is a Jekyll plugin which is supported on Github Pages. It can fetch latest release links on repos so that a manual site update isn't needed. It works fine on my local Jekyll install which makes me wonder why it fails on GitPages. If it doesn't work when I push to the master, I'll replace it with some hardlinks. I need to still fix the footer along with finalizing ci-blog before pushing to master. |
Check it yourself on your published site... Maybe is it needed to be configured something more? I now Github Pages support some plugins...
Cool, keep us informed :-) |
|
Maybe this can be useful: https://help.github.com/articles/repository-metadata-on-github-pages/ |
|
I have not read the docs, but since the releases link works but the latest
one not, maybe the plugin by default use the current project repo? Maybe
it's needed to config it in other place...
El 27/3/2017 3:40 PM, "joshgarde" <notifications@github.com> escribió:
… I don't think so, the releases link is pointing to the website project
itself instead of NodeOS repo, we'll need to put full paths here.
Hm. I wonder why it's not working. I'm using the official github-metadata
Jekyll plugin to fetch the latest release.
I just pushed some new stuff to the v2 branch.
- I've redone the implementation of the hexagons to use a div with
background css
- Removed whitespace on svg
- Footer redesigned
- Some file cleanup which fixes the homepage bug
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#261 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAgfvm_NK5eO4CASEse8CEoy4iM-SbsAks5rp14DgaJpZM4I-daK>
.
|
It's exactly that, except there's no config to set the repo to use in production. So, I've just hardlinked the download button and release button. ci-blog's been moved to it's own repo so it's separate from the website. |
|
ci-blog's been moved to it's own repo so it's separate from the website.
Totally makes sense :-) Where can we run it? We'll need to give it
permissions to commit on the repo to upload the posts too... And now that I
think it, maybe we can use Zappier or IFTTT for that task, since it's just
an issue -> commit automation... hum...
|
Generating the posts and committing them require a bit more than what Zappier or IFTTT can do on the free plans. The script can be run on most CI services as long as they can also securely handle SSH private keys for git. |
I haven't used them too much, so can't opiniate, just only used Zappier for the NodeOS blog RSS.
Yeah, I'm using SemaphoreCI + buho to do NodeOS nightly checks, it's a bit like use a cannon to kill a mosquitoe but we could set it for the website repo... |
|
By the way, we should re-enable the RSS local system as it was being done in the past and deprecate usage of Zappier. If everybody here agrees, we could publish the website as is adding the latests blog posts by hand until ci-blog is up and running, and later work on both projects separately. How do you see it? |
Jekyll handles RSS generation automagically by default.
NodeOS/nodeos.github.io#23 |
Well, not exactly automagically - but it's already enabled though jekyll-feed. I just pushed one last commit to v2 which adds a RSS feed link to the header. The site's pretty much ready to be published as is while ci-blog is being worked on. |
|
If no one has any objections, I'll go ahead and merge the v2 branch with the master in a few hours. |
It's you or me... :-) Could you be able to write a (small) issue blog post about the website update and update the published blog posts after that? |
|
So the bad is already done... we have new web!!! :-P Honestly it's really gorgeous, I'm really proud of your work guys :-) I'm going to write a new post about the announcement and try to upload it with Yay! :-P |
and others
Hi! Are you a front-end web developer? Now is your chance for you and your buddies to contribute to NodeOS (without having to decipher underlying technology in the build process; double win!)
We're redesigning our website and would love to have the talent's of all the developers combined! The first step, of course, would be to design a new page so let's use this thread and create a new idea. You may propose:
Looking forward to getting this going with you all! Tell all your friends!
The text was updated successfully, but these errors were encountered: