-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
I, like @Ad5001, propose that we do everything from scratch as frameworks will quickly go outdated. |
@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. |
I did say we could use Bulma for styling. |
Whooops with the Bulma thing Also: We don't want people to rely on other sites for our plugins. Auto compilation is helpful. |
That's the reason I don't code with React. |
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. |
I tired React and didn’t even finish the tutorial. |
@HimbeersaftLP I have a $10/month DigitalOcean droplet. And yes, it’s on the new pricing, meaning 2GB of RAM. |
@HimbeersaftLP It would be hosted on glitch. If we were to proceed with that idea, each plugin would have:
|
@HimbeersaftLP The “backend” would be located on Heroku or Glitch. Yes, they are free but they have a good reputation. |
bootstrap |
We are talking about backend. |
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) |
glitch does have |
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 |
And we’re talking about backend. |
This is my timeline as someone who has been working with this for while.
|
why not php |
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. |
That language honestly has too many security concerns and is not a modern language, Node.js and Go are modern. |
@Dog2puppy Agreed. We can build it as a static site, that is a great idea. |
@nathfreder
|
blah blah php is awesome |
@nathfreder What’s Invision App? |
no wait! we can use Java!!!!!!11!1!1 |
java -jar boxofdevs.jar |
Or, we could just use the built in Jekyll templating. |
@Dog2puppy That is not needed and needs Ruby to even test. @TheRoyalBlock good point |
@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 |
@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. |
@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. |
@TheDragonRing Can you invite me as a contributor to the boxofdevs.github.io repo? |
@nathfreder You don't need to use a GitHub theme. You can use a GitHub theme. Take for example Dog2puppy/dog2puppy.github.io |
@Dog2puppy We want to design the site for ourself, not use a crummy theme. |
@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 |
Yet, my own site doesn't use a theme. (Bulma is just styling) |
@Dog2puppy I do not like Bulma, we are design the website as a group not from a library. BTW your site is offline. |
Oh, I was using dog2puppy.tk
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Dog2puppy <notifications@github.com>
Sent: Tuesday, February 6, 2018 7:02:10 PM
To: BoxOfDevs/boxofdevs.github.io
Cc: Nathaniel Fredericks; Mention
Subject: Re: [BoxOfDevs/boxofdevs.github.io] Website Redesign (#26)
https://dog2puppy.github.io/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#26 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ahsw6tpWKyBNNsnFuMIIg_eVRzBgR0-kks5tSNnygaJpZM4R7pua>.
|
NAH NAH NAH OURS DOESn"T HAVE A SHADOW |
AND OURS IS A PNG |
Sh |
@TheRoyalBlock Do you have any JS experience? |
@TheDragonRing I were talking about frontend but they made me confused |
@SuperOP535 yeah dw. Everybody was a bit confused. |
@BoxOfDevs/members @SuperOP535 @nathfreder change of plans. So that we can see the new site @ new.boxofdevs.com it will be in this repo. |
@TheDragonRing Alright, now can someone please invite me to the repo. |
@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. |
Alright. Sound good.
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: TheDragonRing <notifications@github.com>
Sent: Wednesday, February 7, 2018 7:52:10 AM
To: BoxOfDevs/boxofdevs.github.io
Cc: Nathaniel Fredericks; Mention
Subject: Re: [BoxOfDevs/boxofdevs.github.io] Website Redesign (#26)
@nathfreder<https://github.com/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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#26 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ahsw6rNma5otO9195Mt8BHYU3yrcQ3dgks5tSY5qgaJpZM4R7pua>.
|
Closing this because we have a new repo. |
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
ToDo
The text was updated successfully, but these errors were encountered: