1. 35
  1.  

  2. 17

    I like the idea, but this part really bothers me:

    you can craft a stylish modern site that will run faster than greased lightning even on mobile thanks to Google AMP technology

    How about saying no to Google’s attempts to monopolize the web?

    1. 6

      For what it’s worth, AMP support is off by default. The switch to enable it has this warning:

      AMP (accelerated mobile pages) creates mobile-optimized pages for your static content that render fast.

      Please note: when this option is enabled your website will load third-party scripts provided by Google’s AMP CDN.

      1. 16

        That first paragraph is still misleading, though. You know what else creates mobile-optimized pages that render fast? Publii with AMP turned off.

        Google’s AMP project is not benign. It sells itself as ‘faster pages’, but you don’t need AMP-the-technology for that; and it does all sorts of things are tenuously connected to speed, but clearly increase Google’s power over the web and its users. Especially: when a user goes from Google dot com to an AMP page, the site never sees that traffic because Google serves the page itself (all the better to track you with, my dear.)

        So Google’s purpose for AMP is pretty clear, and dmbaturin makes a good point that it should not be voluntarily included in any project that cares about the web.

        1. 2

          I largely agree, but this is just a technicality. I wouldn’t say Publii project cares about the web, they care about their users. And their users care about their own visibility. And someone told them they need amp. So they got amp.

          …or something close to that. Again, not saying that this is proper, just that this is how it probably goes down, for a lot of software projects.

      2. 1

        Why stop at Google AMP? I admire that Sourcehut Pages stated limitations include:

        Connections from CloudFlare’s reverse proxy are dropped. Do not help one private company expand its control over all internet traffic.

        1. 1

          What does this mean in practice? Can I be blocked from viewing content hosted on SH pages in some contexts?

          1. 2

            No, the primary goal (I’m assuming) is to prevent people following ‘guru’ advice and putting Cloudflare as a caching proxy in front of their site. If Page’s are not already distributed CDN for static content, I’m sure the goal would be to at least have a couple of mirrors distributed globally if that level of performance is needed in the future which makes Cloudflare redundant as well. Using Cloudflare in any capacity at this point is centralizing the internet because of how many people are using it because it’s ‘free’ and because SEO’d advice always recommends it. We saw Cloudflare go down not long ago and a massive portion of the clearnet went down with it. Cloudflare also tends to through up hCAPTCHAs for users on the Tor network, using VPNs, or just trying to use WiFi in a non-Western country putting an unnecessary burden on users seeking privacy.

      3. 12

        I’m setting up a blog for my father and I wanted something simple and free. I don’t like WordPress: it’s too complicated, the free .com plan has ads, it has a history of security issues, and I’d rather something static that I can deploy on GitHub Pages or Netlify. If it were for me, I’d use an SSG like Zola since I’m comfortable editing Markdown by hand, using git, etc. But for my father I wanted a WYSIWYG editor where you can just drag and drop images and not worry about the filesystem. I tried Netlify CMS but gave up after wasting hours on it. I kept getting errors about git-gateway despite trying everything in this thread.

        Then I found Publii and I was blown away by it. Does exactly what I want, and it’s free and GPL-licensed!

        1. 1

          My wife has been using Publii+Netlify for several sites, but now has complaints - it’s too rigid. I’ll have to start teaching her markdown and SSGs, I think :)

          Personally I think Publii is almost good. I would use it myself, if it didn’t have its internal database, and no simple way of versioning and forking (not software itself - sites that you create with it).

        2. 12

          Oh, we’re finally bringing back FrontPage and iWeb?

          1. 5

            Eh, almost. As far as I can tell, this imposes some file/directory structure constraints and has limited HTML, template and theme editing features. So I’d say we’re bringing half of WordWideWeb back for now :-). Took us about five years to get from that to FrontPage so, adjusting for modern software boilerplate and maintenance requirements I’d say give it another… ten years or so :-).

            On the bright side the HTML code that Publii produces looks considerably less atrocious than anything FrontPage ever did so maybe it’s worth waiting these ten years or so!

            1. 5

              Yeah I get that it feels full circle but I think this is a bit different. I’ve never used FrontPage but I remember iWeb feeling more focused on WYSIWYG web design. Publii feels more like a CMS with all the features you’d expect for a blog: posts, authors, tags, categories, excerpts, feeds, etc. The default theme looks nice, works on mobile, supports dark mode, and provides the exact right level of configurability for my use case (change colors, heading image, date format, pagination, etc.) without having to touch code.

            2. 5

              Looks interesting. This is exactly how Lektor works. A python static generator but with a very minimal admin interface. I have been using it since 2016 and it is just great.

              1. 6

                Yes, I also came across Lektor in my search. If their Mac desktop app had been working I would have tried it. But it’s not supported right now, so I assume you have to start a local server in a terminal in order to access the admin panel. I wanted something easy to use for people who aren’t comfortable with a CLI. That’s good you’re enjoying it though, maybe I’ll give it another look.

                1. 1

                  Oh yeah, I forgot about the Mac desktop client. I completely missed the fact that this is a desktop client. Though I like CLIs, I can see the appeal having used Microsoft’s LiveWriter (now OpenLiveWriter) in the past.

              2. 3

                I have a wordpress blog I manage - maybe I’ll give this a go to see if it is as easy to use. I prefer static site (and right now have my WP outputting static files), but the whole wordpress environment is a hot mess to get into if you want to mess with templates and internals.

                1. 1

                  From almost-personal experience (my non-techie wife has Publii), I can say I like it more then something like wordpress. But like wordpress, if you want a lot of flexibility (besides from just a static blog generator), it’s going to come in your way sooner or later.

                  For regular blogging, however, I like it just fine.

                  1. 1

                    I had issues with it importing my wordpress site. It totally broke the client, made no posts show up, but if I previewed it, it did build correctly. Very strange, but also a deal breaker as I can’t edit old posts or even see new ones.

                2. 3

                  I love the idea of publii! It says “static site generator” in the title, but screenshots seem to indicate that it (mostly?) works for blog-like pages. Is there any support for non-chronological pages like wordpress “pages” feature, or even some sort of content type builder?