Help make the site mobile friendly

[SeiferTim]

I really would like to make this site look good and work on mobile but I do not know how to do that

Thankfully, all of the demos work as html5
But the layout of the site does not.

If anyone knows how to take what we have now and make it functional for small screens please help!

[Geokureli]

This is a continuation of #1, So I'll just link that here

[Geokureli]

I checked a few snippets and while I do think we can make some more improvements I think it looks great on mobile, right now.

• The category list could be collapsible
• The "Powered by Haxeflixel" image is hanging off the right side
• There's a weird iframe for the patreon button that looks screwed up, this is likely whats causing the previous issue

[Geokureli]

@ninjamuffin99, regarding:

There's a weird iframe for the patreon button that looks screwed up, this is likely whats causing the previous issue

I notice snippets is the only page with this issue, the others either haxe a twitter link or a different patreon link:

is there a way to unify these footers? While we're on the subject of unification, is there a way to make the snippets header match, too?

[ninjamuffin99]

hmmm in the same way that i ported the main site, i actually wanted to port the snippets.haxeflixel.com to be using the same 11ty static site generation as the main site!

it should be an easier process than the full HF site docpad -> 11ty conversion.

Although I suppose question now is, how to go about having the snippets separated out from website layout stuff.

We could have this repo be the CONTENT repo. Something that simply has INFORMATION. The markdown files for each snippet attached to it, along with code for each of them. And then the haxeflixel.com repo will get it on the fly (same way it gets the flixel-docs repo) and build from there

[Geokureli]

We could have this repo be the CONTENT repo. Something that simply has INFORMATION. The markdown files for each snippet attached to it, along with code for each of them. And then the haxeflixel.com repo will get it on the fly (same way it gets the flixel-docs repo) and build from there

this makes sense to me, would it also make sense that when changes are made to master, here it triggers haxeflixel.com to redeploy?

Also, I broke flixel CI, with my latest snippet #41, CI had no issues in that PR. We should probably change this CI to catch errors like that