Skip to content
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

Website Redesign #26

Closed
5 tasks
AvgZing opened this issue Feb 6, 2018 · 93 comments
Closed
5 tasks

Website Redesign #26

AvgZing opened this issue Feb 6, 2018 · 93 comments

Comments

@AvgZing
Copy link
Member

AvgZing commented Feb 6, 2018

In this message (Staff and contributors are free to edit this todo) we have: Todo list, and current plans.

NOTE: DO NOT DISCUSS THE WEBSITE REDESIGN ON DISCORD! KEEP DISCUSSIONS HERE!

Plans

  • Host a frontend site with pages similar to our current one on github pages
  • Host a backend projects page, which will ideally have automatic phar building for each commit, along with a stable releases section and possibly even an auto-updater
  • Possible: Vue, Google Polymer, or something built from scratch (probably using jQuery)
  • Possible: Bulma for styling
  • Poll for frontend and backend ---- Backend: http://www.strawpoll.me/15014604 AND Frontend: http://www.strawpoll.me/15014615
  • Start from scratch to avoid having outdated frameworks
  • This is a redesign where all staff and active discord members have a say
  • Add more ad spaces

ToDo

  • Decide on a theme
  • Decide on a framework
  • Decide on pages and their content
  • Code pages
  • Release the newly redesigned website
@AvgZing
Copy link
Member Author

AvgZing commented Feb 6, 2018

I, like @Ad5001, propose that we do everything from scratch as frameworks will quickly go outdated.

@catgirlinspace
Copy link
Contributor

I propose we use Vue for a JS Framework, and Bulma for styling.

@ghost
Copy link

ghost commented Feb 6, 2018

@TheRoyalBlock Uhh, React has been around since 2014 and is being actively maintained by Facebook. Why do we need auto-updaters and phar packagers, we have PocketMine Tools and DevTools for that. Just for reference “Bulma” is not a framework, it is a style library.

@catgirlinspace
Copy link
Contributor

catgirlinspace commented Feb 6, 2018

Bulma for styling.

I did say we could use Bulma for styling.

@AvgZing
Copy link
Member Author

AvgZing commented Feb 6, 2018

Whooops with the Bulma thing

Also: We don't want people to rely on other sites for our plugins. Auto compilation is helpful.

@Ad5001
Copy link
Member

Ad5001 commented Feb 6, 2018

maintained by Facebook

That's the reason I don't code with React.

@HimbeersaftLP
Copy link
Member

Considering that our projects "backend" would most likely be on some free host, I'd expect that to be less reliable than Poggit and GitHub.

@catgirlinspace
Copy link
Contributor

I tired React and didn’t even finish the tutorial.

@catgirlinspace
Copy link
Contributor

@HimbeersaftLP I have a $10/month DigitalOcean droplet. And yes, it’s on the new pricing, meaning 2GB of RAM.

@AvgZing
Copy link
Member Author

AvgZing commented Feb 6, 2018

@HimbeersaftLP It would be hosted on glitch. If we were to proceed with that idea, each plugin would have:

  • Auto updater
  • Auto compiler
  • Stable releases section (Manually mark a compiled build as stable)
  • Description

@ghost
Copy link

ghost commented Feb 6, 2018

@HimbeersaftLP The “backend” would be located on Heroku or Glitch. Yes, they are free but they have a good reputation.

@SuperOP535
Copy link

bootstrap

@ghost
Copy link

ghost commented Feb 6, 2018

We are talking about backend.

@SuperOP535
Copy link

And I'm doing about frontend
image

@HimbeersaftLP
Copy link
Member

Poggit does have a good reputation too, when it doesn't come to the design and we don't need to reinvent the wheel for that (which, as by my experience, usually doesn't work out very well)

@SuperOP535
Copy link

glitch does have phar pre-installed

@AvgZing
Copy link
Member Author

AvgZing commented Feb 6, 2018

Poggit, however, doesn't have an auto-updater. We know that BOD is not good at maintaining and updated plugins, an auto updater is basically a necessity

@catgirlinspace
Copy link
Contributor

catgirlinspace commented Feb 6, 2018

And we’re talking about backend.
insert image

@SuperOP535
Copy link

image

@ghost
Copy link

ghost commented Feb 6, 2018

This is my timeline as someone who has been working with this for while.
@TheRoyalBlock @Dog2puppy

  • Select a backend language. (Node.js or Go)
  • Select a fronted framework. (Vue or Handlebars)
  • Work on the wireframe using invisionapp.com.
  • Start a Glitch project and invite everyone.
  • Begin development of the frontend.
  • Begin development of the backend.
  • Release Website

@SuperOP535
Copy link

why not php

@catgirlinspace
Copy link
Contributor

light bulb appears 💡

We could create an API server using Node.js and Express. For front end, we make a SPA (single page web app) using Vue. In Vue, we would fetch data from the API and render it! And also, Vue supports GitHub Pages.

@ghost
Copy link

ghost commented Feb 6, 2018

That language honestly has too many security concerns and is not a modern language, Node.js and Go are modern.

@ghost
Copy link

ghost commented Feb 6, 2018

@Dog2puppy Agreed. We can build it as a static site, that is a great idea.

@AvgZing
Copy link
Member Author

AvgZing commented Feb 6, 2018

@nathfreder

  1. We will not have a backend page, it's been decided by staff on discord
  2. Frontend and wireframe will likely be coded from scratch to avoid going outdated
  3. No usage of glitch, everything will be on github pages

@SuperOP535
Copy link

SuperOP535 commented Feb 6, 2018

blah blah php is awesome

@catgirlinspace
Copy link
Contributor

@nathfreder What’s Invision App?

@SuperOP535
Copy link

no wait! we can use Java!!!!!!11!1!1

@SuperOP535
Copy link

java -jar boxofdevs.jar

@catgirlinspace
Copy link
Contributor

Or, we could just use the built in Jekyll templating.

@ghost
Copy link

ghost commented Feb 6, 2018

@Dog2puppy That is not needed and needs Ruby to even test. @TheRoyalBlock good point

@dragonwocky
Copy link
Member

dragonwocky commented Feb 6, 2018

@BoxOfDevs/members @nathfreder @SuperOP535 let me clear this up.

The entire idea of having a backend in the first place was based on a misunderstanding, an old post that most people had forgotten about / were ignoring. We aren't actually having a blog (there's nothing to post on one).

