SchemaLoad 13 hours ago

It's pretty sad how there doesn't seem to be any decent free options for websites which are easy to use. Squarespace and such cost a fortune which isn't worth it if you aren't trying to run a full ecommerce site. Plenty of services offer free hosting of static content but don't have any way a normal person can use them. Having to use a static site generator is too hard for non programmers.

I'm just surprised we haven't seem some app that can act like a wordpress admin page but generating a static output you can host for free or very cheap somewhere.

  • fckgw 12 hours ago

    Squarespace is like $20/mo for a basic site promoting your Brick and Mortar business. That includes domain, hosting, and a template/CMS. It's not that pricey.

  • syntheticnature 9 hours ago

    Google Sites exists. Buy a domain, point it at a free Google site. So easy a religion major can make a site that looks pretty decent (ha ha, only serious; I thought he'd used Wordpress at first) for just the cost of domain registration.

  • miladyincontrol 12 hours ago

    A webapp or gui WYSIWYG static generator with basic git support abstracted away would go far for many. Just let it push to some private repo which cloudflare pages or similar would deploy off of.

    It really feels like the only part of a non-static site most want is an editor. I absolutely loathe the matter but I do see why some restaurants only maintain a facebook page for their online presence.

    • burningChrome 11 hours ago

      This is what Netlify does. Hook up a private repo and deploy. Make a commit and it auto builds and you have a CI/CD pipeline. This is what I build all of my static sites with. You can do almost any JS framework like React, Angular, Vue, etc.

      Netlify does way more than this, but it makes hosting static stuff super easy.

      https://www.netlify.com/

  • [removed] 2 hours ago
    [deleted]
  • elemdos 9 hours ago

    That’s what I’ve been working on for the last few years: https://palacms.com (MIT) Not ready to announce the V3 RC yet (need to fill out the starter sites) but it’s working well if you wanna give it a spin - runs & deploys on Railway’s free tier.

  • weitendorf 12 hours ago

    This is exactly what we're trying to build with https://github.com/accretional/statue - you can email me or hit me up on Linkedin to get early access to our free static site hosting (which our new site for the project at https://statue.dev runs on, and which will Soon™ have a public-facing product doing exactly what you just asked for)

    Basically you'll be able to edit the markdown for your site in a souped up version of our lightly reskinned vscode IDE at https://brilliant.mplode.dev and instantly publish/preview the changes in the same browser tab in a pane. Brilliant comes with a full Linux environment running in a container on our cloud platform, and building a Statue static site is already a one-command operation. The little UI we're working on let's nontechnical people skip that and just edit files and click buttons to make changes and publish it, though.

    Here's a one-liner that will get you an entire static site with content (not the landing page yet, though) you can edit via markdown:

    yes | npx sv create . --template minimal --types ts --no-add-ons --install npm && npm install statue-ssg && npx statue init && npm install && npm run dev

    • kindawinda 11 hours ago

      This isn't exactly the point. He said easy to use. Yours requires developer skills which is not what he is looking for.

  • bryanhogan 11 hours ago

    Honestly, there are some easier ways out there now, although of course no solution is perfect.

    For non-technical people I'd recommend the Hostinger Website Builder, Obsidian Quartz or Astro Starlight.

    Although as a front-end dev I'd choose building a custom page with Astro, which has now become much easier though with good templates available + LLM assistance.

    I wrote a comparison of less-technical ways to build a website here with more details: https://webdev.bryanhogan.com/start/ways-to-build/

  • rrr_oh_man 12 hours ago

    I’m building something like this…

    NextJS + Git + Vercel.

  • tomp 12 hours ago

    how about something like feather.so? publish a website / blog from your Notion...

    haven't used it, but looks like a great idea!

davisr 14 hours ago

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.

  • venturecruelty 11 hours ago

    No one should need an entire PostScript interpreter to see the soup of the day, either. A restaurant menu is text and images. HTML and CSS are perfect for text and images.

    • andai 7 hours ago

      Nobody should need 60 million lines of code (Linux Kernel 30M + Chromium 30M) to render some text and images ;)

      • BrenBarn 2 hours ago

        640K ought to be enough for anybody.

        • lioeters 16 minutes ago

          I bet that's part of the reason why microcontrollers, embedded programming, and retro computing are all popular hobbies these days. A return to a simpler time, when programs are compiled to a few kilobytes and run as fast as the hardware allows. Graphics? Unicode? Who needs 'em, just a stream of ASCII and integers for me thanks.

  • hunter2_ 14 hours ago

    I agree with no JS, but why PDF over HTML? Hard-wrapping for letter-sized paper (ok, a PDF doesn't need to be letter-sized, but most menus are approximately that) with crapshoot reflow options for soft-wrapping in certain viewer apps is pretty dicey on a phone, mitigated only slightly by rotating the phone sideways.

    The only benefit I can think of is if it leads to more frequent updates by the restaurant, due to limited skillset.

    • ok123456 11 hours ago

      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.

      • vector_spaces 8 hours ago

        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

    • parpfish 8 hours ago

      Because they can make one nice pdf formatted to get printed out in the restaurant and then reuse it to display on the website

    • pastel8739 8 hours ago

      I vastly prefer looking at a PDF menu over an HTML one nearly all the time. PDFs are usually nicely formatted, and I don’t mind zooming and panning to see everything. HTML is frequently terribly formatted, interspersed with ads, slow, etc

      • foogazi 7 hours ago

        > HTML is frequently terribly formatted, interspersed with ads, slow, etc

        You can put ads into terribly formatted PDFs too

        • saghm 6 hours ago

          In theory, yes, but the parent comment is talking about what they've frequently encountered in practice. Maybe there's reason to expect that having a lot more PDFs of menus might not result in a similar experience, but it doesn't seem obvious to me at least

    • neuroelectron 12 hours ago

      The complexity between the modern web and a pdf is marginal. PDFs do get printed for menus. Editing a PDF and uploading it to the site, integrating prices and syncing between the site, online ordering, PDF menus is just part of the business. There are lots of platforms that help with this such as Slice.

  • victorbjorklund 12 hours ago

    PDF:s are not great on mobile. And you can’t easily translate them (I often translate restaurant menus when they are on a website with just 2 clicks)

    • AlotOfReading 11 hours ago

      Translating anything that renders on my screen is the same two clicks to open an LLM with the screen contents. I expect that will become an increasingly universal experience as LLM features get shoved into every nook and cranny of tech.

      • refactor_master 10 hours ago

        There's been a translate button for years which hooks deep into every nook and cranny of the website's HTML. It works great, it's built in and many restaurants even advertise it for tourists, because it's a zero-effort translation of their existing menu. Plus, it's low-data when you're inside a 1-bar basement restaurant.

        Using an LLM to translate the visible part of a PDF on a mobile... seems like the worst possible solution to the problem.

        • noosphr 8 hours ago

          It's the worst solution, apart from the fact it works better than all the other solutions.

      • jmyeet 10 hours ago

        Translating PDFs is more complicated than that because the strcture of a PDF document doesn't lend itself well to this kind of thing.

        For example: if there's a dish name with a 2 line description below it and some allergy symbols below that, in HTML you can imagine the document structure that produces that. In PDF terms that might be 4 separate objects and, in particular, the eyes can see the two lines are adjacent so they fit together but the document structure doesn't really represent it taht way, necessarily.

        This might also not work with translation because the lines are set for the size of the text they contain. Same for resizing the font.

        Put another waay, PDF should be viewed as a typeset and layout format, not a document format.

        • AlotOfReading 9 hours ago

          I think you're misunderstanding what I'm describing. It's getting a screenshot of the visible portion of the rendered document, not the document itself with all the tags and nastiness inside. The same feature works with a photo of handwritten text, where obviously no digital document exists. It's not perfect, but usually adequate for menu translation.

  • fullstacking 13 hours ago

    To be fair this project uses zero 3rd party npm modules for runtime. The total runtime JS it uses is 1.76kB in size.

    • Groxx 7 hours ago

      It also works just fine without JavaScript, so I'm not sure what they're trying to do with that comment.

      • hunter2_ 6 hours ago

        No, the comment correctly points out that the "Soup" button (and all of its siblings... the food categories) is inoperable when JavaScript is disabled. You're stuck with "All" instead of nice filtering. There are ways to achieve this without JavaScript.

  • dugmartin 14 hours ago

    I agree. There are lots of free AstroJS themes for restaurants that generate static html that you can host somewhere like Firebase hosting for free.

    - https://astro.build/themes/details/astropie/

    - https://astro.build/themes/details/astrorante/

    - https://astro.build/themes/details/tastyyy-restaurant-websit...

    • burningChrome 11 hours ago

      All of my static sites that I've built lately have been done on Netlify. Super easy to hook up to Github and the form handling is a breeze. I've known Mathias going back to when he was personally answering emails and promoting JAMSTACK so you can say I'm a bit biased. lol

      Netlify is a great company that I'll always support.

    • adzm 14 hours ago

      I love Astro; there is so much you can do with it.

    • bryanhogan 11 hours ago

      I was going to recommend the same! Astro + Astro theme + an LLM will get you very far these days.

      • riveralabs 10 hours ago

        I used to be all in on Jekyll. Now all I use is Astro + Tailwind + Claude, and it’s magic. No need for a theme with this combination.

  • DoctorOW 3 hours ago

    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.

  • [removed] 5 hours ago
    [deleted]
  • ThomasMidgley 3 hours ago

    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.

  • ErroneousBosh 12 hours ago

    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 HTML, with thin CSS on it to make it not be black-and-white Times New Roman. Kicking it oldschool.

    • nottorp 3 hours ago

      > People with ADHD or dyslexia use assistive technology

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

  • stronglikedan 14 hours ago

    A PDF can't get the user halfway through the delivery process before seeing the soups.

  • glxxyz 10 hours ago

    Remember during Covid where every restaurant's menu was a QR code on the table that linked to a PDF in S3?

  • pimlottc 13 hours ago

    PDF is a terrible experience on mobile

  • samdoesnothing 10 hours ago

    Nobody should need a PDF renderer to see the soups.

    Actually, nobody should need an XML parser to see the soups either.

  • mvdtnz 13 hours ago

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

    • spartanatreyu 11 hours ago

      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).

      • handoflixue 10 hours ago

        > 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?

      • lmm 5 hours ago

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

    • lmm 5 hours ago

      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.

  • cess11 13 hours ago

    The soup shows for me without JS.

  • fullstacking 10 hours ago

    No one should need PDFs to see the soups when they can be handled perfectly fine with CSS scoped to print and save to PDF....

    /s

mrasong 4 hours ago

How should the menu be adjusted then? Baristas aren’t into code, no one’s gonna learn programming just to tweak a menu.

captn3m0 11 hours ago

I'm not seeing anything very specific in the code - feels like this could be just another Jekyll theme and still work the same. There's some custom front-matter in markdown files, but change that to regular YAML and it will just work.

  • fullstacking 10 hours ago

    There is some code for looking up the geo lat/log of locations at compile. not sure how you would do that. But yeah outside of that your are mostly correct.

    I used elixir because thats what I know and love so it was mostly just a personal choice rather than a technical one.

codewritinfool 14 hours ago

Link at the bottom of your example page results in 404. For me, anyway.

zoobab 2 hours ago

Paper menu, no QR code or internet for me.

bhelkey 12 hours ago

A couple of things:

First, the site generator is MIT licensed but I don't see a link to the license. If someone forks this generator, would they be in compliance with MIT license requirements?

Second, the images linked in this site are quite nice. I can imagine someone choosing to use some of them as is. Are they yours to share?

Third, it appears that you are targeting non-developers. I would think about how to make it as easy as possible to customize. Decisions like putting images in "priv/output/images" seems a bit confusing.

[removed] 10 hours ago
[deleted]