GITNUXSOFTWARE ADVICE
Art DesignTop 10 Best Magazine Maker Software of 2026
Top 10 Magazine Maker Software comparison with ranking criteria for layout pros, covering Affinity Publisher, Adobe InDesign, and QuarkXPress.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Affinity Publisher
Master pages with paragraph and character styles for consistent magazine spreads.
Built for fits when magazine teams need style-based pagination automation without server governance..
Adobe InDesign
Editor pickInDesign scripting API for automating style application, content placement, and batch document updates.
Built for fits when magazine teams need deterministic page layout with template reuse and scriptable batch edits..
QuarkXPress
Editor pickXTensions extension framework for custom import and export actions inside QuarkXPress workflows.
Built for fits when teams need repeatable magazine layout automation with custom XTensions workflow steps..
Related reading
Comparison Table
This comparison table reviews magazine and layout publishing tools by integration depth, including how each platform maps content into a shared data model and what schema supports workflows across devices and teams. It also compares automation and API surface for provisioning, extensibility, throughput testing, and content operations, plus admin and governance controls like RBAC, audit log coverage, and configuration options. Readers can use the table to evaluate tradeoffs in API-driven publishing pipelines versus template-based editing.
Affinity Publisher
desktop publishingDesktop publishing software for designing magazine layouts with typographic controls, master pages, and export to PDF for print-ready output.
Master pages with paragraph and character styles for consistent magazine spreads.
Affinity Publisher is built for magazine-style production with master pages, text and frame tools, and style-driven formatting that can be applied consistently across spreads. Assets created in Affinity Designer and Affinity Photo can be brought into page layouts without flattening the full workflow into a single raster export step. The data model centers on document objects such as frames, layers, and text styles, which makes changes like typography updates and element reflow more predictable than ad hoc edits.
A key tradeoff is limited centralized admin controls. RBAC, audit logs, and org-level provisioning are not exposed in the authoring surface, so multi-user governance depends on file discipline and external process controls. Affinity Publisher fits magazine shops that run mostly local or small-team production with controlled handoffs and repeatable style templates.
- +Master pages and paragraph styles keep typography consistent across large magazines
- +Layers and reusable components support controlled layout refactors
- +File-based interchange with Affinity Designer and Affinity Photo preserves an asset workflow
- +Scripting enables repeatable batch operations for layout and publishing tasks
- –No documented RBAC controls for shared projects or role-based editing
- –No built-in audit logs for changes across multi-user production
- –Automation and API surface are narrower than dedicated CMS and DAM ecosystems
- –Automation control is more dependent on local workflow discipline than centralized governance
Best for: Fits when magazine teams need style-based pagination automation without server governance.
Adobe InDesign
professional layoutProfessional layout tool for magazine-style page composition with advanced typography, styles, multi-page documents, and high-fidelity PDF export.
InDesign scripting API for automating style application, content placement, and batch document updates.
InDesign is the core authoring surface for magazine makers who need typography control and production-ready page composition. The data model supports text, linked graphics, styles, and structured layout objects that map cleanly to magazine templates and recurring sections. Integration depth is strongest when paired with Adobe services for asset management and file handoff into broader publishing pipelines. Automation comes from built-in scripting and extensibility points that can update content, apply style rules, and drive batch operations across documents.
A tradeoff appears in automation and governance depth. InDesign’s automation surface is centered on scripting and document operations, and it does not provide the same end-to-end, API-first content operations model as dedicated publishing platforms. In practice, it fits teams that need layout determinism and template reuse while using separate systems for ingestion, scheduling, and distribution. It is a good fit when throughput depends on consistent redesign of existing templates rather than fully schema-driven content modeling.
- +High-fidelity magazine layout control with typography styles and reusable templates
- +Scripting support for repeatable layout edits and batch document processing
- +Strong integration with Adobe asset and publishing workflows for handoff
- +Document structure and styles support consistent section templates
- –Automation surface is script-driven rather than schema-driven
- –API integration breadth is narrower than platforms built around content models
- –Admin governance relies more on Adobe identity and sharing patterns than document RBAC
- –Data modeling favors layout objects more than structured editorial schemas
Best for: Fits when magazine teams need deterministic page layout with template reuse and scriptable batch edits.
QuarkXPress
publication layoutPage layout application for multi-page publications with grid-based design, typography tooling, and print and digital output workflows.
XTensions extension framework for custom import and export actions inside QuarkXPress workflows.
QuarkXPress provides a data model for page composition, styles, and components that can be driven through templates and repeatable layout rules. XTensions and scripting hooks support custom actions for publishing steps like asset handling, format output, and batch processing. Integration depth is strongest when downstream systems can align with QuarkXPress’ document and export model. Automation throughput is most predictable for controlled production pipelines where content structures stay consistent.
A tradeoff appears with enterprise governance needs because the automation and API surface is tied to the authoring and publishing runtime rather than a centralized schema service. Teams that require API-first data synchronization and RBAC-scoped content orchestration often need external middleware to map their schemas into QuarkXPress’ layout constructs. QuarkXPress fits best when magazines and multi-format documents can be generated from stable templates and controlled data feeds. It is a practical fit when the main integration requirement is repeatable publishing output rather than real-time content platform synchronization.
- +Document-centric data model supports repeatable template-driven magazine layouts
- +XTensions enables custom import, export, and workflow actions for publishing pipelines
- +Batch publishing supports higher throughput for controlled production runs
- +Style and layout rules reduce variation across editions and reprints
- –API surface is not designed around platform-wide event streams or headless provisioning
- –Governance controls are less RBAC-forward than enterprise publishing systems
- –Schema mapping for complex DAM or CMS models often needs external middleware
- –Extensibility work typically requires plugin development rather than configuration-only control
Best for: Fits when teams need repeatable magazine layout automation with custom XTensions workflow steps.
Canva
template-driven designWeb-based design workspace with magazine templates, multi-page document editing, and export options for PDF and print formats.
Brand Kit and reusable brand assets enforce consistent typography, colors, and logos.
Canva centralizes magazine-style layout and brand control around reusable design components and templates. It integrates with external sources through file import, media libraries, and export formats that support editorial workflows.
Automation and extensibility depend on supported APIs for assets, templates, and publishing actions, plus workflow integration via webhooks or connectors offered by the ecosystem. Governance relies on role-based access controls, workspace permissions, and admin-managed brand settings to keep production consistent.
- +Template and brand kit controls keep magazine pages consistent across editions
- +Media management supports versioning for images, logos, and brand assets
- +Export options cover print and web needs with predictable typography handling
- +API and automation options support asset-driven generation and publishing flows
- –Magazine pagination logic can require manual layout adjustments
- –Data modeling for structured article content is limited outside external CMS layers
- –Automation depth depends on available API endpoints for publishing actions
- –Fine-grained approvals can be constrained by workspace permission granularity
Best for: Fits when editorial teams need brand-governed magazine layouts with external content systems.
Lucidpress
cloud publishingBrowser-based publishing tool that assembles multi-page magazine designs from assets with layout automation and export controls.
Template and content API for updating multi-page layouts from external workflows.
Lucidpress is a magazine and multi-page layout builder that exports finished publishing files. Content is managed through reusable assets and templates tied to a structured design data model.
The integration depth is strongest through asset workflows and links to external systems via import and export, with an API surface that supports programmatic content and template operations. Automation relies on external orchestration around those API and configuration primitives rather than built-in rule engines.
- +Template-based magazine layouts keep formatting consistent across issues
- +Reusable assets reduce rework across pages and variants
- +API supports programmatic template and content updates
- +Configuration and RBAC support role-based access management
- +Audit and activity history tracks administrative changes
- –Automation depends on external orchestration for multi-step workflows
- –Data model changes can require careful template governance
- –Complex publishing rules need custom integration logic
- –API coverage may not include every niche designer action
- –Bulk throughput for large catalogs depends on integration design
Best for: Fits when teams need governed templates and programmatic updates for magazine production.
Microsoft Publisher
office publishingWindows desktop publishing product for creating multi-page publications with templates and PDF-based print delivery.
Master pages and page templates for consistent magazine branding across long issues.
Microsoft Publisher supports magazine-style layouts through page templates, master pages, and fine-grained styling built around document-centric publishing workflows. Integration depth is limited because Publisher documents are not backed by a first-class content schema for automation and API-driven provisioning.
Automation and API surface are minimal since Publisher primarily operates inside the desktop authoring experience rather than a programmable magazine data model. Governance and admin controls depend on Microsoft 365 tenant policies for file access, but Publisher itself does not provide RBAC, audit logs, or extensibility controls at the publishing-object level.
- +Desktop page layout tools with master pages and reusable templates
- +Direct control of typography, spacing, and multi-page composition
- +Works with Microsoft 365 files through Save and file interoperability
- –No documented API or automation surface for magazine data provisioning
- –Limited integration depth with external content schemas
- –Weak admin governance for publishing objects like sections and issues
Best for: Fits when small teams need repeatable magazine layouts with minimal automation requirements.
PageR
digital magazineInteractive publishing and digital magazine builder that formats content for web viewing with page-based layout and sharing links.
API-based page provisioning from schema-backed templates and configuration sets.
PageR focuses on schema-driven page templates and API-first provisioning for magazine-style content layouts. It supports an automation surface for generating pages from structured data and configurations.
The data model centers on content entities, layout rules, and environment-specific settings that can be managed with role-based access controls and audit logging. Admin governance focuses on workspace boundaries, controlled deployments, and traceable changes across page builds.
- +API-first provisioning for pages from structured content and layout rules
- +Schema-driven templates keep magazine layouts consistent across builds
- +RBAC controls restrict authoring versus publishing operations
- +Audit log provides traceability for page and configuration changes
- –Automation depends on consistent data modeling for reliable rendering
- –Complex layout logic can require careful template versioning
- –Integration throughput can bottleneck on large content batches
- –Extensibility often requires aligning custom fields with the schema
Best for: Fits when editorial teams need API-based page generation with RBAC and auditable publishing changes.
Flipsnack
flipbook publishingDigital flipbook maker that converts PDF or assets into paginated interactive magazine experiences for online viewing.
Interactive magazine publishing with embed-ready outputs for consistent distribution across channels.
Flipsnack focuses on document publishing for magazines, with layout templates and interactive components designed for fast page rendering and repeatable exports. Its integration depth centers on share links and embed outputs, which define a simple data model for published assets rather than a granular document schema.
Automation and API surface are oriented around creating and updating publishable assets, with extensibility most practical via webhooks and workflow integrations than via authoring-time schema control. Admin and governance controls support role-based access and asset ownership patterns, with audit visibility tied to account activity within the workspace model.
- +Magazine templates support consistent page grids and reusable design systems
- +Interactive elements add embedded media and links without manual scripting
- +Embed and share outputs make downstream publishing integration straightforward
- –Data model centers on published assets, limiting per-element schema governance
- –Automation surface lacks granular authoring controls compared with API-first CMS workflows
- –RBAC is workspace scoped, which can be limiting for multi-tenant governance
Best for: Fits when teams need repeatable magazine publishing with integration via embeds and lightweight automation.
Issuu
hosted publishingDigital publishing platform that hosts magazine issues and provides viewer-based presentation with page navigation and embedding.
Document-to-page viewer conversion with magazine-style navigation and embedded media rendering.
Issuu publishes and hosts magazine-style pages created from uploaded document files. It preserves a page-oriented reading surface with embedded media and viewer presentation settings.
The integration story centers on ingesting assets and managing metadata, which limits data model control compared with schema-first magazine systems. Automation and extensibility depend largely on workflow around content provisioning and distribution rather than deep API-driven layout governance.
- +Page-based viewer rendering for uploaded magazine files
- +Metadata-driven organization for issues, series, and collections
- +Embedding and reading settings support media-rich presentations
- +Distribution workflows for publishing schedules and visibility
- –Limited evidence of layout-level schema governance via API
- –Content model focuses on published assets over configurable components
- –Automation surface is more provisioning-oriented than event-driven
- –Admin controls show less granularity for RBAC and audit depth
Best for: Fits when teams publish document-based magazines and need hosting plus consistent metadata control.
Publuu
digital magazinesDigital publishing software that turns PDF files into interactive magazines with viewer settings and embed options.
Interactive magazine publishing with web-ready viewing and embed outputs per issue.
Publuu fits teams that publish magazine-style content and need repeatable publishing workflows across multiple issues. It focuses on designing interactive page layouts, hosting them for web and embedding, and tracking readership metrics tied to published assets.
Integration depth is centered on publish-and-embed flows, with limited visibility into a public API surface for automated provisioning. Automation and governance controls depend on account roles and project organization rather than external schema-driven workflows.
- +Interactive magazine pages with embedded media support
- +Publishing workflow supports multiple issues and versioned content updates
- +Share and embed outputs are consistent across devices
- +Readership analytics connect engagement back to published pages
- –API surface for automation and provisioning is not clearly documented publicly
- –Extensibility options rely more on editor features than external integrations
- –RBAC granularity is limited compared with enterprise publishing stacks
- –Audit log availability and export are not emphasized for governance needs
Best for: Fits when teams publish interactive issues and manage updates without heavy external automation.
How to Choose the Right Magazine Maker Software
This guide covers magazine maker workflows across Affinity Publisher, Adobe InDesign, QuarkXPress, Canva, Lucidpress, Microsoft Publisher, PageR, Flipsnack, Issuu, and Publuu. It focuses on integration depth, the underlying data model, automation and API surface, and admin governance controls.
The recommendations compare layout-first tools like Affinity Publisher and Adobe InDesign with schema-first and provisioning-first tools like Lucidpress and PageR. The guide also contrasts publishing-hosting paths in Flipsnack, Issuu, and Publuu where page viewing and embed outputs shape operational controls.
Tools that generate magazine pages from templates, assets, and structured content rules
Magazine maker software produces multi-page magazine layouts for print or digital viewing by combining templates, page rules, and reusable styling or components. Some tools keep the data model centered on layout objects like masters, paragraph styles, and page templates, which is typical of Affinity Publisher and Adobe InDesign.
Other tools center the data model on structured content entities and schema-driven templates, which is typical of PageR and also appears in Lucidpress through a template and content API. The result is either deterministic page composition with scripting hooks or API-first page provisioning with RBAC and audit logging for governance.
Evaluation criteria for integration, schema control, automation, and governance
Magazine production work fails when the page system cannot map content, styles, and publishing settings into a repeatable schema or automated pipeline. Integration depth matters because asset handling, template updates, and distribution all touch external systems.
Automation and API surface matters because controlled throughput depends on whether multi-step operations can run from configuration and events instead of local editing discipline. Admin governance matters because multi-user production needs RBAC, audit log traceability, and deployment boundaries that match how magazines ship across issues.
Document data model built around masters and style schemas
Affinity Publisher delivers consistent typography at scale with master pages plus paragraph and character styles, which anchors pagination and layout refactors. Microsoft Publisher and Adobe InDesign also use master pages and reusable templates, but Affinity Publisher pairs that control with scripting and repeatable publishing settings for drift reduction.
Schema-driven page provisioning from configuration sets
PageR provisions pages from structured content and layout rules via an API-first workflow, and it ties page builds to environment-specific settings. Lucidpress supports template and content updates from external workflows through a content and template API, which fits when magazine production relies on programmatic layout regeneration.
Automation surface that supports batch edits and repeatable publishing runs
Adobe InDesign supports scripting for style application, content placement, and batch document processing, which enables deterministic revisions at scale. QuarkXPress uses XTensions as a workflow extension framework for custom import, export, and workflow actions, which supports repeatable publishing steps when throughput is controlled.
API and extensibility breadth beyond file-level interchange
Lucidpress emphasizes a template and content API for updating multi-page layouts from external workflows rather than relying only on file interchange. QuarkXPress remains more plugin-focused through XTensions, and Affinity Publisher scripting stays narrower than platforms built around platform-wide content models.
Governance controls with RBAC and audit log traceability
PageR provides RBAC that restricts authoring versus publishing operations and includes an audit log for traceability of page and configuration changes. Lucidpress includes audit and activity history for administrative changes, while Affinity Publisher and Adobe InDesign lack documented multi-user RBAC and built-in audit log coverage for collaborative production.
Integration depth for asset ecosystems and downstream distribution
Canva uses Brand Kit and reusable brand assets to enforce consistent typography, colors, and logos, and it integrates through supported media libraries and publishing exports. Flipsnack, Issuu, and Publuu center integration on embed and share outputs, which makes distribution predictable but limits per-element schema governance.
Pick the magazine maker by matching the pipeline model to governance needs
Start by identifying whether magazine production needs layout determinism inside a page editor or page generation from a schema and configuration sets. Affinity Publisher and Adobe InDesign fit teams that require master pages and paragraph styles with scripting-driven batch edits.
Then map where controls must live. PageR and Lucidpress provide schema-level provisioning and traceability for multi-user operations, while Flipsnack, Issuu, and Publuu optimize for publish and embed workflows with governance tied to workspace and account roles rather than fine-grained authoring objects.
Define the center of gravity for the data model
If the magazine process is anchored in masters, paragraph styles, and consistent page grids, Affinity Publisher and Microsoft Publisher match the document-centric model. If the process is anchored in structured content entities and layout rules that must render consistently across environments, PageR and Lucidpress match schema-driven or API-fed production.
Verify the automation approach matches the batch workload
For deterministic batch revisions, Adobe InDesign scripting supports repeatable operations like style application and content placement across documents. For custom import and export steps embedded inside authoring workflows, QuarkXPress XTensions supports workflow actions that can raise throughput for controlled production runs.
Assess the API and extensibility surface for external orchestration
When external systems must update templates and content programmatically, Lucidpress offers a template and content API that supports updates from outside workflows. When the workflow must begin with API-based page provisioning, PageR aligns with schema-backed templates and configuration sets.
Confirm governance requirements before adopting a workflow
If authoring and publishing roles must be enforced with traceability, PageR provides RBAC and an audit log for page and configuration changes. If the requirement is administrative change history and template governance around a template-content API, Lucidpress includes audit and activity history for administrative changes, while Affinity Publisher and Adobe InDesign lack documented RBAC and built-in audit log coverage for collaborative production.
Choose the distribution model that fits how issues ship
If issues must publish as embed-ready interactive pages, Flipsnack focuses on interactive flipbook publishing with embed and share outputs. If the team needs hosting plus consistent viewer navigation, Issuu centers on document-to-page viewer conversion, while Publuu emphasizes interactive pages with web-ready viewing and embed outputs per issue.
Which teams benefit from these magazine maker software architectures
Magazine maker software selection depends on whether the workflow is primarily layout authoring, API-driven provisioning, or hosted interactive distribution. The right match changes how governance is implemented and where automation must connect.
The segments below map directly to each tool’s best-fit scenario and highlight the controls that tend to matter most in real magazine operations.
Design-led magazine teams prioritizing master pages and style consistency
Affinity Publisher fits when magazine teams need master pages plus paragraph and character styles that keep typography consistent across large multi-page spreads. Microsoft Publisher also supports master pages and templates for long issues, but it lacks a documented automation and API surface.
Production teams that need deterministic batch edits via scripting
Adobe InDesign fits when repeatable production depends on scripting hooks for style application and batch document processing. QuarkXPress also fits when repeatability depends on structured templates and XTensions workflow actions for import and export.
Editorial operations that require schema-driven page generation with RBAC and audit logs
PageR fits when editorial teams need API-based page provisioning from schema-backed templates and configuration sets. Lucidpress fits when teams need governed templates and programmatic updates via a template and content API with audit and activity history for administrative changes.
Editorial brands managing consistency through Brand Kit and controlled templates
Canva fits when editorial teams need Brand Kit and reusable brand assets that enforce consistent typography, colors, and logos across editions. Canva also supports automation and publishing actions, but pagination logic may require manual layout adjustments.
Teams focusing on interactive publishing, embed outputs, and hosted viewing
Flipsnack fits when repeatable interactive magazine publishing relies on embed-ready outputs and template-driven page rendering from assets. Issuu and Publuu also focus on document-to-page viewer conversion and web-ready viewing with embedded navigation settings, which shifts governance toward workspace and published assets.
Pitfalls that break magazine production pipelines
Several failures show up repeatedly when tools are chosen for layout output rather than for integration, schema control, or governance behavior. These pitfalls can lead to manual drift, brittle automation, and weak change traceability.
The fixes below name the specific tools that avoid each failure mode and the controls that must be validated before production begins.
Choosing an editor-first tool without governance-grade RBAC and audit logs
Affinity Publisher and Adobe InDesign support master pages and scripting, but they lack documented RBAC controls and built-in audit logs for multi-user production. PageR avoids this gap with RBAC and an audit log for page and configuration changes, and Lucidpress provides audit and activity history for administrative changes.
Expecting schema-driven provisioning from tools that center layout interchange
Flipsnack, Issuu, and Publuu center on published assets and embed-ready outputs, which limits per-element schema governance. PageR and Lucidpress align better because they tie layouts to a template-content API or schema-backed configuration sets for consistent page generation.
Treating pagination consistency as a purely visual exercise
Canva can require manual pagination adjustments when magazine pagination logic diverges from templates. Affinity Publisher reduces drift by coupling master pages with paragraph and character styles, and QuarkXPress reduces variation with style and layout rules for reprints.
Assuming extensibility will work as configuration-only integration
QuarkXPress XTensions provides workflow extension via plugins, and it requires plugin development rather than configuration-only control for advanced integration. Lucidpress and PageR align better when automation must run through documented API and configuration primitives.
Designing an automation pipeline that depends on local workflow discipline
Affinity Publisher automation relies more on scripting and file-based workflows than on centralized governance and schema-driven rule engines. PageR and Lucidpress support external orchestration with API-based provisioning and template-content updates that can keep changes traceable across builds.
How We Selected and Ranked These Tools
We evaluated each magazine maker across features, ease of use, and value, then computed an overall rating as a weighted average where features carry the most weight at 40% while ease of use and value each account for 30%. Features had the largest impact because magazine workflows fail when style control, templates, automation, or schema governance do not match the production pipeline. We used only the provided review records and their named capabilities, such as Affinity Publisher master pages with paragraph and character styles and PageR API-first provisioning with RBAC and audit logs.
Affinity Publisher separated itself in this scoring because its features profile combined master pages and paragraph plus character styles for consistent magazine spreads with scripting and repeatable publishing settings, which directly lifted the features factor and made it stronger than tools that lack documented RBAC and audit log coverage or that rely more heavily on manual workflow discipline.
Frequently Asked Questions About Magazine Maker Software
Which magazine maker tools support API-first or schema-driven page generation?
How do the tools differ in integration depth for editorial systems and asset pipelines?
What options exist for SSO, RBAC, and audit logging in magazine production workflows?
Which tools are best when style governance and typography consistency must be deterministic across issues?
What is the most automation-friendly approach for batch updates across many pages or documents?
How does data migration work when moving content from a CMS or spreadsheets into magazine layouts?
Which tools support granular admin controls for editorial teams versus authoring-only governance?
When extensibility is required for custom workflow actions, which platforms offer the most direct hooks?
Why do some tools struggle with automation when the magazine data model must be strictly controlled?
Conclusion
After evaluating 10 art design, Affinity Publisher stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Art Design alternatives
See side-by-side comparisons of art design tools and pick the right one for your stack.
Compare art design tools→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.