Then it turned into the idea that we might need to auto-compile projects, but as I pointed out earlier - we have nothing to auto-compile, and even if we did, I'm not sure users would actually want to use not-yet-functional half-coded versions of updates. For plugins, we can manually use Poggit and GitHub releases, and for other projects either they won't need compiling (frontend web projects), or they'll be a kind of project we haven't yet considered, and so we'll deal with that when we come to it.

Now it seems mainly just that some people want a backend (for what reason I'm no longer sure), and it's turned into an argument with seemingly no solution.

Let's just get the frontend done first, as @@nathfreder said, then we will hopefully realise that we don't need a backend.

Oh, and BTW? What's all this about boxofdevs.com going? At the moment, since the domain hasn't expired, we might as well use it. When it does expire, I may renew it or we may just stick with boxofdevs.github.io - either way, I'm not sure what that has to do with this...

P.S. Yes, as @TheRoyalBlock said, I made a branch called total-revamp. I'm working on a commit that's almost finished, then once it's done (adds a few basics and things like jQuery + FontAwesome), we can start planning what we want the site to end up looking like.

Edit: That commit has now been pushed. At the moment, the jQuery and FontAwesome files are there ready to use, but later on they may be changed to CDNs. See the commit here: 089c0e0

@catgirlinspace
Copy link
Contributor

catgirlinspace commented Feb 6, 2018

@nathfreder GitHub Pages supports Jekyll built in and really Ruby knowledge isn’t needed. The reason you would use it on GitHub Pages is for things like changing a Navbar. Do you want to change all 10 or 100 or even more pages just to update the Navbar, when you could simply change 1 file.

@ghost
Copy link

ghost commented Feb 6, 2018

@Dog2puppy That is if you use a theme, if you want to build your on Jenkyll site you need Ruby Gems to compile it, then when you upload to GitHub it will be built again by GitHub.

@ghost
Copy link

ghost commented Feb 6, 2018

@TheDragonRing Can you invite me as a contributor to the boxofdevs.github.io repo?

@catgirlinspace
Copy link
Contributor

catgirlinspace commented Feb 6, 2018

@nathfreder You don't need to use a GitHub theme. You can use a GitHub theme. Take for example Dog2puppy/dog2puppy.github.io

@ghost
Copy link

ghost commented Feb 6, 2018

@Dog2puppy We want to design the site for ourself, not use a crummy theme.

@ghost
Copy link

ghost commented Feb 6, 2018

@TheDragonRing We can re-design the website, then I will make a logo in Adobe AI that is not stolen https://dartstorage.co/product/large-box

@catgirlinspace
Copy link
Contributor

Yet, my own site doesn't use a theme. (Bulma is just styling)

@ghost
Copy link

ghost commented Feb 6, 2018

@Dog2puppy I do not like Bulma, we are design the website as a group not from a library. BTW your site is offline.

@catgirlinspace
Copy link
Contributor

@ghost
Copy link

ghost commented Feb 6, 2018 via email

@catgirlinspace
Copy link
Contributor

catgirlinspace commented Feb 6, 2018

Our box is stolen? Who is responsible for this? @BoxOfDevs/members

MY BOX!

THIS IS MY BOX!!!!!

@AvgZing
Copy link
Member Author

AvgZing commented Feb 6, 2018

NAH NAH NAH OURS DOESn"T HAVE A SHADOW

@AvgZing
Copy link
Member Author

AvgZing commented Feb 6, 2018

AND OURS IS A PNG

@catgirlinspace
Copy link
Contributor

MY BOX!

THIS IS MY BOX!!!!!

@catgirlinspace
Copy link
Contributor

image
I SEE TONS OF SHADOWS!!!

@AvgZing
Copy link
Member Author

AvgZing commented Feb 6, 2018

Sh

@catgirlinspace
Copy link
Contributor

@TheRoyalBlock Do you have any JS experience?

@SuperOP535
Copy link

@TheDragonRing I were talking about frontend but they made me confused

@dragonwocky
Copy link
Member

@SuperOP535 yeah dw. Everybody was a bit confused.
@Dog2puppy erhm... the image was originally off a Google search I think... we didn't discover it was stolen until recently-ish... and the one with the shadow is the old version...

@dragonwocky
Copy link
Member

dragonwocky commented Feb 7, 2018

@BoxOfDevs/members @SuperOP535 @nathfreder change of plans. So that we can see the new site @ new.boxofdevs.com it will be in this repo.

@catgirlinspace
Copy link
Contributor

And if you want to see what I'm doing using Jekyll, you can see it here and the finished design here.

@ghost
Copy link

ghost commented Feb 7, 2018

@TheDragonRing Alright, now can someone please invite me to the repo.

@dragonwocky
Copy link
Member

@nathfreder I'll add you, but since multiple people will be working on it at once please don't commit directly, use pull requests - even the BOD members are using them.

@ghost
Copy link

ghost commented Feb 7, 2018 via email

@catgirlinspace
Copy link
Contributor

Closing this because we have a new repo.

@BoxOfDevs BoxOfDevs locked as resolved and limited conversation to collaborators Feb 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants