Delivering WordPress in 7kb

Re:Delivering WordPress in 7kb by social_quotient on Thursday July 12, 2018 @07:52AM (#17513650)

This is a great reminder of what can be done by just “rethinking everything” and saying why do I NEED that plugin, lib, script, font lib etc. one thing not immediately obvious to me was that the responsive menu goes to a new page https://sustywp.com/menu/ and because the site is so fast it actually doesn’t feel like a page load. I haven’t really thought about this but hamburger menus get so complex these days it might just be easier to load a minimal page.

Something about this menu approach feels so clever but wrong at the same time.

[ Parent | on HN ]

Re:Delivering WordPress in 7kb by carrier_lost on Thursday July 12, 2018 @10:51AM (#17515179)

The menu on this site is essentially what a website's index page used to be, back in the early days of the WWW. It was, generally, a listing of a website's contents, modeled after the default directory listing that a web server produces.

So this menu felt very normal to me, but it may be off-putting to newer users of the web who are used to contemporary conventions such as slide-out hamburgers (not to be confused with slider hamburgers :-) ).

[ Parent | on HN ]

Re:Delivering WordPress in 7kb by jazoom on Thursday July 12, 2018 @08:07AM (#17513701)

I just opened and closed it a few times to try it out. Then I pressed the back button several times to get back here, cycling the menu open and closed again.

I'm gonna go with "it's a bad idea".

[ Parent | on HN ]

Re:Delivering WordPress in 7kb by juliangoldsmith on Thursday July 12, 2018 @11:51AM (#17515767)

I don't think opening and closing the menu is a realistic test.

Generally when a user opens the menu they're trying to go to a different page.

[ Parent | on HN ]

Re:Delivering WordPress in 7kb by dosy on Thursday July 12, 2018 @08:31AM (#17513787)

That's a bug not a design flaw. You could fix that with a tiny bit more JS checking history entries for repetition.

[ Parent | on HN ]

Re:Delivering WordPress in 7kb by Jarwain on Thursday July 12, 2018 @08:32AM (#17513795)

If one really wanted to, couldn't they eliminate menu access from the user's history?

[ Parent | on HN ]

Re:Delivering WordPress in 7kb by jazoom on Thursday July 12, 2018 @08:50AM (#17513879)

Yes. You can use replace() instead of push().

But there are other issues like bookmarking or sharing the page with the menu open. People won't expect the result.

It's really not difficult to create an on-page menu so this seems more trouble than it's worth.

[ Parent | on HN ]

Re:Delivering WordPress in 7kb by thesumofall on Thursday July 12, 2018 @11:29AM (#17515552)

But would people really try to share / bookmark a page that at that very moment doesn't show the content they want to share?

I think it is a beautiful, simple solution that just works (and also did work perfectly in the past when we didn't have JS)

[ Parent | on HN ]

Re:Delivering WordPress in 7kb by jjeaff on Friday July 13, 2018 @02:27AM (#17520902)

Yes. If you have ever worked on a site with lots of users, you will find that if there is a way to break something, someone will absolutely do that thing. It might not be super often, but it will definitely happen.

[ Parent | on HN ]