![\"llms.txt](\"https://getpublii.com/blog/media/posts/91/llms-txt-statistic.webp\")
There's a new file causing arguments across tech Twitter, SEO communities, and developer forums. It's called llms.txt, and depending on who you ask, it's either the future of how AI systems discover your content — or a complete waste of time.
\nHere's what makes this weird: over 844,000 websites have already implemented it — according to BuiltWith's tracking as of October 25, 2025. Major companies like Anthropic (Claude docs), Cloudflare, and Stripe are using it. Yet not a single major AI platform has officially said they actually read these files.
\nYeah. Think about that for a second.
\nSo what's going on?
\nPicture this: someone asks ChatGPT or Claude a question about your product. The AI needs to fetch information from your website right now, while answering.
\nBut there's a problem.
\nYour website has navigation menus, cookie banners, footers, sidebars, JavaScript-heavy layouts, and marketing copy scattered everywhere. The actual useful information? Buried somewhere in all that noise. And the AI only has seconds to find it, plus limited \"context window\" space to work with.
\nThis is fundamentally different from how Google works. Google crawls your site over days or weeks, indexes everything, serves cached results. AI systems need to grab content in real-time during conversations with users. It's messy. Resource-intensive. Often inaccurate.
\nEnter llms.txt — a simple text file you place at yourdomain.com/llms.txt that essentially says: \"Hey AI, skip all the clutter. Here are my 10 most important pages, already in clean Markdown format.\"
\nJeremy Howard from Answer.AI proposed this back in September 2024. The idea spread fast. But whether it actually works? That's where things get messy.
\nThe format is deliberately simple — just Markdown. You start with your site name as an H1 header. Add a short description in a blockquote. Then organize your key pages under H2 headers like \"Documentation,\" \"Getting Started,\" or \"API Reference.\"
\nEach link follows this pattern: [Page Title](URL): Brief description of what's here.
That's it. No complex syntax, no XML schemas, no configuration files. A developer can write one by hand in 20 minutes.
\nThere's also llms-full.txt — a comprehensive version with all your documentation in one massive file instead of links. Cloudflare's version? 3.7 million tokens. Vercel's has been called \"a 400,000-word novel.\" The logic? Why make the AI follow links when you can give it everything upfront?
\nReal example from Stripe.com llms.txt:
\n# Stripe\n\n> Stripe is a technology company that provides financial infrastructure for businesses. Businesses of every size—from new startups to established public companies—use Stripe to accept payments online and in person, embed financial services, and create custom revenue models. For complete documentation in a single file, see [Full Documentation](https://stripe.com/llms-full.txt).\n\n## Payments\n\n- [Stripe Payments](https://stripe.com/payments): Accept payments online and in person globally with a payments solution built for any business—from scaling startups to global enterprises.\n- [Stripe Payments features](https://stripe.com/payments/features): Learn more about Stripe Payments features.\n- [Payment methods](https://stripe.com/payments/payment-methods): Acquire more customers and improve conversion by offering the most popular local payment methods around the world. Join millions of global businesses that launch and manage payment methods through Stripe.or Anthropic Claude Docs llms.txt:
\n# Claude Docs\n\n## Docs\n\n- [Kosten und Nutzung verfolgen](https://docs.claude.com/de/api/agent-sdk/cost-tracking.md): Token-Nutzung für die Abrechnung im Claude Agent SDK verstehen und verfolgen\n- [Benutzerdefinierte Tools](https://docs.claude.com/de/api/agent-sdk/custom-tools.md): Erstellen und integrieren Sie benutzerdefinierte Tools, um die Funktionalität des Claude Agent SDK zu erweitern\n- [Hosting des Agent SDK](https://docs.claude.com/de/api/agent-sdk/hosting.md): Bereitstellung und Hosting des Claude Agent SDK in ProduktionsumgebungenClean. Curated. Focused on the pages that matter most.
\nThe standard also suggests offering Markdown versions of your pages by adding .md to URLs (page.html.md). This gives AI systems pure text without HTML parsing headaches.
\nThe adoption list tells a story. It's not random small sites — it's developer tools, documentation platforms, and technical companies where AI coding assistants are critical.
\nMintlify made the biggest impact. In November 2024, they enabled automatic llms.txt generation for every documentation site they host. Thousands of technical docs — including Anthropic, Cursor, Pinecone, and Windsurf — got llms.txt files instantly. This adoption suggests the industry sees value in structured AI-readable documentation.
\nMajor tech companies show interesting implementation patterns. Anthropic has both llms.txt (8364 tokens) and llms-full.txt (481,349 tokens) covering their entire API documentation. Cloudflare organizes theirs by product, letting AI fetch only relevant context per service. NVIDIA split implementation between technical docs (1,259 tokens) and their main site (252,607 tokens). Stripe structures by product categories, using an \"Optional\" section for specialized tools like Stripe Climate.
\nDeveloper tools dominate. Supabase, Zapier, Modal, and dozens of others have adopted it. Makes sense — their users rely heavily on AI coding assistants, and accurate llms.txt files could improve the quality of AI-generated code suggestions about their platforms.
\nThree community directories actively track implementations: llms-text.com/directory lists 788+ verified sites, llmstxt.site shows hundreds with token counts, and directory.llmstxt.cloud categorizes by industry. These resources let you see real examples — valuable if you're considering implementation.
\nBut here's where it gets weird.
\nNot one major AI platform has officially committed to using llms.txt.
\nZero. Zilch. Nada.
\nGoogle's John Mueller explicitly stated on Reddit and Bluesky: \"No AI system currently uses llms.txt.\" OpenAI hasn't announced ChatGPT or GPTBot parse these files. Anthropic — despite publishing their own llms.txt — hasn't confirmed Claude's systems reference it during conversations. Google, Microsoft, Perplexity, and Meta? Radio silence.
\nThink about that. Websites are implementing a standard to help AI systems find their content, but the AI systems haven't confirmed they're looking for it.
\nSome SEO practitioners see OpenAI crawlers pinging llms.txt files every 15 minutes in their logs. But crawling a file doesn't mean using it for anything meaningful. Profound's GEO tracking shows Microsoft and OpenAI bots actively fetching both llms.txt and llms-full.txt, but this could just be exploratory crawling.
\nCould be nothing.
\nThe optimistic interpretation? Platforms are quietly testing before making commitments. The skeptical view? They're never going to adopt it because better solutions already exist or will soon emerge.
\nThe skeptics aren't holding back.
\nThe skeptical argument comes down to this: There's no proven evidence that llms.txt improves AI retrieval, boosts traffic, or enhances model accuracy. And no provider has officially committed to parsing it.
\nBeyond that, there's a trust problem. Separate files enable manipulation. You could put different content in llms.txt than what humans see on your actual pages. This breaks the fundamental compact of trustworthy indexing.
\nWhy would AI platforms trust it?
\nResearch backs up the gaming concern. A paper called \"Adversarial Search Engine Optimization for Large Language Models\" demonstrated that carefully crafted content-level prompts can make LLMs 2.5× more likely to recommend targeted content. If websites can put special instructions in llms.txt that don't appear in visible HTML, abuse potential is massive.
\nGoogle's John Mueller has advised SEOs to \"question everything\" and catch misleading information before investing time in unnecessary work. The implication? Don't chase shiny objects without evidence.
\nThe case rests on concrete realities:
\nCritics also point to what they call \"misinformation loops.\" SEO tools like Rank Math and SEMrush flag missing llms.txt as site issues. This creates pressure to implement without evidence of value. Business owners anxious about AI visibility adopt it, reinforcing the perception that it matters — even though it might not.
\nIt's a self-fulfilling cycle built on hope, not data.
\nThe counter-arguments focus on logical positioning and anecdotal signals.
\nCarolyn Shelby from Yoast frames it as future-proofing: \"Ranking is no longer the prize — inclusion is.\" Her logic? AI systems need clarity and structure. Even if platforms haven't committed yet, providing that structure positions you for when they do.
\nFair point.
\nThe strongest supporting evidence comes from direct conversations. Windsurf highlighted that llms.txt saves time and tokens when AI agents parse documentation — a concrete technical benefit. Anthropic specifically requested llms.txt and llms-full.txt for their documentation on Mintlify, demonstrating clear interest from a leading AI company (even if not for their inference systems).
\nGoogle included llms.txt in their Agents to Agents (A2A) protocol, signaling at least experimental interest. The low-risk, potential-reward calculation appeals to early adopters: implementation takes 1-4 hours with no demonstrated downside if platforms eventually adopt the standard.
\nJeremy Howard's vision extends beyond current reality. In March 2025, he stated: \"It's 2025 and most content is still written for humans instead of LLMs. 99.9% of attention is about to be LLM attention, not human attention.\"
\nBold claim. Maybe prescient, maybe premature.
\nThis framing suggests llms.txt is less about immediate SEO gains and more about philosophical alignment with an AI-mediated future. Whether this vision materializes or proves premature is the billion-dollar question.
\nOne case study from Springs Apps reported 20% increase in search engine visibility and 15% improvement in accurate AI query answers after implementation — though such data points remain rare and unverified by independent sources.
\nRobots.txt succeeded because it solved a mutual problem with minimal cost. Websites needed crawl control. Search engines wanted respectful access. Everyone benefited. Major platforms (Google, Bing, OpenAI, Anthropic) officially honor it. It emerged from consensus and evolved through RFC 9309.
\nSchema.org succeeded because Google, Microsoft, Yahoo, and Yandex jointly developed it. Search engines demonstrably use it for rich results. Benefits are measurable — rich snippets increase click-through rates by documented percentages.
\nSitemap.xml followed similar patterns — broad platform support preceded widespread adoption.
\nllms.txt? Has none of these characteristics yet.
\nIt's a single-party proposal without W3C involvement or consortium backing. No major LLM provider has announced support. Gaming potential is significant. Most concerning, there's no demonstrated value: traffic improvements, ranking benefits, or accuracy enhancements remain theoretical.
\nThe comparison reveals what typically makes web standards succeed: multi-stakeholder buy-in, clear and enforceable benefits, low gaming potential, integration with existing infrastructure, and explicit platform commitments.
\nllms.txt has... hope.
\nWhere llms.txt does fit naturally is in the broader evolution toward AI-readable content. Just as websites adapted to mobile, social sharing, and voice search, they'll adapt to AI systems. The specific mechanism — whether llms.txt or something else — matters less than the underlying principle: content must be structured for machine understanding while remaining valuable for humans.
\nRegardless of llms.txt, certain tactics demonstrably improve how AI systems understand and cite your content.
\nWrite direct answers to questions in the first paragraph. Use conversational language matching natural queries. Create strong heading hierarchies (H2, H3, H4) that make content scannable. Employ bulleted lists and comparison tables. Provide concrete examples with data and citations. Implement schema markup. Build internal linking that connects related concepts. Keep information up-to-date with clear timestamps. Demonstrate authoritative expertise backed by experience.
\nThese aren't AI-specific tricks — they're good content strategy that happens to serve AI comprehension exceptionally well.
\nThe convergence of human UX and AI optimization is the real insight.
\nResearch into Generative Engine Optimization (GEO) shows that certain tactics improve AI visibility: adding authoritative citations, using clear statistics, including relevant quotes, structuring content with crisp headings, and writing in natural language.
\nCompanies like Vercel report 10% of signups now come from ChatGPT due to GEO efforts, not traditional SEO. The shift is from \"ranking\" to \"being referenced\" — success means appearing in AI-generated answers, not just organic results.
\nTools like SEMrush's Enterprise AIO, Profound's GEO tracking, and Ahrefs Brand Radar now monitor AI visibility — tracking brand mentions in AI responses, citation frequency, and sentiment. This data remains imperfect but improves monthly.
\nYou know what matters? Being cited. Being referenced. Being trusted enough that AI systems pull your content when answering questions.
\nGood news — we've built a dedicated llms.txt Generator plugin specifically for Publii CMS that handles all of this automatically.
\nHere's what it does:
\nAutomatic content selection. The plugin identifies your most valuable content based on featured posts, main tags, and recent updates. No manual curation needed (though you can override if you want).
\nSmart organization. It groups posts by their main tags to show your site's core topics, adds featured articles automatically, and includes recent posts that weren't captured elsewhere. Everything follows the official llms.txt specification.
\nZero maintenance. The file generates during your normal Publii rendering process. Publish a new post? The llms.txt updates automatically. Mark something as featured? It gets added. No scripts, no manual updates, no forgetting.
\nFull control when you want it. Through a simple repeater interface, you can manually curate \"Key Resources\" — select specific posts or pages to highlight. Add optional notes for AI systems. Customize sections. Or just let the plugin do its thing.
\nConfiguration takes under 10 minutes. After that, you never think about it again.
\nThe plugin will be available soon through the Publii marketplace.
\nHere's the truth: you should add llms.txt to your site. All sites. Small blogs, local businesses, niche content communities, everything in between.
\nThe calculation is straightforward. There's literally no downside. The Publii plugin generates it automatically once, then maintains itself. It takes 10 minutes to enable. If AI platforms never adopt llms.txt, your site loses nothing — the file just sits there harmlessly. If they do, you're already there.
\nBut there's a bigger reason.
\nRight now, traffic is fragmenting. Your small business blog isn't just competing for Google visibility anymore. People are asking ChatGPT questions that could lead them to your content. Perplexity is summarizing information with citations. Claude is answering questions while pulling from your pages. These platforms handle hundreds of millions of searches monthly, and the number keeps growing.
\nYou're already visible to these systems. Google indexes your site, so AI platforms can crawl it. The question isn't whether they see you — it's whether they can find your best stuff quickly. An llms.txt file is basically a highlight reel. It says, \"Here's what I'm actually good at. Start here.\"
\nEven if llms.txt never becomes official protocol, you're training AI systems to understand your site better. You're curating how machines read you. That's valuable regardless of what comes next.
\nThe setup is genuinely painless with Publii. You're not writing complex XML or managing metadata spreadsheets. The plugin figures out your best content, organizes it, and handles updates. Add one line to your config file. Done. Move on with your actual work.
\nWhy wait for evidence when you can hedge your bets for free?
\nIf you're running Publii, the answer is obvious: install the plugin and enable it. Configuration takes less time than your morning coffee. You'll spend more effort worrying about whether to do it than actually doing it.
\nFor other platforms, evaluate your options. Some CMS systems already support llms.txt generation. Others let you upload it manually. The effort scales with your site's complexity, but it shouldn't be more than an hour of work for most sites.
\nThen continue doing what actually matters: write better content, improve your information architecture, maintain fresh material, build legitimate expertise. These fundamentals drive visibility in both human search and AI systems. llms.txt is an amplifier for content that already works.
\nThe AI platforms will figure out their own adoption timelines. Your job is to make your content as accessible and well-organized as possible. llms.txt is one tool for that. But it's a tool that costs nothing to implement and might matter a lot.
\nSo implement it.
\nllms.txt sits at the intersection of hope and pragmatism. It addresses a real problem — how AI systems efficiently find your best content — but may or may not become the actual solution.
\nWhat's undeniable? Content discovery is increasingly AI-mediated.
\nChatGPT, Perplexity, Claude, and Microsoft Copilot now receive enormous amounts of traffic from users worldwide. Google has launched AI Mode. Industry analysts forecast that AI-powered search could capture significant market share in coming years. These aren't distant possibilities — they're current realities reshaping how people discover information.
\nThe llms.txt debate crystallizes a larger question facing content creators in 2025: How do you prepare for a future that's simultaneously inevitable in direction but uncertain in specifics?
\nThe answer likely involves maintaining strong fundamentals while selectively experimenting with emerging standards, measuring everything possible, and staying flexible as the landscape evolves.
\nFor now, llms.txt remains a proposed standard seeking adoption — promising in concept, uncertain in execution, and controversial in value. The next 12-24 months will determine whether it joins robots.txt and sitemap.xml as essential web infrastructure or fades as an interesting experiment that addressed a problem AI systems solved differently.
\nEither way, the attention it's generating reveals how seriously the industry takes AI-readable content optimization.
\nAnd that seriousness? Entirely justified.
", "image": "https://getpublii.com/blog/media/posts/91/llms-txt-statistic-4.webp", "author": { "name": "Bob Mitro" }, "tags": [ "Publishing" ], "date_published": "2025-10-23T16:01:19+02:00", "date_modified": "2026-01-10T11:09:01+01:00" }, { "id": "https://getpublii.com/blog/publii-make-your-website-better-than-ever.html", "url": "https://getpublii.com/blog/publii-make-your-website-better-than-ever.html", "title": "Why Publii CMS Might Be the Website Tool You've Been Looking For", "summary": "Building a website today feels different than it did a few years ago. You're not just competing with other blogs anymore — you're trying to get noticed by AI models, satisfy increasingly picky search algorithms, and keep your visitors' data…", "content_html": "Building a website today feels different than it did a few years ago. You're not just competing with other blogs anymore — you're trying to get noticed by AI models, satisfy increasingly picky search algorithms, and keep your visitors' data safe while still delivering a fast, beautiful experience.
\n![\"Alt](\"https://getpublii.com/blog/media/posts/18/publii-make-website-better-than-ever.webp\")
That's a lot to juggle, especially if you're an independent creator who just wants to write and publish without wrestling with servers, databases, or security patches.
\nPublii solves this. It's evolved into something pretty remarkable since its early days.
\nI'll show you what makes it different — not with marketing hype, but with the actual features that solve real problems you're probably facing right now.
\nBefore we dive into specifics, here's the core idea: Publii generates static websites locally on your computer, then sends them directly to your server. No database. No WordPress backend sitting there vulnerable to attacks. No constant updates breaking your site at 3 AM.
\nEverything happens on your machine first. You write, customize, preview — all offline. Then when you're ready, you sync it to your hosting. The result is a website that loads instantly, stays secure, and costs almost nothing to run.
\nBut that's just the foundation. The real value comes from how Publii handles the details.
\nYou know what's annoying? Being forced to write in a specific editor that doesn't match your brain. Some people think in formatted paragraphs. Others live in Markdown. Some need semantic structure handled automatically.
\n![\"WYSIWYG](\"https://getpublii.com/blog/media/posts/18/three-editors-wysiwyg-markdown-block-copy.webp\")
\nPublii gives you three different editors, and you can switch between them on a per-post basis:
\nBlock Editor — This one treats each content type (text, image, video, code) as its own clean section. You can reorder things smoothly without cluttering up your interface with a million buttons.
\nWYSIWYG Editor — The classic approach. If you're comfortable with a regular word processor, this works exactly how you'd expect. It includes a live stats panel that tracks your word count, reading time, and sentence structure as you write. Small detail, but it keeps you aware of pacing without needing external tools.
\nMarkdown Editor — For speed-typists who hate lifting their hands off the keyboard. Type, format with symbols, keep your flow uninterrupted. If you've ever used Bear, Obsidian, you'll feel right at home.
\nThe point isn't just variety — it's that your content, your tools, your rules. You're not adapting to how some platform wants you to work.
\nLet's talk about a problem nobody enjoys fixing: image optimization.
\nHigh-resolution photos from modern phones are huge. If you upload them directly to a site, mobile users suffer. But manually resizing images for different screen sizes? That's tedious busywork.
\nPublii handles this automatically with responsive images. It creates multiple versions of each photo and serves the right one based on the visitor's device. Someone on a 4K monitor gets the full-resolution version. Someone on a phone gets a lighter file that still looks crisp on their smaller screen.
\nOn top of that, Publii automatically converts JPG and PNG images to WebP format — Google's newer, more efficient image standard. Smaller files, same quality. Your site loads faster without you doing anything.
\nWhat's useful for developers and designers: you can configure image handling separately for different parts of your site. Featured images in hero sections can have different sizes than featured images in post listings. Gallery images, content images, author backgrounds — each can be optimized independently. If you're building custom themes or need precise control, the documentation covers the details.
\nThis matters more now because page speed is a direct ranking factor. Google doesn't just prefer fast sites — it actively penalizes slow ones. And in the age of AI-powered search, where models like ChatGPT or Perplexity pull content to answer queries, technical performance signals trust and authority.
\nPrivacy regulations have changed since the early days.
\nGDPR in Europe. CCPA in California. Increasing user awareness about tracking. If you're running a site today, you need to handle this properly — not just for legal compliance, but because your visitors actually care.
\nPublii sites are private by default. Static sites don't collect user data, don't store credentials, don't send information to third parties. There's no database tracking visitor behavior. You're clean from the start.
\nBut most people do want some third-party tools. Analytics, maybe. Comments. A newsletter signup. Publii lets you add those, but with full privacy controls.
\n![\"Cookie](\"https://getpublii.com/blog/media/posts/18/publii-static-cms-cookies.webp\")
\nThe cookie banner system is more sophisticated than you'd expect. You can create a simple notice, or go deeper with granular consent options — letting visitors accept or reject specific cookie groups. Each third-party plugin can be tied to a consent category, so YouTube embeds only load after approval, Google Analytics respects user choices, and everything stays GDPR-compliant.
\nThere's also Google Consent Mode v2 integration built in. If you use Google Analytics 4 or Google Ads, this is crucial for maintaining data collection while respecting regulations.
\nWhat makes this different: the Publii app itself runs entirely offline on your computer. No cloud sync. No telemetry. No usage tracking. You're not feeding your content and habits back to some company's servers. It's your work, staying on your machine, until you decide to publish it.
\nPublii themes are hand-coded with plain HTML, CSS, and vanilla JavaScript. No React. No Vue. No heavy frameworks that load hundreds of kilobytes before your content even appears.
\nThis sounds old-school, but it's actually the smartest approach for static sites. Frameworks are great for dynamic apps. For content websites? They're overkill. They slow down load times, complicate the code, and make your site harder for search engines and AI models to interpret.
\nPublii's themes load fast because they're lightweight by design. And they're built with fluid typography — text that scales smoothly with screen size, not just at breakpoints. Even if someone resizes their browser window slightly, the layout adjusts to stay readable. Small touch, but it makes the experience feel polished.
\n![\"Typographic](\"https://getpublii.com/blog/media/posts/18/themes-rwd.webp\")
\nPublii goes deeper than most platforms: typographic precision.
\nThe themes use a modular scale for font sizing. Instead of randomly picking 16px for body text, 24px for an H3, and 32px for an H2, everything follows a mathematical ratio. Usually something like 1.25 (major third) or 1.333 (perfect fourth). This creates visual harmony — headings relate to each other and to body text in a way that just feels right, even if visitors can't articulate why.
\nThere's also careful attention to vertical rhythm. Each element aligns to a baseline grid, so line heights, margins, and spacing all follow consistent intervals. This isn't just aesthetic perfectionism — it makes long-form content significantly easier to read. Your eyes don't have to constantly adjust to irregular spacing as they move down the page.
\nAnd typography doesn't stop at sizing. Publii themes use variable fonts loaded locally from your server. No Google Fonts CDN calls. No external requests that slow down your first paint or leak visitor data to third parties.
\nVariable fonts are a relatively recent web standard that packs multiple font weights and styles into a single file. Instead of loading separate files for regular, bold, italic, and bold-italic (which means 4+ HTTP requests), you get one file with continuous control over weight, width, and sometimes even slant. Smaller total file size, more typographic flexibility, better performance.
\nIt's the kind of detail most people won't consciously notice, but it compounds with everything else to create a reading experience that feels professional and polished.
\nThemes also include lazy loading by default. Images, videos, even comments load only when the visitor scrolls to them. The initial page load is lightning-fast, which keeps bounce rates low and keeps visitors engaged.
\nThis has changed the most in recent years: what it means to be \"findable\" online.\"
\nTraditional SEO still matters — title tags, meta descriptions, clean URLs, XML sitemaps. Publii generates all of that automatically. But now there's a new layer: AI discoverability.
\nChatGPT, Perplexity, Google's SGE (Search Generative Experience) — these systems analyze websites differently than traditional search engines. They need semantic clarity. Clean structure. Metadata that helps them understand context and trustworthiness.
\nPublii generates semantic HTML5 by default. That means proper heading hierarchy, meaningful tag structure, and microdata markup for full post pages. This isn't just \"nice to have\" — it's how AI models determine whether your content is credible enough to cite or include in answers.
\n![\"Automatic](\"https://getpublii.com/blog/media/posts/18/open-graph-protocol.webp\")
\nYou also get Open Graph tags automatically. When someone shares your post on social media, it looks professional with the right image, title, and description. But beyond appearances, AI models also parse these tags to understand your content's context and authority.
\nAnd URLs? By default, Publii creates clean, readable links. Turn on \"Pretty URLs\" and extensions disappear entirely — just clear, semantic paths that make sense to humans and machines.
\nThe XML sitemap is auto-generated and kept current. Search engines and AI crawlers use this to explore your site efficiently, discover new content, and build a complete picture of what you offer.
\nThis stuff matters because visibility isn't just about Google ranking anymore. It's about whether an AI model considers your content trustworthy enough to reference when answering a user's question.
\nFor years, Publii focused exclusively on blog posts. That was fine for many users, but limiting for others who wanted static landing pages, about sections, or service descriptions.
\nVersion 0.46 changed that by introducing Pages — dedicated content types separate from your blog. Now you can build a complete website structure: blog posts for timely content, pages for evergreen information.
\nThis opens up Publii for more than just personal blogs. Small business sites, portfolios, documentation hubs — anything that needs both static pages and \"dynamic\" content.
\nEarly versions of Publii were fairly locked down. You got what you got. But starting with version 0.39, the plugin system opened things up.
\nThe Publii Marketplace now offers plugins for everything you'd actually need — analytics, search, comments, social sharing, galleries, syntax highlighting, and various developer tools. Both free and premium options available.
\nWhat's smart about this is the privacy integration. Each plugin can be tied to specific cookie consent groups. Add YouTube embeds or analytics? Visitor consent gets handled automatically through the cookie banner. No code editing needed.
\nEverything installs through the app interface. Just download, enable, configure. The ecosystem keeps growing, but the foundation works.
\nIf you're already running a WordPress site and feeling exhausted by constant updates, security worries, or slow load times, Publii includes a WordPress importer.
\nIt pulls your posts, pages, and categories over in minutes. You're not starting from scratch — you're moving your existing content to a faster, more secure platform without losing your audience.
\nLet me bring this all together. Publii's advantage isn't one killer feature — it's how everything compounds:
\nThe result? Sites that load in under a second, even on slower connections. That's not just \"nice for users\" — it's a ranking signal, a trust signal, and a conversion factor.
\nFast sites keep visitors engaged. Slow sites lose them before the content even appears.
\nPublii works best for independent creators, small businesses, and anyone who values control over their content.
\nIf you're a blogger, writer, or consultant who wants a professional web presence without technical headaches — this is it.
\nIf you're building a small business site and need fast performance without paying for expensive hosting — this handles that.
\nIf you care about privacy, both yours and your visitors', and you're tired of platforms treating your content as data to harvest — Publii respects that boundary.
\nWhat it's not great for: complex web apps, e-commerce with hundreds of products, or sites that need real-time user interaction. Static sites have limits. But for content-driven websites, those limits rarely matter.
\nPublii has changed a lot since 2016. It's no longer just a simple static site generator — it's a complete content management system designed for the realities of 2026.
\nYou get speed, security, privacy, and AI-readiness out of the box. You control your workflow with multiple editors and plugin options. You own your content completely, with no platform lock-in.
\nIt just works. No surprises at 3 AM. No security patches breaking your site. No performance degradation as your traffic grows.
\nIf you've been thinking about simplifying your web presence — or if you're just tired of fighting with WordPress — Publii is worth trying. Download it, build a test site, and see how it feels to work with a tool designed around your needs instead of around ads, tracking, and vendor lock-in.
\nYour website doesn't need to be complicated to be good. Sometimes simpler is exactly what wins.
", "image": "https://getpublii.com/blog/media/posts/18/publii-make-website-better-than-ever-copy.webp", "author": { "name": "Bob Mitro" }, "tags": [ "Publishing", "How it works?" ], "date_published": "2025-10-13T09:29:00+02:00", "date_modified": "2025-10-14T17:48:39+02:00" }, { "id": "https://getpublii.com/blog/why-you-should-own-your-content-not-rent-it.html", "url": "https://getpublii.com/blog/why-you-should-own-your-content-not-rent-it.html", "title": "Why You Should Own Your Content (Not Rent It)", "summary": "Look, I get it. WordPress.com is easy. Medium has that clean interface. Substack handles everything for you. It's tempting to just sign up and start writing. But here's the thing nobody talks about: you're building your house on someone else's…", "content_html": "Look, I get it. WordPress.com is easy. Medium has that clean interface. Substack handles everything for you. It's tempting to just sign up and start writing. But here's the thing nobody talks about: you're building your house on someone else's land. And that land? It comes with rules you didn't write, costs you didn't plan for, and an exit door that might be harder to find than you think.
\n![\"Why](\"https://getpublii.com/blog/media/posts/90/own-your-content-2.png\")
When Medium says it's free, what they really mean is: free until we change our minds. Free until we decide your content belongs behind a paywall. Free until we pivot our business model. Again.
\nI've watched this happen. Writers who spent years building audiences woke up one day to find their traffic cut in half because of algorithm changes. Or their articles locked behind paywalls they didn't choose. Or worse – their accounts suspended with no real explanation.
\nWordPress.com isn't much better. Sure, the basic tier is free. But want a custom domain? That'll cost you. Want to remove their branding? More money. Want plugins? Even more. Before you know it, you're paying $25 a month for features you could have for free elsewhere.
\nAnd Substack? They take 10% of everything you make. Forever. That might not sound like much when you're starting out, but imagine having 10,000 subscribers paying $5 a month. That's $5,000 going to Substack. Every. Single. Month. For what, exactly?
\nHere's what happens when you depend on a platform: They change their terms of service – you agree or you leave. They increase prices – you pay or you leave. They shut down a feature you rely on – you adapt or you leave. They get acquired by a company you don't trust – you... well, you get it.
\nYou're not really in control. You're a tenant, not an owner. And tenants can be evicted.
\nThis is where something like Publii makes sense. It's not sexy. It won't go viral on Twitter. But it gives you something those platforms can't: actual ownership.
\nPublii is a static site generator – but unlike command-line tools like Hugo or Jekyll, it's a desktop application with a clean graphical interface. What does that mean in practical terms? Your website is just files. HTML, CSS, images. No database constantly running in the background. No server processing requests. Just... files.
\nThink of it like the difference between renting an apartment and owning a small, portable house. Your Publii site? You can pick it up and move it anywhere. Host it on Netlify today, GitHub Pages tomorrow, your own server next month. Doesn't matter. The files are yours.
\nAnd here's something clever: Publii has plugins and themes, but they work differently than WordPress. Instead of running on your server (creating security risks), they operate locally on your computer during the build process. By the time your site hits the server, it's just clean, static HTML. All the functionality has already been baked in. No server-side code means no server-side vulnerabilities.
\nWant to dive deeper into the differences? Check out this comprehensive comparison between static and dynamic websites.
\nStatic sites are fast. Really fast. WordPress sites typically load in 2-4 seconds. That's if they're well-optimized. A poorly configured WordPress site? We're talking 6-10 seconds. Maybe more.
\nPublii sites? Under two seconds. Often way under.
\nWhy does this matter? Because people are impatient. Google is impatient. That slow-loading blog post? Most people will leave before it finishes loading. And Google will rank you lower for it.
\nBut speed isn't just about numbers. It's about respect. When your site loads instantly, you're respecting your readers' time. You're not making them wait while your database queries run and your plugins load and your tracking scripts phone home.
\nDiscover more about Publii's SEO and performance optimization features.
\nSpeaking of tracking scripts... Every major platform tracks your readers. They have to. That's how they make money. They build profiles, serve ads, collect data, sell insights.
\nWith Publii, there's none of that by default. No tracking. No cookies that need consent banners. No data collection. No third-party scripts running in the background. This isn't just nice for privacy-conscious readers. It's legally significant.
\nGDPR in Europe. CCPA in California. Privacy laws are spreading. And they're getting stricter. Running a site on major platforms with all their default tracking? You're probably violating several of them without even knowing it.
\nA static Publii site with no tracking? You're compliant by default. Right out of the box.
\nOf course, full GDPR compliance also depends on the content you embed – if you add a YouTube video or Google Maps, those bring their own tracking. But Publii gives you the tools to handle this properly. With built-in privacy features like consent management, lazy loading for embeds, and privacy-friendly alternatives for common services, you can maintain compliance while still having the functionality you need.
\nYou can add analytics later if you want. Privacy-respecting ones like Plausible or Fathom. But you're starting from a clean slate, not trying to untangle a mess of third-party scripts.
\nHere's a truth about websites: the more complex they are, the more vulnerabilities they have.
\nWordPress powers about 40% of the web. That makes it a massive target. Every plugin is a potential security hole. Every theme update is a risk. Every database query is an opportunity for SQL injection. The WordPress security team does good work. But they're always playing defense. New vulnerabilities are found constantly.
\nStatic sites? There's almost nothing to hack. No database to inject SQL into. No admin panel to brute force. No server-side code to exploit. Just static files sitting on a server.
\nCan someone hack your hosting account? Sure, if you use a terrible password. But they can't exploit your website itself because there's no website to exploit – just HTML files.
\nPublii isn't perfect. Nothing is.
\nYou need to think about hosting. Most platforms handle this for you. With Publii, you're choosing where to host. Though honestly, this takes about 10 minutes to set up on Netlify or Vercel, and then you never think about it again.
\nComments aren't built directly into the core app, but you can easily add them through plugins like Commento, Cusdis, Hyvor Talk, or others from the marketplace. Or just skip them entirely and direct people to social media.
\nAnd if you want complex functionality – user accounts, e-commerce, interactive features – you'll need to integrate external services. A pure static site can't do database-driven features.
\nBut here's the thing: most people don't need that stuff. Most people just need to publish articles. Maybe show some images. Link to their social media. That's it. And for that use case, Publii is actually better than the alternatives.
\nYes. WordPress has 60,000+ plugins.
\nYou know what else comes with 60,000+ plugins? 60,000 potential security vulnerabilities. 60,000 different ways for your site to break when something updates. 60,000 pieces of code that might conflict with each other.
\nI've spent hours debugging WordPress sites where two plugins just... didn't like each other. Nothing in the documentation said they'd conflict. But they did. And the site went down.
\nOr worse – plugins that aren't actively maintained become incompatible with new WordPress versions over time, leaving your site vulnerable or broken. Just look at Wordfence's weekly security reports: \"40,000 WordPress Sites Affected by Arbitrary File Read Vulnerability\", \"88 Vulnerabilities in This Week's Report\", \"200,000 Sites Affected by File Deletion Vulnerability\". This isn't occasional. It's constant.
\nWith Publii, there's just less stuff that can go wrong. Fewer moving parts. Fewer things to update. That's not a limitation — that's the point.
\nThis is where platform dependence really hurts.
\nTry exporting your content from Medium. You get a messy ZIP file with HTML fragments. Your images? They're still hosted on Medium's servers. Your formatting? Probably broken. Your URLs? All changed.
\nMoving from WordPress.com to self-hosted WordPress? Easier, but you're still tied to WordPress. And you lose features you might have been paying for.
\nMoving from Substack? Your subscriber list comes with you (if they let you export it), but you're starting over with distribution.
\nWith Publii, everything is just files. Your entire website is HTML files on your computer – that's what Publii generates as output. You can copy them anywhere. Back them up to Dropbox. Push them to GitHub. Host them in twelve different places at once if you want.
\nAnd here's something that really sets Publii apart: even in the unlikely event that the project ever stopped being maintained (which seems improbable given its growing popularity and active community), you'd still be fine. The app would continue working on your computer, generating your sites exactly as it does today. No server-side dependencies. No subscription that expires.
\nPlus, those HTML files? You can edit them directly in any code editor if you ever need to. Your content isn't locked in a proprietary format or trapped in someone's database.
\nEverything is yours. The files. The URLs. The images. All of it. Not licensed to you. Not stored on their servers. Yours.
\nLet's be realistic about costs:
\nYou can upgrade to paid hosting later if you need it. But most blogs will never outgrow free tier hosting on Netlify, Vercel, or Cloudflare Pages. So you're comparing $0 to $96-300+ per year. And with the free option, you own everything.
\nHere's why Publii hosting costs nothing: static sites don't need expensive infrastructure. No PHP processing. No MySQL databases. No server-side computing. Just files served straight from a CDN.
\nLike any tool, Publii isn't for everyone. It's designed with a specific use case in mind – and it excels at that. But it's important to understand whether your needs align with what Publii does best.
\nPublii makes sense if you're writing articles, running a portfolio, or just want a fast business site without the drama. It's for people who care about owning their platform, not renting it. People who value speed, privacy, and security. People who don't want ongoing costs eating into their budget every month.
\nBut if you need user accounts, real-time team editing, or built-in e-commerce? You'll need something else. If you're building a community platform with forums or complex interactive features, Publii isn't the right tool.
\nMost creators fall into the first category. They just want to write and publish without drama.
\nPlatforms want you dependent. That's their business model. Get you in, get you comfortable, get you invested. Then slowly turn the screws. Increase prices. Change features. Add restrictions.
\nIt's not evil. It's just business. But you don't have to play that game.
\nWith Publii, you're choosing independence. You're choosing to own your platform. You're choosing to control your costs. You're choosing to decide what tracking and analytics you use, if any. You're choosing to build on land you own. And when the next platform melts down – and there will be a next one, there always is – you'll be watching from a distance, grateful you made the choice to be independent.
\nIf this resonates with you, here's how to start:
\nThat's it. No database to configure. No security hardening. Just write and publish.
\nPlatforms come and go. Remember Google+? Vine? Posterous? All gone. Taking thousands of creators' content with them.
\nThe creators who owned their platforms? They migrated and kept going.
\nThis isn't about being paranoid. It's about being realistic. Companies change. Priorities shift. What's free today might not be tomorrow. Building on Publii means you're not making a bet on a company.
\nYou're making a bet on yourself. Your content stays yours. Your audience stays yours. Your control stays yours. That's not just better for business. It's better for peace of mind. And honestly? With everything going on in the tech world heading into 2026, a little peace of mind is worth a lot.
\nSo yeah. Platforms are convenient. But convenience has a price. Sometimes that price is money. Sometimes it's control. Sometimes it's both.
\nPublii is a bit less convenient upfront. But over time? It's liberating. You publish what you want, when you want, how you want. No algorithm to appease. No terms of service to worry about. No surprise price increases.
\nJust you, your content, and your readers. The way it should be.
\n* All pricing and features mentioned in this article were accurate as of October 11, 2025.
", "image": "https://getpublii.com/blog/media/posts/90/own-your-content.png", "author": { "name": "Bob Mitro" }, "tags": [ "Publishing" ], "date_published": "2025-10-11T10:55:05+02:00", "date_modified": "2025-10-11T17:28:22+02:00" }, { "id": "https://getpublii.com/blog/release-047.html", "url": "https://getpublii.com/blog/release-047.html", "title": "Publii CMS v0.47.x: Introducing the Notification Center, Many Fixes and Improvements", "summary": "Welcome back after the summer break! We're excited to announce the release of Publii CMS v0.47. This latest update is primarily focused on introducing a long-awaited feature: the Notification Center. Alongside this new addition, this version also includes a significant…", "content_html": "Welcome back after the summer break! We're excited to announce the release of Publii CMS v0.47. This latest update is primarily focused on introducing a long-awaited feature: the Notification Center. Alongside this new addition, this version also includes a significant number of patches and improvements, addressing many of the bugs and suggestions reported by our community.
\nStaying on top of the latest updates for Publii, its themes, and plugins is now easier than ever with the introduction of the much-requested Notification Center. This new feature provides a centralized hub for all important communications, ensuring you're always in the loop.
\n![\"Publii](\"https://getpublii.com/blog/media/posts/89/notification-center-publii.webp\")
The Center is organized into clear sections, displaying several types of alerts:
\nEach update notification provides all the necessary details at a glance, including your current version, the new version number or a link to view update details. Crucially, it also contains a direct link to the Publii site to download the new package. This puts you firmly in control; you decide if and when you want to update.
\nTo make notifications more relevant, they can be targeted to specific platforms. For instance, if we release a hotfix that only applies to the Windows version of Publii, only Windows users will be alerted.
\nWe also understand that you may not want to act on an update immediately. If a notification alert becomes distracting, you can simply mark it as read. This will dismiss the prompt, but the information will remain available in the Notification Center for you to review later. Furthermore, you can delete notifications at any time, or if you prefer, you can disable the feature entirely in the application settings by withdrawing your consent.
\nIn this release, we've also included several smaller, but highly useful, features that will definitely improve your day-to-day experience with Publii. These include:
\nWe've enhanced link management across Publii's editors to give you more styling and accessibility control. In the standard WYSIWYG editor, you can now directly specify a CSS class for your links. This is perfect for applying custom styles, like creating buttons or visually distinct links, without leaving the editor.
\n![\"Class](\"https://getpublii.com/blog/media/posts/89/block-editor-title-class-atributes.png\")
The Block Editor receives an even bigger upgrade. In addition to assigning a CSS class, you can now also define the title attribute for your links. This addition is excellent for improving your site's accessibility and providing extra context to your visitors.
\nFor users who frequently work with files, we're testing a new workflow enhancement that brings the File Manager right to your fingertips. This provides instant, one-click access, saving you a few steps every time you need to manage your site's files.
\nTo try it out, click the three-dots menu in the top-right corner and select App Settings from the dropdown. In the window that appears, scroll to the bottom to find the Experimental Features section, where you can enable this option.
\n![\"File](\"https://getpublii.com/blog/media/posts/89/show-file-manager-in-sidebar-option.png\")
Note: As this is an experimental feature, its behavior or placement may change in future updates based on community feedback.
\nFinally, this update also bundles in several other handy improvements:
\nSmall Upload in Repeater: For theme and plugin developers, we've added support for the smallupload control within the Repeater field. Previously, only the large image uploader was available. Now, for more compact layouts, you can use the much smaller upload UI.
Custom S3 Cache-Control Headers: Based on valuable community feedback (ref, GitHub), we’ve added more control over HTTP headers for S3-compatible deployments. Previously, Publii could set a restrictive Cache-Control: no-cache header on HTML files, which prevented some third-party CDNs from caching pages and impacting performance. You can now define custom cache-control headers directly in the S3 deployment settings. This provides greater flexibility and ensures better compatibility with a wider range of storage providers and CDN configurations.
New Global Variable: A new global variable, @website.description, has been added. Theme developers can now easily output the site's internal description (from the Site Settings) anywhere in their theme files.
We've made several improvements to enhance user experience and website functionality:
\nWe've also addressed several bugs to improve stability and performance:
\nog:url meta tags to be generated for nested pages, which could impact social media sharing. (ref. GitHub Discussion)This update also brings a range of important fixes that improve stability, consistency, and reliability across the platform.
\n./ prefix. (ref. GitHub Issue #2345)input[*] fields to prevent inconsistencies. (ref. GitHub Discussion #2352)This update brings essential fixes that improve rendering stability, editor functionality, and overall user experience across the platform.
\n{{#isNot}} Handlebars helper: Introduced the {{#isNot}} helper as the logical opposite of the existing {{#is}} helper, allowing theme developers to check when a page context does NOT match specified types.allowedPostStatus functionality to properly support featured, hidden, and excluded statuses, and added filtering for trashed posts. Previously, only any, published, and draft worked correctly.This update delivers several important improvements focused on performance, editor capabilities, API flexibility, and UI polish across the application.
\nThis maintenance update resolves a startup issue affecting new installations and users restoring a site from a backup.
\n.tar backup file. (ref. GitHub Discussion #2420)This update introduces several refinements across Notification Center behavior, menu handling, rendering logic, the block editor, UI robustness, and the WordPress importer.
\nThis update focuses on editor stability, media handling reliability, structured data generation, UI usability improvements, and bundled theme maintenance.
\n\"createAuthorPages\": false was set, preventing schema URLs pointing to non-existent pages. (ref. GitHub Issue #2464)This update focuses on security hardening, GitHub API stability, sitemap reliability, slug handling improvements, developer experience enhancements, and core dependency upgrades.
\n502 Bad Gateway when uploading a large number of files at once. The issue was caused by changes in GitHub API behavior affecting createTree requests with large payloads, which required improved batching and request handling to maintain stability. (ref. GitHub Issue #2465 or GitHub Issue #2567)parent field in page context, improving hierarchical data handling in themes. (ref. GitHub Issue #2522)@website.postsUrl for easier access to the posts listing URL.Cmd+H on macOS.(ref. GitHub Issue #2492)The release of Publii v0.47 reinforces our commitment to building a more intuitive and powerful platform, guided directly by the needs of our users. The new Notification Center is a major step towards better communication, while the host of enhancements and community-reported fixes demonstrates our ongoing dedication to quality and stability. Every update aims to refine your workflow and make managing your website a more seamless experience.
\nPublii's evolution is a collaborative process, and your voice is the most critical part of it. We invite you to continue sharing your ideas, suggestions, and bug reports on our community forum. Your active participation is what pushes the project forward.
\n", "image": "https://getpublii.com/blog/media/posts/89/publii_047.webp", "author": { "name": "Bob Mitro" }, "tags": [ "Releases" ], "date_published": "2025-09-23T09:27:56+02:00", "date_modified": "2026-04-24T14:50:19+02:00" }, { "id": "https://getpublii.com/blog/release-046-5.html", "url": "https://getpublii.com/blog/release-046-5.html", "title": "Publii 0.46.5 Released: Smarter Post Prefix Handling, Plugin Asset Improvements, and More", "summary": "Publii continues its evolution, bringing sharper tools and smarter workflows to static site creation. Version 0.46.5 introduces expanded post prefix support, improved asset management for plugins, or significant refinements to metadata handling. This release also delivers a wide range of…", "content_html": "Publii continues its evolution, bringing sharper tools and smarter workflows to static site creation. Version 0.46.5 introduces expanded post prefix support, improved asset management for plugins, or significant refinements to metadata handling. This release also delivers a wide range of stability improvements and bug fixes that enhance both the user experience and development flexibility. Whether you are building complex sites or simple blogs, Publii now provides an even stronger foundation for your projects.
\nSeveral improvements have been introduced to enhance site flexibility, simplify development workflows, and improve overall performance.
\nposts.hbs template. When a post prefix path (e.g., /blog/) is used, Publii will display a separate listing page using posts.hbs instead of falling back to the homepage index.hbs. This improves theme consistency and separation between homepage and post prefix listings./blog/) is used, Publii now automatically renders the prefix path using the posts.hbs template if available, or falls back to index.hbs. There is no longer a requirement to set a page as the homepage to display content at the prefix URL. This makes prefix handling more flexible and eliminates empty folders at post prefixes.This update also brings a range of important fixes that improve stability, consistency, and reliability across the platform.
\n?v=X) for CSS and JS files was not updated correctly during the first site generation after changes. Previously, HTML files were generated before the updated CSS/JS assets were available, causing the {{ css }} and {{ js }} helpers to load outdated checksums. This could result in browsers serving cached versions of styles and scripts even after synchronization. (ref. GitHub Discussion)/blog/) incorrectly pointed to the root URL (/) instead of the correct prefix URL. maxCount limit. Duplication is now correctly blocked once the maximum number of entries is reached. Additionally, the duplicate button is visually disabled when the limit is exceeded. (ref. GitHub Issue #2085)text inputs and textarea fields did not apply correctly when displayed inside tabbed plugin settings. With every update, Publii advances further in making static site management easier, faster, and more reliable. The improvements and fixes introduced in this release focus on flexibility, stability, and better user experience, building a stronger foundation for future developments.
\nWe encourage you to join the Publii Community to share your ideas, feedback, and suggestions. Your input plays a vital role in shaping Publii into the most powerful and intuitive static CMS available.
\nReady to explore the latest features? Download the newest version and take your site to the next level.
\n", "image": "https://getpublii.com/blog/media/posts/87/publii-0.46.png", "author": { "name": "Bob Mitro" }, "tags": [ "Releases" ], "date_published": "2025-04-26T07:44:41+02:00", "date_modified": "2025-04-26T19:57:54+02:00" }, { "id": "https://getpublii.com/blog/release-046-4.html", "url": "https://getpublii.com/blog/release-046-4.html", "title": "Publii CMS v0.46.4 Released - New Homepage Context, Improvements, and Bug Fixes", "summary": "With each update, Publii evolves, refining its capabilities to make managing static sites more seamless and intuitive. Version 0.46.4 introduces a new homepage context, several usability improvements, and a collection of bug fixes that enhance stability and content organization. This…", "content_html": "With each update, Publii evolves, refining its capabilities to make managing static sites more seamless and intuitive. Version 0.46.4 introduces a new homepage context, several usability improvements, and a collection of bug fixes that enhance stability and content organization.
\nThis release's main addition is the introduction of a dedicated homepage context for rendering. This feature streamlines the handling of homepage content and ensures better customization options across themes.
\nThe homepage context will now apply when:
\nWith this change, Publii now uses a unified context for any type of homepage - whether it’s a page or a listing of posts. This makes theming and customization more straightforward.
\nPlease note that the existing index context remains unchanged and is still assigned exclusively to homepage only.
Several refinements have been introduced to make site management more efficient:
\nThis update also resolves several issues affecting site generation, rendering, and linking:
\nindex.hbs for Rendering: Ensures the correct template is usedog:url Generation: When the post prefix is disabled, URLs in the og:url meta tag are now correct (ref. GitHub)#INTERNAL_LINK#. All author links now resolve correctly (ref. GitHub)maxCount Option: Resolved an issue where repeaters did not respect the maximum count setting (ref. GitHub)In addition to the previously listed fixes, we’ve also addressed some issues:
\n#INTERNAL_LINK# syntax incorrectly appended a comma at the end of the domain, leading to broken links (404 errors).These fixes require updating to the latest available version of Publii, which retains the same version number but comes with a new build number 17047.
\nWith each release, Publii becomes more refined, adaptable, and powerful. The new homepage context, along with a set of enhancements and fixes, makes this version one of the most stable and feature-rich yet.
\nAs always, we invite you to join the Publii Community and share your thoughts. Your feedback helps shape the future of Publii, ensuring it remains the best static CMS for modern site-building.
\nReady to upgrade? Download the latest version and explore the new features!
\n", "image": "https://getpublii.com/blog/media/posts/86/publii-0.46.png", "author": { "name": "Bob Mitro" }, "tags": [ "Releases" ], "date_published": "2025-02-28T08:21:42+01:00", "date_modified": "2025-03-31T08:45:20+02:00" }, { "id": "https://getpublii.com/blog/release-046-3.html", "url": "https://getpublii.com/blog/release-046-3.html", "title": "Publii CMS v0.46.3: New Features, Enhancements, and Bug Fixes", "summary": "We’re excited to announce the release of Publii CMS version 0.46.3 (build 17008), which includes a range of new features, improvements, and bug fixes to further enhance user experience and site functionality. This update builds upon the changes introduced in…", "content_html": "We’re excited to announce the release of Publii CMS version 0.46.3 (build 17008), which includes a range of new features, improvements, and bug fixes to further enhance user experience and site functionality. This update builds upon the changes introduced in version 0.46.2 and addresses key user feedback, making Publii an even more efficient and versatile platform for static site generation.
\nTo enhance organization and usability within the Publii app, we’ve introduced a new Site Description (Internal) field in the site settings. This additional textarea allows users to input a site description for internal reference only.
\nThe entered description will appear in the Publii interface on the site selection screen beneath the site’s name. This makes it easier to identify and manage multiple sites within the app, especially when working on numerous projects.
\nThis feature is particularly useful for users managing multiple sites. It provides a quick way to differentiate projects without affecting the site’s public-facing metadata.
\n![\"Internal](\"https://getpublii.com/blog/media/posts/85/internal-site-description.webp\")
![\"Internal](\"https://getpublii.com/blog/media/posts/85/site-description-page-listing.webp\")
This feature was added in response to a user request on GitHub (Issue #1831), highlighting the need to organize sites within Publii’s interface better.
\nWe’ve expanded the functionality of the slug display option to provide better transparency and control over URL structures in the Publii app. Previously, users could enable slugs on post and page listings by toggling the Show slugs on the post/page listings option in the App Settings.
\n![\"Slugs](\"https://getpublii.com/blog/media/posts/85/tag-author-slugs.webp\")
With this update, the option Show slugs across all listing views has been renamed and now includes slugs for tags, author listing pages, and posts and pages. This enhancement ensures consistent visibility of slugs across all relevant listing views, making site management more intuitive and organized.
\nThis update introduces support for Handlebars partials located in subdirectories. This enables developers to better organize their templates and maintain cleaner project structures.
\nExample:
\ntheme/\n|\n├── assets/\n|\n├── partials/\n│ ├── header/\n│ │ ├── logo.hbs\n│ │ ├── navigation.hbs\n│ │ └── search.hbs\n│ ├── footer/\n│ │ ├── copyright.hbs\n│ │ ├── links.hbs\n│ │ └── social.hbs\n│ ├── blog/\n│ │ ├── post-meta.hbs\n│ │ ├── post-excerpt.hbs\n│ │ └── post-tags.hbs\n│ └── shared/\n│ ├── pagination.hbs\n│ └── notifications.hbs\n│\n└── index.hbs\n└── config.json\n└── post.hbs\n└── page.hbs\nIn your templates, you can reference partials using their subdirectory paths:
\n{{> header/logo }}\n{{> shared/breadcrumbs }}\n{{> footer/social }}\nThis improvement was implemented in response to community feedback, as requested in a GitHub Discussion (#1785).
\nIframe plugins now support app notifications, making it easier for users to stay informed about changes and updates while working within iframe-enabled plugins. This improvement applies to plugins like the Language File Editor, where real-time notifications can streamline workflows by providing immediate feedback on actions or changes.
\nAdditionally, iframe plugins now better detect system color scheme changes. Previously, switching between dark and light modes required restarting the Publii app for the changes to take effect. With this update, color scheme adjustments are applied in real time.
\nWe've also addressed several bugs to improve stability and performance:
\n') in URLs containing #INTERNAL_LINK#. This ensures proper parsing, even when used within JavaScript. The update also resolves issues with links such as file/author, which previously required specific handling due to their non-numeric nature. It eliminates the need to search for the attribute's closing quotation or apostrophe (ref. GitHub Discussion).og:url meta tag and canonical links included an extra slash (//) in the URL under specific configurations. (ref. GitHub Discussion).settingsDisplay: \"tabs\" were saved in the wrong directory, and the preview remained empty. The upload and preview now work correctly regardless of the display setting (ref. GitHub Issue).fs.mkdirSync where appropriate, resolving an issue where adding featured images failed if the /input/media/posts folder did not exist. The folder is now created automatically, ensuring seamless functionality even when cloning the project from a repository (ref. GitHub Issue)..htpasswd files placed in the Tools/File Manager/root directory were not uploaded during FTP deployment. These files are now included in the deployment process alongside .htaccess (ref. GitHub Issue).Publii CMS v0.46.3 represents another step forward in our commitment to improving functionality, addressing user concerns, and introducing features that make managing static sites more intuitive and flexible.
\nAs always, we welcome your feedback in the community forum to help us shape the future of Publii. Stay tuned for more updates and enhancements, and thank you for being a part of the Publii journey!
\nWe look forward to seeing the fantastic static websites you create with this latest release.
\n", "image": "https://getpublii.com/blog/media/posts/85/publii-0.46.png", "author": { "name": "Bob Mitro" }, "tags": [ "Releases" ], "date_published": "2024-12-23T05:52:59+01:00", "date_modified": "2025-02-28T08:55:45+01:00" }, { "id": "https://getpublii.com/blog/publii-gallery-plugins.html", "url": "https://getpublii.com/blog/publii-gallery-plugins.html", "title": "Introducing Publii's New Gallery Plugins: A Better Way to Manage Image Galleries", "summary": "We are pleased to announce the release of the Core Lightbox Gallery and Simple Lightbox Gallery plugins, which introduce a new and improved way to manage and display image galleries in Publii. Below, we explain why gallery functionality is separated…", "content_html": "We are pleased to announce the release of the Core Lightbox Gallery and Simple Lightbox Gallery plugins, which introduce a new and improved way to manage and display image galleries in Publii. Below, we explain why gallery functionality is separated from themes and how this change benefits our users.
\nPlease note: This change is optional and not obligatory. Your theme's built-in gallery functionality will continue to work as it has in the past. However, if you want to use the new gallery plugins, you must update your theme or apply the changes described later in this article to your custom theme.
\nUntil now, galleries were built-in and managed directly within themes using PhotoSwipe v4. While this solution served its purpose for a long time, it had begun to show its age. Though reliable, PhotoSwipe v4 lacked many modern features, performance improvements, and customization options that newer libraries provide. As a result, many users expressed interest in upgrading to the latest version of PhotoSwipe or integrating alternative gallery libraries to meet their needs better.
\nAnother significant limitation was the built-in gallery's lack of flexibility. Each theme was restricted to the same gallery implementation, leaving no room for switching to alternatives or introducing customizations beyond the default settings. This was a frustrating constraint for users who wanted more control or unique site functionality.
\nMaintaining the built-in gallery also became increasingly challenging. Updating the gallery code required simultaneous updates to all themes, a process that was not only time-consuming but also inefficient. This approach tied gallery improvements to theme updates, often leading to delays in delivering new features and optimizations to users.
\nTo address these challenges, we decided to move the gallery functionality out of themes and into plugins. By decoupling galleries from themes, we can now provide users with multiple options for gallery libraries, each tailored to specific needs and preferences. This shift eliminates the reliance on theme updates for gallery improvements and ensures that new features and fixes can be delivered more quickly and efficiently.
\nTo kick off this new approach, we’ve introduced two plugins:
\nCore Lightbox Gallery: Powered by the latest version of PhotoSwipe (v5), this plugin offers modern features, including dynamic zoom controls, smooth animations, and advanced customization options. It's designed to deliver a sleek and high-performance gallery experience. A detailed description of its capabilities can be found on its marketplace page.
\nSimple Lightbox Gallery: Based on VenoBox 2, this plugin is perfect for users who value simplicity and elegance. It includes essential features like touch swipe navigation, keyboard accessibility, and customizable preloader animations, all in a lightweight package. Visit its marketplace page for more details and features.
\nBy transitioning to a plugin-based model, we’ve created a more versatile and efficient solution for managing image galleries. Users now have the freedom to choose the gallery experience that best suits their site, whether they prefer the modern capabilities of Core Lightbox Gallery or the streamlined simplicity of Simple Lightbox Gallery.
\nWith this approach, gallery plugins can deliver cutting-edge features without being tied to theme updates. This means faster feature releases, reduced maintenance overhead, and a cleaner, more efficient setup for both themes and plugins. It’s a win-win for users: improved performance, greater flexibility, and access to the best tools for managing and displaying image galleries.
\nThis modular approach also opens the door for introducing additional gallery plugins in the future, offering users even more options to suit their needs.
\nTo fully take advantage of the new gallery plugins, updating your themes to the latest versions is essential, released on December 10, 2024. These updates ensure seamless integration with the plugins.
\nIn most cases, these will be versions 2.1.0.0 or 3.1.0.0.
\nPlease note: If you prefer not to update your theme, its built-in gallery functionality will continue to work as it has in the past. However, if you want to use the new plugins but choose not to update your theme or are using a custom theme, you must make the manual adjustments described below.
\nLocate and remove the code responsible for loading the built-in gallery in the following theme files: /partials/head.hbs and /partials/footer.hbs This includes the main gallery initialization code and any conditional logic tied to gallery styles or assets.
Locate the head.hbs file (/Documents/Publii/sites/YOUR_SITE/input/themes/YOUR_THEME/ ) in your theme or its override and remove blocks of code like the examples below:
{{#is \"post\"}}\n {{#post}}\n {{#if hasGallery}}\n <link rel=\"stylesheet\" href=\"{{css \"photoswipe.css\" }}\">\n {{/if}}\n {{/post}}\n{{/is}}\n{{#checkIf @config.custom.frontSource '==' \"post\"}}\n {{#checkIf @config.custom.frontGallery '==' true}}\n {{#is \"index\"}}\n <link rel=\"stylesheet\" href=\"{{css \"photoswipe.css\" }}\">\n {{/is}}\n {{/checkIf}}\n{{/checkIf}}\nIn older theme versions, also remove code related to inline styles for PhotoSwipe icons:
\n{{#is \"post\"}}\n {{#post}}\n {{#if hasGallery}}\n <style>\n {{#checkIf @config.custom.galleryLightboxStyle '==' \"pswp--dark\"}}\n .pswp--svg .pswp__button,\n .pswp--svg .pswp__button--arrow--left:before,\n .pswp--svg .pswp__button--arrow--right:before {\n background-image: url({{@website.assetsUrl}}/svg/gallery-icons-light.svg);\n }\n {{else}}\n .pswp--svg .pswp__button,\n .pswp--svg .pswp__button--arrow--left:before,\n .pswp--svg .pswp__button--arrow--right:before {\n background-image: url({{@website.assetsUrl}}/svg/gallery-icons-dark.svg);\n }\n {{/checkIf}}\n </style>\n {{/if}}\n {{/post}}\n{{/is}}\n{{#checkIf @config.custom.frontSource '==' \"post\"}}\n {{#checkIf @config.custom.frontGallery '==' true}}\n {{#is \"index\"}}\n <style>\n {{#checkIf @config.custom.galleryLightboxStyle '==' \"pswp--dark\"}}\n .pswp--svg .pswp__button,\n .pswp--svg .pswp__button--arrow--left:before,\n .pswp--svg .pswp__button--arrow--right:before {\n background-image: url({{@website.assetsUrl}}/svg/gallery-icons-light.svg);\n }\n {{else}}\n .pswp--svg .pswp__button,\n .pswp--svg .pswp__button--arrow--left:before,\n .pswp--svg .pswp__button--arrow--right:before {\n background-image: url({{@website.assetsUrl}}/svg/gallery-icons-dark.svg);\n }\n {{/checkIf}}\n </style>\n {{/is}}\n {{/checkIf}}\n{{/checkIf}}\nNext, locate the footer.hbs file and remove the following pieces of code:
\n{{#checkIfAny post.hasGallery page.hasGallery}}\n {{> photoswipe}}\n{{/checkIfAny}}\n\n{{#checkIf @config.custom.frontSource '==' \"post\"}}\n {{#checkIf @config.custom.frontGallery '==' true}}\n {{#is \"index\"}}\n {{> photoswipe}}\n {{/is}}\n {{/checkIf}}\n{{/checkIf}}\nFor older implementations:
\n{{#is \"post\"}}\n {{#post}}\n {{#if hasGallery}}\n {{> photoswipe}}\n {{/if}}\n {{/post}}\n{{/is}}\n\n{{#checkIf @config.custom.frontSource '==' \"post\"}}\n {{#checkIf @config.custom.frontGallery '==' true}}\n {{#is \"index\"}}\n {{> photoswipe}}\n {{/is}}\n {{/checkIf}}\n{{/checkIf}}\nYou can also remove unused assets, such as CSS, JS, or SVG icons related to the built-in gallery and the /partials/photoswipe.hbs file.
That's it.
\nThe shift to plugin-based galleries represents a significant milestone for Publii. Whether you opt for the advanced Core Lightbox Gallery or the elegant Simple Lightbox Gallery, you can look forward to a modern, customizable, and seamless gallery experience.
\nIf you have any questions or need help transitioning your galleries, please don’t hesitate to contact our support team via the community forum.
", "image": "https://getpublii.com/blog/media/posts/84/core-lightbox-gallery.png", "author": { "name": "Bob Mitro" }, "tags": [ "Releases" ], "date_published": "2024-12-10T18:28:44+01:00", "date_modified": "2024-12-11T07:39:16+01:00" }, { "id": "https://getpublii.com/blog/release-046-2.html", "url": "https://getpublii.com/blog/release-046-2.html", "title": "Publii CMS v0.46.2: Content Conversion, New Blog Listing Options, Global UI Enhancements and more...", "summary": "We’re pleased to introduce Publii CMS version 0.46.2 (build 16967), bringing a range of updates that enhance flexibility in content management and improve site functionality. This release includes new options for creating custom blog post listings, tools for content conversion,…", "content_html": "We’re pleased to introduce Publii CMS version 0.46.2 (build 16967), bringing a range of updates that enhance flexibility in content management and improve site functionality. This release includes new options for creating custom blog post listings, tools for content conversion, expanded organizational options across the interface, and support for the Elixir programming language, among many other refinements. Each update aims to improve user experience, making Publii an even more powerful tool for creating and managing static websites.
\nTo further enhance flexibility in content management, we’ve introduced the ability to convert posts to pages and pages to posts. This feature allows users to adapt the structure of their website content more efficiently to meet changing needs.
\n![\"Post](\"https://getpublii.com/blog/media/posts/83/post-to-page-conversion.webp\")
In the Publii interface, this can be done by selecting one or more posts or pages in the list view. Once selected, click on the “More” dropdown menu at the top and choose the \"Convert to page\" or \"Convert to post\" option as needed.
\nDuring the conversion process, all metadata for the post or page will be preserved except for specific post/page options. This is because the options available for posts and pages may differ significantly. However, if you decide to convert the content back to its original type later, the original configuration settings will be restored, ensuring a seamless experience.
\nWhen we set the Posts Prefix in the SEO settings, for example, to \"blog,\" our posts will be displayed in the /blog/ directory, such as /blog/our-post/. By default, the /blog/ page will be built using the index.hbs file. This setup works well if we display a \"page\" as the homepage. But what if we want the /blog/ page to have a custom layout different from the homepage? In that case, we should use the posts.hbs file.
Simply place posts.hbs in the theme's root directory, and Publii will automatically skip index.hbs and display the contents of posts.hbs on the page specified by the posts prefix, e.g., /blog/. This gives users complete control over the appearance and layout of the blog page, independent of the design set for the homepage.
Additionally, ensure you include the appropriate feature flag in the Supported Features section in the theme’s config.json file. Add \"postsPage\": true to enable support for this custom layout functionality, as outlined in the Publii Supported Features documentation.
The theme settings have been enhanced with support for nested tabs, allowing for better organization of configuration options within the settings panel. This feature enables theme developers to create a more structured and user-friendly layout, especially useful when a specific section requires multiple settings that need to be grouped logically. By assigning a parentgroup to an option, you can nest it under a designated parent group, creating a clear hierarchy in the settings.
![\"Nested](\"https://getpublii.com/blog/media/posts/83/theme-nested-options.webp\")
For instance, let’s say you have settings related to the homepage and want to group specific hero section options within it. By using the parentgroup attribute, you can define these relationships in the theme configuration file as follows:
{\n \"name\": \"heroText\",\n \"label\": \"Hero Section Text\",\n \"group\": \"Hero\",\n \"parentgroup\": \"Homepage\",\n \"value\": \"\",\n \"type\": \"wysiwyg\"\n}\nIn this example, \"Hero Section Text\" is part of the \"Hero\" group, nested under the main \"Homepage\" settings. This approach organizes options more effectively and improves usability by helping users locate related settings quickly.
\nCurrently, this feature is supported by Bespoke theme in version 1.1.0.0.
\nWe have expanded the range of supported languages in syntax highlighting to include Elixir, addressing the needs of developers who use this language in their posts or documentation.
\nTo ensure Elixir syntax is displayed correctly on your website, you must enable the latest version of the Syntax Highlighter plugin, version 2.0.0, which adds support for Elixir. Make sure your plugin is up to date to take advantage of this new language support.
\nWe’ve made several adjustments to the interface to enhance usability and visual consistency across the app.
\nFirstly, we’ve reduced the base font size to 14px throughout the app, aligning it with standard application font sizing. Of course, users who prefer a larger font size can increase it in the app settings.
\nWe've also updated the right sidebar for posts, pages, tags, and authors. Section headers now have background colors to make them more easily identifiable.
\nWe’ve also refined various other elements, like icons and other small details, to create a cleaner, more cohesive look across the app.
\nWe've also addressed several bugs to improve stability and performance:
\nog:url and canonical tags for SEO (ref. GitHub Issue)src attribute (ref. GitHub Issue)Publii CMS v0.46.2 was initially planned as a simple hotfix, but we decided to go beyond quick fixes and add a few new features and modifications that enhance both functionality and user experience.
\nThese updates are a testament to our commitment to continually improve Publii based on user feedback and evolving web standards. While this release provides vital fixes, it also adds new tools to give our users more control and flexibility in managing their sites.
\nAs always, your feedback is invaluable in shaping Publii's direction. We encourage you to share your thoughts, ideas, and any issues you encounter in our community forum. Together, we can continue refining Publii to make it the best platform for static site generation.
\nWe’re looking forward to seeing what you create with this update and appreciate your ongoing support and collaboration.
\n", "image": "https://getpublii.com/blog/media/posts/83/publii-0.46.png", "author": { "name": "Bob Mitro" }, "tags": [ "Releases" ], "date_published": "2024-11-01T12:14:05+01:00", "date_modified": "2025-02-28T08:55:50+01:00" }, { "id": "https://getpublii.com/blog/release-046.html", "url": "https://getpublii.com/blog/release-046.html", "title": "Publii CMS v0.46.x: Introducing Pages, Enhanced Sync Mechanism, New Image Config Options and Simple Theme v.3", "summary": "We're excited to announce the release of Publii CMS version 0.46, which brings a highly requested feature from our community: Pages. Until now, Publii exclusively supported posts, but with this update, we've expanded the platform's capabilities to include dedicated pages,…", "content_html": "We're excited to announce the release of Publii CMS version 0.46, which brings a highly requested feature from our community: Pages. Until now, Publii exclusively supported posts, but with this update, we've expanded the platform's capabilities to include dedicated pages, offering a whole new way to manage your content.
\nFor quite some time, our community has been requesting a feature that allows for creating pages separate from posts, and we've listened. The new Pages tab in Publii v.46 allows users to create and manage pages with the same ease and flexibility as posts but with crucial differences catering to more complex site structures.
\n![\"Introducing](\"https://getpublii.com/blog/media/posts/82/publii-pages-3.webp\")
While the page creation process is similar to posts—choose one of the three available editors and start writing—the main distinction lies in how pages are treated within the site. Pages exist independently of the post loop, meaning they are separate entities that do not mix with your site's regular blog posts (listings).
\nLike with posts, Pages come with various options in the pageConfig settings. This means you can enable or disable features such as comments, display of the date, or author information. By default, these options are turned off for Pages, giving you a clean slate to work with. However, it's important to note that you won't find options like related pages or navigation between pages, as is available for posts. This is by design, reflecting the nature of Pages as standalone content rather than part of a sequential or related series.
One of the standout features of Pages is the ability to nest them, allowing for hierarchical structures. You can designate a page as a parent, with other pages acting as its children, and so on. This nesting can be managed directly within the page editor or in bulk using the Edit Hierarchy button available on the Pages listing.
\n![\"Nested](\"https://getpublii.com/blog/media/posts/82/nested-urls-3.webp\")
Another highly requested feature that comes with the Pages is support for nested URLs, providing more organized and user-friendly web addresses. Additionally, you can now natively set any Page as the homepage of your site. This means that the content of the selected Page, along with its individual settings like SEO, will be displayed as your site's main page.
\n![\"Set](\"https://getpublii.com/blog/media/posts/82/set-page-as-homepage-2.webp\")
If desired, you can move the previous index page with the post listing to a different directory, such as \"blog,\" by adjusting the settings in the \"Pretty URLs\" section of your site settings.
\n![\"Post](\"https://getpublii.com/blog/media/posts/82/post-prefix.webp\")
You must update your themes and plugins to the latest versions to take full advantage of the new Pages feature.
\nPages have been designed based on the existing post structures so that you may find additional page templates in your theme. This includes the standard templates and an \"empty container\" template, providing a blank canvas for adding your custom code. This flexibility ensures that Pages can be easily integrated into your site design.
\nImportant: If you have overridden theme files, we strongly advise against updating to the new versions without proper preparation, as it may cause your customizations to stop working correctly. Before proceeding with an update, carefully compare and merge your files, or consider renaming or removing the override folder.
\nFor those using custom themes or making significant modifications to official Publii themes, we have also published a detailed article in our dev documentation that guides you through manually adding Page support. This resource is invaluable for users who need to integrate Pages into their unique theme setups.
\nRemember to update your plugins to support the new Pages feature. This will help maintain full functionality and compatibility with Publii v.46.
\nAnother exciting enhancement is the addition of image support within the configuration options for various content types, including posts, tags, authors, and pages. Publii offers a range of customization fields, as detailed in our Theme Settings API documentation. With this update, you can configure images for these elements, providing even greater flexibility and creative options.
\n![\"Enhanced](\"https://getpublii.com/blog/media/posts/82/image-field.webp\")
This new feature is handy if you want, for example, to have multiple featured images. You can now configure a different featured image in your post teasers than the one displayed on the actual post page. The same applies to tags and author profiles, allowing you to present a more personalized and visually engaging experience across your site.
\nIn Publii v.46, we've further expanded the capabilities of the Repeater Field, which was first introduced in version 0.43 as a powerful tool for theme and plugin development. The Repeater Field allows for the dynamic addition of multiple instances of a particular set of fields within the Publii backend, offering a more granular level of customization and flexibility.
\n![\"Image](\"https://getpublii.com/blog/media/posts/82/image-support-in-repeater-field.webp\")
With this update, we've added support for two new field types within the Repeater control:
\nImage Field Support: You can now add image fields within a Repeater, allowing for the dynamic inclusion of images as part of your content configurations. This is particularly useful for scenarios where multiple images need to be managed dynamically, such as in sliders, where you can now create a slider from pictures and descriptions alone without needing post content.
\nFile-Dropdown Field Support: Additionally, we've introduced support for a file-dropdown field within the Repeater control. This field allows users to select files from the File Manager, offering a streamlined way to manage and incorporate various file types into your repeater-controlled content.
\nThese enhancements make the Repeater Field an even more powerful tool for developers and users, providing more options for customizing and managing content in Publii. Whether you're building complex layouts or need more control over your content's structure, the updated Repeater Field is designed to meet your needs more efficiently and quickly.
\nIn response to feedback from our users, we've significantly improved how Publii detects changes in synced files. Previously, Publii generated a single MD5 checksum for the entire site, which was stored in the files.publii.json file. This approach often led to issues where, despite only one file being edited, the sync process would mistakenly re-upload many files due to mismatched checksums.
With the new method, the files.publii.json file now contains a list of all files in your site, each with its own individual checksum. This change allows Publii to detect which files have been modified more accurately and ensure that only those specific files are uploaded during synchronization. Here's how it works:
files.publii.json now includes a detailed list of every file on your site, each accompanied by its own MD5 checksum. This allows Publii to precisely determine which files have been altered since the last sync.files.publii.json with the list on the server. If differences in checksums are found, only those files that have changed will be uploaded, reducing the risk of unnecessary bulk uploads and speeding up the deployment process.Note: After this change, your site may re-upload all files during the first synchronization, but this will only occur once. Subsequent syncs will only upload modified files.
\nNote: It's important to note that if, for any reason, you prefer to restrict access to the file list, you can create a redirect from the files.publii.json to your homepage or block access to the file using, for example,.htaccess rules.
This update should significantly improve the sync process, making it more accurate and efficient while providing better control over your site's deployment.
\nWith the release of Publii v.46, we're also excited to introduce the completely redesigned and rewritten Simple Theme v.3. This latest version features an enhanced appearance and a refined codebase, ensuring better performance and compatibility with the newest features in Publii, including full support for Pages.
\nThe redesign brings a fresh, modern look to the Simple theme while optimizing its underlying code for improved speed and flexibility. Whether you're creating a blog, portfolio, or business site, the updated Simple theme provides a sleek, responsive design that takes full advantage of Publii's latest capabilities.
\n\n![\"Simple](\"https://getpublii.com/blog/media/posts/82/simple-theme-v3-2.webp\")
Note: If you prefer to continue using the Simple theme in its previous form (v.2), we recommend not updating to v.3. The file for version 2 will still be available for download on the theme's page under the \"Changelog\" section.
\nIn addition to the Simple theme, nearly all Publii themes have been updated to support the new Pages feature. But that’s not all—these updates also enhance typography, making achieving the perfect look for your site easier.
\n![\"Italic](\"https://getpublii.com/blog/media/posts/82/italic-fonts.webp\")
We've added support for dedicated italic versions of variable fonts already existing within Publii themes. These are not just slanted versions of regular text but specifically designed italic fonts that offer a more polished and authentic appearance. These fonts are automatically detected and loaded, though you can turn off this feature if desired.
\nMoreover, the typography options in the Theme Settings have been expanded with several new controls under the FONTS tab. These include:
\nThese enhancements ensure you can fully customize your site's typography, aligning it perfectly with your design vision.
\nWe've made several improvements to enhance user experience and website functionality:
\n<a href=\"# INTERNAL_LINK#/post/29\">link</a> were only functional within the WYSIWYG editor. Now, this functionality has been extended to include theme config options, as well as tag and author settings, providing more flexibility in linking content throughout your site.isMainTag flag in tags data for easier differentiation between regular tags and main tags.We've also addressed several bugs to improve stability and performance:
\nresponsiveImageAttributes, responsiveSizes, and responsiveSrcSet helpers.featured_image_id was causing problems. (GitHub)Due to the extensive changes in version 0.46.2, including additional features and fixes, we’ve dedicated a separate post to detail all updates. For a complete overview of hotfix 0.46.2, you can read the full release article here.
\nPublii CMS v0.46 is a significant step forward in our mission to create a more versatile and user-friendly platform. With the introduction of the Pages feature, enhanced synchronization methods, expanded image configuration options, and numerous other improvements, we continue to respond to the needs and feedback of our vibrant community. These updates not only increase the functionality and flexibility of Publii but also ensure that our users have the tools they need to create and manage their websites more efficiently.
\nAs always, your feedback plays a vital role in shaping Publii's future. We encourage you to share your thoughts, suggestions, and any issues you encounter on our community forum. Together, we can make Publii even better.
\nWe’re excited to see what you create with the latest version and look forward to your continued support and collaboration.
\n", "image": "https://getpublii.com/blog/media/posts/82/publii-0.46.png", "author": { "name": "Bob Mitro" }, "tags": [ "Releases" ], "date_published": "2024-08-14T10:20:51+02:00", "date_modified": "2025-02-28T08:55:56+01:00" } ] }