Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Free static site generator for small restaurants and cafes

lite.localcafe.org

Post reply on HN
Print view View original

71–80 of 110 posts

Re: Free static site generator for small restaurants and cafes

#71

Post by ok123456 »

vector_spaces wrote: post #59
ok123456 wrote: post #31

Earlier quoted context omitted.

If the restaurant doesn't have anything besides a menu, /index.pdf is fine—no web design required; reuse the menu they're printing anyway. The trade-off is that they'll have to pinch/zoom if they have a small display. It's a minor inconvenience to make the exact information they want available instantly.

index.pdf won't tend to play nicely with screen readers and also sucks for people on crappy mobile networks, so it's a minor inconvenience for some, and straight up unusable for others

> index.pdf won't tend to play nicely with screen readers

The horrible Wix sites most restaurants end up using are likely less accessible than a PDF. The Adobe PDF reader can reflow text.

> also sucks for people on crappy mobile networks

The average wysiwyg site builder produces bundles that are an order of magnitude larger than a PDF menu. Also, the PDF is easier to cache correctly and can be easily saved for offline access.

Re: Free static site generator for small restaurants and cafes

#72

Post by lmm »

spartanatreyu wrote: post #38
mvdtnz wrote: post #11

Earlier quoted context omitted.

No one is browsing the internet without JS today (within margin of error). Whether or not this "should" be the case, it is.

This is the wrong way of looking at it. Making a website's basic functionality work without JS isn't just for the random users who switch off their browser's JS runtime. It's also for the people who have a random network dropout or slowdown on a random file (in this case a JS file).

Then why does that same logic not apply to the CSS file?

Re: Free static site generator for small restaurants and cafes

#73

Post by lmm »

mvdtnz wrote: post #11
davisr wrote: post #2

No one should need JS to see the soups when that could be handled perfectly fine with CSS. I wish restaurants would just make their homepage a PDF of the menu.

No one is browsing the internet without JS today (within margin of error). Whether or not this "should" be the case, it is.

From a business perspective you can go further: the people who are browsing the internet without JS are people who are going to cost you more to support than they'll ever bring you in revenue. Just like trying to support Linux gamers, excluding them is a net positive.

Re: Free static site generator for small restaurants and cafes

#74

Post by justsomehnguy »

handoflixue wrote: post #46
spartanatreyu wrote: post #38

Earlier quoted context omitted.

This is the wrong way of looking at it. Making a website's basic functionality work without JS isn't just for the random users who switch off their browser's JS runtime. It's also for the people who have a random network dropout or slowdown on a random file (in this case a JS file).

> It's also for the people who have a random network dropout or slowdown on a random file (in this case a JS file). Does that really apply when the javascript is only ~2kb?

Do the end user should troubleshoot if that was a network dropout, some browser incompatibility or just a crappy code by a crappy coder?

> the javascript is only ~2kb?

It can be even 200Mb if it's not loaded properly and now a website doesn't even function.

Re: Free static site generator for small restaurants and cafes

#76

Post by mpweiher »

ok123456 wrote: post #71
vector_spaces wrote: post #59

Earlier quoted context omitted.

index.pdf won't tend to play nicely with screen readers and also sucks for people on crappy mobile networks, so it's a minor inconvenience for some, and straight up unusable for others

> index.pdf won't tend to play nicely with screen readers The horrible Wix sites most restaurants end up using are likely less accessible than a PDF. The Adobe PDF reader can reflow text. > also sucks for people on crappy mobile networks The average wysiwyg site builder produces bundles that are an order of magnitude larger than a PDF menu. Also, the PDF is easier to cache correctly and can be easily saved for offlin…

Why is Wix horrible...or why does it create horrible sites by default?

Curious, I haven't tried it.

Re: Free static site generator for small restaurants and cafes

#78

Post by DoctorOW »

davisr wrote: post #2

No one should need JS to see the soups when that could be handled perfectly fine with CSS. I wish restaurants would just make their homepage a PDF of the menu.

What an exhausting solution to a made-up problem. This is exactly the kind of functionality JS was made to provide. There's a lot more JS in the PDF.js renderer modern browsers, and if you're not using a modern browser it likely wouldn't render at all. As others have pointed out, you're asking restaurants to throw away mobile traffic, screen readers, anyone not on a mainstream desktop browser to save ~20 lines of code in a programming language you don't like.

Re: Free static site generator for small restaurants and cafes

#79

Post by ThomasMidgley »

davisr wrote: post #2

No one should need JS to see the soups when that could be handled perfectly fine with CSS. I wish restaurants would just make their homepage a PDF of the menu.

I wish restaurants would just make a homepage with menu _and_ opening hours.

In my area most restaurants have no website.

If they have a website it's often very hard to find their opening hours. Under 'contact'? Nope! At the footer? Nay! Maybe somewhere hidden in the menu PDF? With luck... Outside their homepage at google maps? Maybe. On their Tripadvisor page? Hahaha! Funny! Not.

Re: Free static site generator for small restaurants and cafes

#80

Post by nottorp »

ErroneousBosh wrote: post #23
davisr wrote: post #2

No one should need JS to see the soups when that could be handled perfectly fine with CSS. I wish restaurants would just make their homepage a PDF of the menu.

PDF is an enormous pain in the tits to view on a phone and has significant accessibility issues for people using assistive technologies. It's not even about blind people. People with ADHD or dyslexia use assistive technology, which frequently makes an absolute horlicks of interpreting PDF. It's one of the reasons I'm trying to move a lot of documentation at work away from PDF and onto just straight HTML. Plain old HT…

> People with ADHD or dyslexia use assistive technology

Wait for 2 more iOS redesigns and everyone will use assistive technology on Apple devices :)

Post reply on HN