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

Refresh the Website! #261

Closed
lite20 opened this Issue Jun 26, 2016 · 124 comments

Comments

@lite20
Member

lite20 commented Jun 26, 2016

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:

  • Theme idea's
  • Template ideas (you can sketch, or paste screenshots)
  • Web frameworks (like bootstrap) that we should (or shouldn't) use, and why

Looking forward to getting this going with you all! Tell all your friends!

@lite20 lite20 self-assigned this Jun 26, 2016

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Jun 26, 2016

Member

Put it on tweeter too ;-)

Member

piranna commented Jun 26, 2016

Put it on tweeter too ;-)

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jun 26, 2016

Member

@piranna don't you own the NodeOS twitter account? or is that @groundwater (who I never see around :( )

Member

lite20 commented Jun 26, 2016

@piranna don't you own the NodeOS twitter account? or is that @groundwater (who I never see around :( )

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Jun 26, 2016

Member

It was created by @groundwater (that started the project and now is working
on runtime.js), but I have access to it to publish oficial things. When I
was talking about say it on Twitter, I was asking about you asked gor help
there and later I could ve able to retweet ;-)
El 26/6/2016 2:52, "Lite McFish" notifications@github.com escribió:

@piranna https://github.com/piranna don't you own the NodeOS twitter
account? or is that @groundwater https://github.com/groundwater (who I
never see around :( )


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/AAgfvtYvTpJFT5YrurHXRdn5ML2LmHryks5qPc1LgaJpZM4I-daK
.

Member

piranna commented Jun 26, 2016

It was created by @groundwater (that started the project and now is working
on runtime.js), but I have access to it to publish oficial things. When I
was talking about say it on Twitter, I was asking about you asked gor help
there and later I could ve able to retweet ;-)
El 26/6/2016 2:52, "Lite McFish" notifications@github.com escribió:

@piranna https://github.com/piranna don't you own the NodeOS twitter
account? or is that @groundwater https://github.com/groundwater (who I
never see around :( )


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/AAgfvtYvTpJFT5YrurHXRdn5ML2LmHryks5qPc1LgaJpZM4I-daK
.

@piranna piranna changed the title from Refresh the Wesbite! to Refresh the Website! Jun 26, 2016

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Jun 26, 2016

Member

What about doing it using BOOTSTRA.386? :-P

Member

piranna commented Jun 26, 2016

What about doing it using BOOTSTRA.386? :-P

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jun 26, 2016

Member

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!

Member

lite20 commented Jun 26, 2016

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!

@AkiraLaine

This comment has been minimized.

Show comment
Hide comment
@AkiraLaine

AkiraLaine Jul 1, 2016

@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 commented Jul 1, 2016

@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 😄

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 1, 2016

Member

@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!)

Member

lite20 commented Jul 1, 2016

@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!)

@iDentity1337

This comment has been minimized.

Show comment
Hide comment
@iDentity1337

iDentity1337 Jul 1, 2016

Put some ideas and concepts, would love to see them and maybe make them come true :)

iDentity1337 commented Jul 1, 2016

Put some ideas and concepts, would love to see them and maybe make them come true :)

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 1, 2016

Member

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.

image

Member

lite20 commented Jul 1, 2016

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.

image

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 1, 2016

Member

I tried using the same colors as the logo, but we could easily swap colors for something nicer.

Member

lite20 commented Jul 1, 2016

I tried using the same colors as the logo, but we could easily swap colors for something nicer.

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 1, 2016

Member

The nav links are also just template. We'd probably want one for the blog too (and rss?)

Member

lite20 commented Jul 1, 2016

The nav links are also just template. We'd probably want one for the blog too (and rss?)

@iDentity1337

This comment has been minimized.

Show comment
Hide comment
@iDentity1337

iDentity1337 Jul 1, 2016

Thanks to the nature of NodeOS's logo, it's easy to convert it to any color.

So, the header:
• The easiest thing to do here is to make the navigation part in CSS and the hexagons as an image. But the option to create random hexagons in a canvas using CSS or JS is not forgotten.
Part below the header:
• Simple grid.

