search

HaxeFlixel / haxeflixel.com

haxeflixel.com docpad/11ty source
https://haxeflixel.com/
70 stars 102 forks source link

11ty + tailwind website overhaul / rewrite #219

Closed ninjamuffin99 closed 7 months ago

ninjamuffin99 commented 10 months ago

going off of #182 I have taken the liberty in beginning a SITE OVERHAUL / REDESIGN

this PR will start out as a DRAFT to keep it around here on this haxeflixel repo

https://www.11ty.dev/ https://tailwindcss.com/

I have set up the barebones stuff and got some of the docpad stuff out of the way, for other people to work on it, all they should need is npm and running npm install should let them play around in code!

@01010111 I've been chattin with mr will blanton about web site DESIGN things, see where his mind is at with things (check out his cool personal sites I think they look nice... lol)

progress gifs as of writing

img

img

img

you can load the current (as of writing) version of the site here: https://ninjamuffin99.github.io/haxeflixel.com

open to contributions and help of course!!!

Geokureli commented 9 months ago

I know very little about web dev, but I just wanted to list out some of my priorities. I would like a site that

  1. Easy for non-webdev savvy people to setup and test locally
  2. Easy for non-webdev savvy people to change or add content
  3. isn't dependent on something that won't be maintained in the coming years

We're in this situation because the people who knew the old system moved on to other things, and the tech behind it is now shaky and cumbersome, what is your future forecast of 11ty and tailwind?

ninjamuffin99 commented 9 months ago

For points 1 and 2, I've found it veeeery easy and seamless to setup and test locally. It's a matter of just npm install then running npm run dev to build/serve it locally. Then to add content, the format is pretty standard for static site generators, in fact, you can even use a few different static site templating languages. However, most things can be easily created / added to with some basic markdown files for content that we want to be easy to add/change. I got stuff like the HaxeFlixel blog in-progress, and I didn't touch any of the old markdown files (other than changing the front matter from ``` to ---)

In terms of my future forecast, I think Tailwind for sure is going to be around for a damn while, and as I've been going through remaking things, I've found it super ergonomic! And is becoming more and more industry standard for CSS (if it isn't already)

For the future of 11ty, we will LOOK TO THE PAST! Where development team pride themselves in 11ty being VERY stable. "At time of writing, we’ve shipped 56 releases dating back December 2017 and only two of those releases have had Eleventy-specific breaking changes.". So with that being said, I would place bets on being able to maintain 11ty updates to a new Haxeflixel.com with very little effort going forward.

In terms of people moving onto other things, I personally have found it very easy to get setup, and learn my way around things, coming from someone who has made only one other static site generated website. Once things ARE all proper setup, I can imagine it being even easier for people to learn their way around things, as the heavy lifting of setup/config is all done more or less as well.