This would be easy to do unless you want hexagons to be randomly generated.

iDentity1337 commented Jul 1, 2016

Thanks to the nature of NodeOS's logo, it's easy to convert it to any color.

So, the header:
• The easiest thing to do here is to make the navigation part in CSS and the hexagons as an image. But the option to create random hexagons in a canvas using CSS or JS is not forgotten.
Part below the header:
• Simple grid.

This would be easy to do unless you want hexagons to be randomly generated.

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 1, 2016

Member

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.

Member

lite20 commented Jul 1, 2016

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.

@iDentity1337

This comment has been minimized.

Show comment
Hide comment
@iDentity1337

iDentity1337 Jul 2, 2016

Will give it a shot tonight/tomorrow. Where should I put results?

iDentity1337 commented Jul 2, 2016

Will give it a shot tonight/tomorrow. Where should I put results?

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 2, 2016

Member

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.

Member

lite20 commented Jul 2, 2016

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.

@iDentity1337

This comment has been minimized.

Show comment
Hide comment
@iDentity1337

iDentity1337 Jul 2, 2016

https://github.com/iDentity1337/nodeos.github.io

I'll put stuff there under a specific folder

iDentity1337 commented Jul 2, 2016

https://github.com/iDentity1337/nodeos.github.io

I'll put stuff there under a specific folder

@AkiraLaine

This comment has been minimized.

Show comment
Hide comment
@AkiraLaine

AkiraLaine Jul 2, 2016

@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)

AkiraLaine commented Jul 2, 2016

@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)

@AkiraLaine

This comment has been minimized.

Show comment
Hide comment
@AkiraLaine

AkiraLaine Jul 2, 2016

@lite20 Here's a quick mockup of what the home page could look like?
capture

AkiraLaine commented Jul 2, 2016

@lite20 Here's a quick mockup of what the home page could look like?
capture

@luii

This comment has been minimized.

Show comment
Hide comment
@luii

luii Jul 2, 2016

Member

Wow thats looks really nice keep up level

Member

luii commented Jul 2, 2016

Wow thats looks really nice keep up level

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 2, 2016

Member

@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.

Member

lite20 commented Jul 2, 2016

@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.

@iDentity1337

This comment has been minimized.

Show comment
Hide comment
@iDentity1337

iDentity1337 Jul 2, 2016

@AkiraLaine nice. Is Bulma a good framework to work with?

iDentity1337 commented Jul 2, 2016

@AkiraLaine nice. Is Bulma a good framework to work with?

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 2, 2016

Member

@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

Member

lite20 commented Jul 2, 2016

@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

@iDentity1337

This comment has been minimized.

Show comment
Hide comment
@iDentity1337

iDentity1337 Jul 2, 2016

@lite20 now i can work on mine, thanks for svg :P

iDentity1337 commented Jul 2, 2016

@lite20 now i can work on mine, thanks for svg :P

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 2, 2016

Member

@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!

@lite20 now i can work on mine, thanks for svg :P

Haha yeah no problem! Excited to see what you create!

Member

lite20 commented Jul 2, 2016

@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!

@lite20 now i can work on mine, thanks for svg :P

Haha yeah no problem! Excited to see what you create!

@iDentity1337

This comment has been minimized.

Show comment
Hide comment
@iDentity1337

iDentity1337 Jul 2, 2016

Which is better, 1st or second?
http://i.imgur.com/RLay163.png
http://i.imgur.com/WUWSmIl.png

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.

iDentity1337 commented Jul 2, 2016

Which is better, 1st or second?
http://i.imgur.com/RLay163.png
http://i.imgur.com/WUWSmIl.png

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.

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 2, 2016

Member

I like the first a bit more. In the second he header seems rather oversized.

Member

lite20 commented Jul 2, 2016

I like the first a bit more. In the second he header seems rather oversized.

@Coretool

This comment has been minimized.

Show comment
Hide comment
@Coretool

Coretool Jul 2, 2016

Member

I actually like the second one more, I find it more clear. Many small things (the first one ) start to iritate.

Member

Coretool commented Jul 2, 2016

I actually like the second one more, I find it more clear. Many small things (the first one ) start to iritate.

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 3, 2016

Member

@iDentity1337 Many people like the second one. Is it possible to create a nice in-between? Else, the second one sounds like the right one to go with (I asked a few friends opinion)

Member

lite20 commented Jul 3, 2016

@iDentity1337 Many people like the second one. Is it possible to create a nice in-between? Else, the second one sounds like the right one to go with (I asked a few friends opinion)

@iDentity1337

This comment has been minimized.

Show comment
Hide comment
@iDentity1337

iDentity1337 Jul 3, 2016

@lite20 Here's a small update, going to bed, 04:39 here.

uxituzn

EDIT: I've used jQuery for now, will probably rebuild the whole lib with what I need, since loading the complete library for few effects is stupid. And yes, that text at the right appends slowly.

iDentity1337 commented Jul 3, 2016

@lite20 Here's a small update, going to bed, 04:39 here.

uxituzn

EDIT: I've used jQuery for now, will probably rebuild the whole lib with what I need, since loading the complete library for few effects is stupid. And yes, that text at the right appends slowly.

@AkiraLaine

This comment has been minimized.

Show comment
Hide comment
@AkiraLaine

AkiraLaine Jul 3, 2016

Thanks for all the feedback :D @lite20 Here is the website with the SVG included.
capture-2

AkiraLaine commented Jul 3, 2016

Thanks for all the feedback :D @lite20 Here is the website with the SVG included.
capture-2

@AkiraLaine

This comment has been minimized.

Show comment
Hide comment
@AkiraLaine

AkiraLaine Jul 3, 2016

@lite20 Apart from the home page, what else do you need (blog, downloads page...etc?)
Also, @iDentity1337 I don't see the point of us working on 2 different versions of the website, we could just work together? @lite20 What do you think?

AkiraLaine commented Jul 3, 2016

@lite20 Apart from the home page, what else do you need (blog, downloads page...etc?)
Also, @iDentity1337 I don't see the point of us working on 2 different versions of the website, we could just work together? @lite20 What do you think?

@AkiraLaine

This comment has been minimized.

Show comment
Hide comment

AkiraLaine commented Jul 3, 2016

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Jul 3, 2016

Member

Really gorgeous designs, I'll move from here and delegate the design to you, definitely you have more skills and knowledges on frontend than me :-D

Just to note, the idea of randomly generated hexagons is really cool :-D and also, you would be interested on this tutorial to create hexagons in pure CSS ;-)

And finally for the record, the color palette of NodeOS is based on the 16 colors of the ANSI colors from the standard VGA, being used as primary ones the cold ones, and in fact the colors of the logo are blue #0000aa and cyan #00aaaa, as you can see it in the logo SVG source code. Based on Material UI guidelines, secondary colors would be black, white and grey #aaaaaa, being the resalt one brght cyan #55ffff.

Member

piranna commented Jul 3, 2016

Really gorgeous designs, I'll move from here and delegate the design to you, definitely you have more skills and knowledges on frontend than me :-D

Just to note, the idea of randomly generated hexagons is really cool :-D and also, you would be interested on this tutorial to create hexagons in pure CSS ;-)

And finally for the record, the color palette of NodeOS is based on the 16 colors of the ANSI colors from the standard VGA, being used as primary ones the cold ones, and in fact the colors of the logo are blue #0000aa and cyan #00aaaa, as you can see it in the logo SVG source code. Based on Material UI guidelines, secondary colors would be black, white and grey #aaaaaa, being the resalt one brght cyan #55ffff.

@iDentity1337

This comment has been minimized.

Show comment
Hide comment
@iDentity1337

iDentity1337 Jul 3, 2016

Good morning :DD

Well, I just finished a good part of my web, here's a screenshot: http://i.imgur.com/fkXtLiQ.png ..
@AkiraLaine I hate frameworks, but why not 👍

iDentity1337 commented Jul 3, 2016

Good morning :DD

Well, I just finished a good part of my web, here's a screenshot: http://i.imgur.com/fkXtLiQ.png ..
@AkiraLaine I hate frameworks, but why not 👍

@iDentity1337

This comment has been minimized.

Show comment
Hide comment
@iDentity1337

iDentity1337 Jul 3, 2016

9xiaonu

Mine is done, but not responsive like @AkiraLaine 's is :/

EDIT: I've pushed the whole website to the fork under folder iDentity1337:
https://github.com/iDentity1337/nodeos.github.io
Still has some stuff to be done, including responsivness.

iDentity1337 commented Jul 3, 2016

9xiaonu

Mine is done, but not responsive like @AkiraLaine 's is :/

EDIT: I've pushed the whole website to the fork under folder iDentity1337:
https://github.com/iDentity1337/nodeos.github.io
Still has some stuff to be done, including responsivness.

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jul 3, 2016

Member

@AkiraLaine @iDentity1337

I don't see the point of us working on 2 different versions of the website, we could just work together? @lite20 What do you think?

Yes I agree. Both of you have created excellent sites, so let's discuss how we want to merge them.

Before I begin I should mention that you've both done excellent work! To merge the two, I suggest that we build off @AkiraLaine's source simply so we don't have to go through the process of re-implementing things with Bulma. I've noticed that @iDentity1337 has a nice space at the top of his version matching the color of the base hexagons. This ensures the white icons are always visible. I suggest you port this to the final version.

For the content of the page, I suggest we go with @AkiraLaine's version as it is already responsive. For the footer... they're both really nice, I can't actually decide on one. I likehow @iDentity1337 made the email bar dark so that it didn't scream for attention too much, so that's something to keep in mind but ultimately I leave that to you guys to decide 😛

Excellent work guys! I'm working on randomly generating the Hexagons to a canvas, and on designing the carousel; good work!

Member

lite20 commented Jul 3, 2016

@AkiraLaine @iDentity1337

I don't see the point of us working on 2 different versions of the website, we could just work together? @lite20 What do you think?

Yes I agree. Both of you have created excellent sites, so let's discuss how we want to merge them.

Before I begin I should mention that you've both done excellent work! To merge the two, I suggest that we build off @AkiraLaine's source simply so we don't have to go through the process of re-implementing things with Bulma. I've noticed that @iDentity1337 has a nice space at the top of his version matching the color of the base hexagons. This ensures the white icons are always visible. I suggest you port this to the final version.

For the content of the page, I suggest we go with @AkiraLaine's version as it is already responsive. For the footer... they're both really nice, I can't actually decide on one. I likehow @iDentity1337 made the email bar dark so that it didn't scream for attention too much, so that's something to keep in mind but ultimately I leave that to you guys to decide 😛

Excellent work guys! I'm working on randomly generating the Hexagons to a canvas, and on designing the carousel; good work!

@luii

This comment has been minimized.

Show comment
Hide comment
@luii

luii Feb 16, 2017

Member

unable to build because json 1.8.3 isnt compatible with 2.4
getting this error:

generator.c: In Funktion »generate_json«:
generator.c:861:25: Fehler: »rb_cFixnum« nicht deklariert (erste Benutzung in dieser Funktion)
     } else if (klass == rb_cFixnum) {
                         ^~~~~~~~~~
generator.c:861:25: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
generator.c:863:25: Fehler: »rb_cBignum« nicht deklariert (erste Benutzung in dieser Funktion)
     } else if (klass == rb_cBignum) {

@joshgarde could you compile it and upload it maybe?

Member

luii commented Feb 16, 2017

unable to build because json 1.8.3 isnt compatible with 2.4
getting this error:

generator.c: In Funktion »generate_json«:
generator.c:861:25: Fehler: »rb_cFixnum« nicht deklariert (erste Benutzung in dieser Funktion)
     } else if (klass == rb_cFixnum) {
                         ^~~~~~~~~~
generator.c:861:25: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
generator.c:863:25: Fehler: »rb_cBignum« nicht deklariert (erste Benutzung in dieser Funktion)
     } else if (klass == rb_cBignum) {

@joshgarde could you compile it and upload it maybe?

@luii

This comment has been minimized.

Show comment
Hide comment
@luii

luii Feb 17, 2017

Member

nvm i got it working with bundle, for all using jekyll with ruby 2.4.0 you need to add this line to the gemfile gem "json", github: 'flori/json', branch: "v1.8" right under source

Member

luii commented Feb 17, 2017

nvm i got it working with bundle, for all using jekyll with ruby 2.4.0 you need to add this line to the gemfile gem "json", github: 'flori/json', branch: "v1.8" right under source

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 6, 2017

Member

Hi guys, how is this going on?

Member

piranna commented Mar 6, 2017

Hi guys, how is this going on?

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 24, 2017

Member

Since I'm going to talk in the next weeks in a major national event here at Spain, I think it would be a good time to do the final works and publish an updated version of the NodeOS website, how do you see it?

Member

piranna commented Mar 24, 2017

Since I'm going to talk in the next weeks in a major national event here at Spain, I think it would be a good time to do the final works and publish an updated version of the NodeOS website, how do you see it?

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Mar 24, 2017

Member

@piranna that's definitely a good idea. From my understanding a template is being built from the pages I and the others created a while back. Unfortunately I have no idea how either of the two attempts to convert them to Jekyll pages are going.

Member

lite20 commented Mar 24, 2017

@piranna that's definitely a good idea. From my understanding a template is being built from the pages I and the others created a while back. Unfortunately I have no idea how either of the two attempts to convert them to Jekyll pages are going.

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Mar 24, 2017

Member

If no progress is made in a bit, I'll attempt to pick it up

Member

lite20 commented Mar 24, 2017

If no progress is made in a bit, I'll attempt to pick it up

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 25, 2017

Member

I don't know what's the status, since I almost have no idea of web development I step back from it, but the mockups seems they were really advanced, so maybe we have something to publish soon :-)

Member

piranna commented Mar 25, 2017

I don't know what's the status, since I almost have no idea of web development I step back from it, but the mockups seems they were really advanced, so maybe we have something to publish soon :-)

@djesmond

This comment has been minimized.

Show comment
Hide comment
@djesmond

djesmond Mar 25, 2017

Contributor

I don't have any experience with these frameworks, but if needed, I can built something temporary ( but better than current) in React.

Contributor

djesmond commented Mar 25, 2017

I don't have any experience with these frameworks, but if needed, I can built something temporary ( but better than current) in React.

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 26, 2017

Member
Member

piranna commented Mar 26, 2017

@djesmond

This comment has been minimized.

Show comment
Hide comment
@djesmond

djesmond Mar 26, 2017

Contributor

Yes i agree, it mentioned it as a backup plan, if something had to be made quick.
The better solution is to continue with the current (this issue).

Contributor

djesmond commented Mar 26, 2017

Yes i agree, it mentioned it as a backup plan, if something had to be made quick.
The better solution is to continue with the current (this issue).

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 26, 2017

Member

The better solution is to continue with the current (this issue).

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?

Member

piranna commented Mar 26, 2017

The better solution is to continue with the current (this issue).

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?

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 26, 2017

Member

By the way, there are some minor pending branches of @lite20, @rakannimer and @PhillippBosch, maybe you would like to review them too...

Member

piranna commented Mar 26, 2017

By the way, there are some minor pending branches of @lite20, @rakannimer and @PhillippBosch, maybe you would like to review them too...

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 26, 2017

Member

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:

  • at a 1366x768 screen the bottom of the page gets missed and you need to scroll. It works correctly up to 921px width, if it's higher then the scroll bar pop-ups. Seems to be related to the hexagons at the top, that's an image set to width: 100% and so its height gets increased. Setting it to a max of 128px and the body width to 920px seems to be just enought to this don't happen anymore
  • the hexagons has some white pixels at each side
  • all the code is on the header section, we should define a body and footer too for better structure :-)
  • what's the purpose of the subscription email? We don't have a mail list... :-/
  • download and blog links doesn't work. Where should they be pointing to? The releases page and the CiBlog?
Member

piranna commented Mar 26, 2017

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:

  • at a 1366x768 screen the bottom of the page gets missed and you need to scroll. It works correctly up to 921px width, if it's higher then the scroll bar pop-ups. Seems to be related to the hexagons at the top, that's an image set to width: 100% and so its height gets increased. Setting it to a max of 128px and the body width to 920px seems to be just enought to this don't happen anymore
  • the hexagons has some white pixels at each side
  • all the code is on the header section, we should define a body and footer too for better structure :-)
  • what's the purpose of the subscription email? We don't have a mail list... :-/
  • download and blog links doesn't work. Where should they be pointing to? The releases page and the CiBlog?
@joshgarde

This comment has been minimized.

Show comment
Hide comment
@joshgarde

joshgarde Mar 26, 2017

Member

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
https://github.com/NodeOS/nodeos.github.io/tree/v2

Answering the issues in order:

  1. Sounds like a plan

  2. It's an issue with the original SVG that needs to be smoothened out in a vector editor

  3. There's already body code in the layouts folder and I didn't have anything to put in the footer

  4. I don't know - everyone else had it in their designs along with the original website

  5. They work on the latest build. Try deleting the previously generated pages or downloading the new update

Member

joshgarde commented Mar 26, 2017

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
https://github.com/NodeOS/nodeos.github.io/tree/v2

Answering the issues in order:

  1. Sounds like a plan

  2. It's an issue with the original SVG that needs to be smoothened out in a vector editor

  3. There's already body code in the layouts folder and I didn't have anything to put in the footer

  4. I don't know - everyone else had it in their designs along with the original website

  5. They work on the latest build. Try deleting the previously generated pages or downloading the new update

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 26, 2017

Member

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"

Don't worry, we are lately everybody busy here... :-/

It adds docs

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.

I don't know - everyone else had it in their designs along with the original website

Maybe it's copypaste. I vote to remove it if we don't have plans to use it.

They work on the latest build. Try deleting the previously generated pages or downloading the new update

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.

Member

piranna commented Mar 26, 2017

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"

Don't worry, we are lately everybody busy here... :-/

It adds docs

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.

I don't know - everyone else had it in their designs along with the original website

Maybe it's copypaste. I vote to remove it if we don't have plans to use it.

They work on the latest build. Try deleting the previously generated pages or downloading the new update

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.

@joshgarde

This comment has been minimized.

Show comment
Hide comment
@joshgarde

joshgarde Mar 26, 2017

Member

I have the site running on my own repo on GitHub Pages for testing with absolute paths -
https://joshgarde.github.io/

The download button with releases is broken, but everything else seems to work.

Member

joshgarde commented Mar 26, 2017

I have the site running on my own repo on GitHub Pages for testing with absolute paths -
https://joshgarde.github.io/

The download button with releases is broken, but everything else seems to work.

@joshgarde

This comment has been minimized.

Show comment
Hide comment
@joshgarde

joshgarde Mar 27, 2017

Member

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

Member

joshgarde commented Mar 27, 2017

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

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 27, 2017

Member

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.

Member

piranna commented Mar 27, 2017

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.

@joshgarde

This comment has been minimized.

Show comment
Hide comment
@joshgarde

joshgarde Mar 27, 2017

Member

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
Member

joshgarde commented Mar 27, 2017

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
@joshgarde

This comment has been minimized.

Show comment
Hide comment
Member

joshgarde commented Mar 27, 2017

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Mar 27, 2017

Member

@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.

It's an issue with the original SVG that needs to be smoothened out in a vector editor

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).

Member

lite20 commented Mar 27, 2017

@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.

It's an issue with the original SVG that needs to be smoothened out in a vector editor

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).

@joshgarde

This comment has been minimized.

Show comment
Hide comment
@joshgarde

joshgarde Mar 27, 2017

Member

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

Member

joshgarde commented Mar 27, 2017

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

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 27, 2017

Member

@joshgarde looks gorgeous! Y'all did a wonderful job

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've already patched the SVG in the latest commit, but you're welcome to tidy it up if you want

I was going to say that :-P Yeah, now it doesn't have problems, and in fact it scale horizontally :-)

Member

piranna commented Mar 27, 2017

@joshgarde looks gorgeous! Y'all did a wonderful job

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've already patched the SVG in the latest commit, but you're welcome to tidy it up if you want

I was going to say that :-P Yeah, now it doesn't have problems, and in fact it scale horizontally :-)

@joshgarde

This comment has been minimized.

Show comment
Hide comment
@joshgarde

joshgarde Mar 27, 2017

Member

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...

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.

Member

joshgarde commented Mar 27, 2017

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...

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.

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 27, 2017

Member

If it doesn't work when I push to the master, I'll replace it with some hardlinks.

Check it yourself on your published site... Maybe is it needed to be configured something more? I now Github Pages support some plugins...

I need to still fix the footer along with finalizing ci-blog before pushing to master.

Cool, keep us informed :-)

Member

piranna commented Mar 27, 2017

If it doesn't work when I push to the master, I'll replace it with some hardlinks.

Check it yourself on your published site... Maybe is it needed to be configured something more? I now Github Pages support some plugins...

I need to still fix the footer along with finalizing ci-blog before pushing to master.

Cool, keep us informed :-)

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 27, 2017

Member
Member

piranna commented Mar 27, 2017

@joshgarde

This comment has been minimized.

Show comment
Hide comment
@joshgarde

joshgarde Mar 29, 2017

Member

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...

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.

Member

joshgarde commented Mar 29, 2017

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...

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.

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 29, 2017

Member
Member

piranna commented Mar 29, 2017

@joshgarde

This comment has been minimized.

Show comment
Hide comment
@joshgarde

joshgarde Mar 29, 2017

Member

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.

Member

joshgarde commented Mar 29, 2017

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.

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 29, 2017

Member

Generating the posts and committing them require a bit more than what Zappier or IFTTT can do on the free plans

I haven't used them too much, so can't opiniate, just only used Zappier for the NodeOS blog RSS.

The script can be run on most CI services as long as they can also securely handle SSH private keys for git

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...

Member

piranna commented Mar 29, 2017

Generating the posts and committing them require a bit more than what Zappier or IFTTT can do on the free plans

I haven't used them too much, so can't opiniate, just only used Zappier for the NodeOS blog RSS.

The script can be run on most CI services as long as they can also securely handle SSH private keys for git

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...

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Mar 29, 2017

Member

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?

Member

piranna commented Mar 29, 2017

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?

@joshgarde

This comment has been minimized.

Show comment
Hide comment
@joshgarde

joshgarde Mar 29, 2017

Member

By the way, we should re-enable the RSS local system as it was being done in the past and deprecate usage of Zappier.

Jekyll handles RSS generation automagically by default.

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?

NodeOS/nodeos.github.io#23
Ready when you are.

Member

joshgarde commented Mar 29, 2017

By the way, we should re-enable the RSS local system as it was being done in the past and deprecate usage of Zappier.

Jekyll handles RSS generation automagically by default.

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?

NodeOS/nodeos.github.io#23
Ready when you are.

@joshgarde

This comment has been minimized.

Show comment
Hide comment
@joshgarde

joshgarde Mar 29, 2017

Member

Jekyll handles RSS generation automagically by default.

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.

demo: https://joshgarde.github.io

Member

joshgarde commented Mar 29, 2017

Jekyll handles RSS generation automagically by default.

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.

demo: https://joshgarde.github.io

@joshgarde

This comment has been minimized.

Show comment
Hide comment
@joshgarde

joshgarde Apr 2, 2017

Member

If no one has any objections, I'll go ahead and merge the v2 branch with the master in a few hours.

Member

joshgarde commented Apr 2, 2017

If no one has any objections, I'll go ahead and merge the v2 branch with the master in a few hours.

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Apr 2, 2017

Member

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?

Member

piranna commented Apr 2, 2017

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?

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Apr 2, 2017

Member

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 ci-blog. There are some minor issues that we could keep fixing on the way, so I think we can officially close this issue :-)

Yay! :-P

Member

piranna commented Apr 2, 2017

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 ci-blog. There are some minor issues that we could keep fixing on the way, so I think we can officially close this issue :-)

Yay! :-P

@piranna piranna closed this Apr 2, 2017

@piranna piranna removed the discussion label Apr 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment