PHPackages bymayo/curated - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. bymayo/curated ActiveCraft-plugin[Utility & Helpers](/categories/utility) bymayo/curated ============== Manually order related elements per source in Craft CMS. 1.0.1(3w ago)01[1 issues](https://github.com/bymayo/craft-curated/issues)proprietaryPHPPHP >=8.2CI passing Since May 13Pushed 6d agoCompare [ Source](https://github.com/bymayo/craft-curated)[ Packagist](https://packagist.org/packages/bymayo/curated)[ RSS](/packages/bymayo-curated/feed)WikiDiscussions craft-5 Synced 1w ago READMEChangelog (3)Dependencies (2)Versions (3)Used By (0) [![](https://raw.githubusercontent.com/bymayo/craft-curated/craft-5/resources/icon.png)](https://raw.githubusercontent.com/bymayo/craft-curated/craft-5/resources/icon.png) Curated for Craft CMS 5 ======================= [](#curated-for-craft-cms-5) Craft can show you related elements, but can't reorder them when the relation lives on the other side. **Curated fixes that.** The field auto-populates from existing relations — add a Product to your *T-shirts* category and it appears in *T-shirts'* Curated field, ready to drag into place. The same Product can sit at #1 in *T-shirts* and #9 in *Sale*, each category with its own independent order. Works with Entries, Categories, Assets, Users, and (with Craft Commerce) Products and Variants. > ### 🎬 [Watch the video walkthrough →](https://www.youtube.com/watch?v=Vzwgn6WafNg) > > [](#-watch-the-video-walkthrough-) > > See Curated in action in under a few minutes. Perfect for… ------------ [](#perfect-for) - **Categories with products**: reorder products per category, move popular items to the top. - **Editorial / blog landing pages**: "Related articles", "Editor's picks", "More from this author" in a deliberate sequence. - **Image galleries**: order images per Album, lead image first. - **Event lineups**: order speakers per conference, artists per festival, or sessions per day. - **Series and courses**: drag episodes into the right sequence per series, modules per course, or chapters per book. [![](https://raw.githubusercontent.com/bymayo/craft-curated/craft-5/resources/screenshot.png)](https://raw.githubusercontent.com/bymayo/craft-curated/craft-5/resources/screenshot.png) Features -------- [](#features) - **Per-source sort order**: the same Entry can be #1 on one Category page and #9 on another. Same goes for Products in storefront categories, Assets in galleries, or Users on different team pages. - **Auto-populates**: the field fills itself from every native relation between the source and target type, in either direction. No configuration. - **Default Placement**: where auto-discovered relations land before they're explicitly ordered. Before or after other elements, title, date created/updated, random, plus **price** for Commerce Products and Variants. - **Quick reorder actions**: Move to top / bottom / position N inside each item's menu, alongside Craft's Move up / Move down. - **Pin items**: pin items to always lead the list, per source. Survives sorts, drag-reorders, and new auto-discovered relations. - **One-shot Sort by…**: dropdown above the picker for resorting the whole list (title, date, random, price). - **Search**: live filter input above the picker. Hides non-matching items while preserving order, for fields holding hundreds of items. - **Ordering-first by default**: the Add button is hidden; flip **Allow adding elements** on the field to enable curated-only additions. - **Six element types**: Entries, Categories, Assets, Users, Commerce Products and Variants. Narrow by source (Section, Group, Volume, Product Type). - **Native Twig**: `category.curatedProducts.all()` returns a chainable `ElementQuery`. - **GraphQL**: query the field on its host element, with all the usual element arguments (`limit`, `status`, `search`, etc.), and mutate it with a list of IDs in your desired curated order. - **Per-site ordering**: different order per site. - **Element-index column**: each Curated field is a column option on its host element's index. Shows the first curated item with a "+N" overflow for the rest, exactly like Craft's native relation field columns. How Curated compares -------------------- [](#how-curated-compares) Curated is about **ordering**, not establishing or proxying the relation itself. CapabilityCraft's native relation fieldsMany to ManyReverse RelationsCuratedDrag-reorder per source❌ shared sortOrder❌ uses native❌ uses native✅Same target at different positions in different sources❌❌❌✅Show relations created from the *other* side❌✅ one configured field✅ one configured field✅ any field, either directionField's picker writes a native relation✅✅ proxiesvaries❌ ordering onlyPer-site ordering❌inherits nativeinherits native✅Auto-includes new relations created elsewhere❌❌❌✅Quick reorder actions (Move to top / bottom / position)❌❌❌✅Pin / Unpin items to the top of a source❌❌❌✅Inline "Sort by…" reorder (title / date / random / price)❌❌❌✅Default Placement for new relations❌❌❌✅GraphQL support✅❌❌✅**Different jobs.** Many to Many and Reverse Relations *edit the inverse side* of one specific relation field. Curated *orders* whatever's already related (any direction, any field). Install ------- [](#install) ``` composer require bymayo/curated ``` Enable in `Settings > Plugins`, or install via the Plugin Store. Requirements ------------ [](#requirements) - Craft CMS 5.7+ - PHP 8.2+ Setup ----- [](#setup) 1. Create a **Curated** field. Give it a **handle** (e.g. `curatedProducts`), pick the **Element type** (Entry, Category, Asset, User, Commerce Product / Variant), optionally restrict **Sources**, then add it to the field layout of the source element (e.g. a Category). 2. Open the source. The field is pre-populated with every matching element already natively related to it. Drag to reorder; save. 3. Read on the front end via your field handle. The examples below assume the handle is `curatedProducts`: ``` {% for product in category.curatedProducts.all() %} {{ product.title }} {% endfor %} ``` Chain any normal query method: ``` {% set top3 = category.curatedProducts.limit(3).all() %} {% set inStock = category.curatedProducts.status('live').all() %} ``` ### Query from the other side [](#query-from-the-other-side) ``` {% set products = craft.products.curatedBy(category, 'curatedProducts').all() %} ``` The second argument is the handle of the Curated field on the source. Returns empty if the field doesn't exist on that layout. ### GraphQL [](#graphql) Curated fields surface on their host element with the standard element argument set for the target type (`limit`, `offset`, `status`, `search`, `orderBy`, etc.). The resolver returns the saved curated order, then applies any arguments you pass. ``` { category(slug: "t-shirts") { curatedProducts(limit: 12, status: "live") { ... on Product { id title } } } } ``` Mutations accept an array of element IDs in the desired curated order: ``` mutation { save_someSection_someEntryType_Entry( id: 1308 curatedProducts: [1639, 1660, 1657] ) { id } } ``` How Curated works ----------------- [](#how-curated-works) Curated queries every native relation between this source and elements of the target type, in either direction: - Category has an Entries field pointing at entries (source → target), **or** - Entry has a Categories field pointing at the category (target → source). Both surface in the Curated field. The displayed list is `[saved curated order] + [native relations not yet curated]`. **Default Placement** controls where new natives land. ### Sync utility [](#sync-utility) Go to **Utilities → Curated Sync** in the CP and click **Sync now**. You don't need this for Curated fields to work, they populate themselves. Run it when you want to save the current order in one go, for example after importing a batch of entries or migrating content between environments. It's safe to re-run, nothing gets duplicated. ### Console command [](#console-command) ``` php craft curated/sync ``` Same as the Sync utility, just from the terminal. Handy after a deploy, or from a script. Supported element types ----------------------- [](#supported-element-types) Element typeCommon use caseEntry"Related articles", "Editor's picks"CategorySub-categories under a parentAssetGallery / lookbook orderUserFeatured authors, staff orderCommerce ProductDrag products inside a categoryCommerce VariantVariant display orderCraft Commerce is required for Commerce Product and Variant types. Warnings -------- [](#warnings) 1. **Curated sits alongside native relations.** Keep the canonical relation where Craft expects it; use Curated on the source for order. 2. **Removing an item is soft by default.** It drops out of the saved curated order, but reappears at the end on next render because the native relation still exists. To remove for good, also remove the native relation. Or enable the **Fully remove on delete** plugin setting below. 3. **Fully remove on delete (plugin setting) is destructive.** When on, removing an item from a Curated field also deletes every native relation row between the two elements, in both directions, across any relation field. There's no undo. Editors removing items here will silently edit the canonical relation elsewhere in Craft, not just this field. Off by default for a reason. 4. **Curated writes content, not Project Config.** Field settings sync via project config; the curated order itself lives in `curated_relations` and won't sync between environments. 5. **Large lists.** The drag UI is good for hundreds of items, not tens of thousands. See the `max_input_vars` note below if you expect 1000+ items per field. When an element is deleted entirely, it's removed from every curated list automatically. ### `max_input_vars` and big lists [](#max_input_vars-and-big-lists) PHP's `max_input_vars` (default `1000`) caps how many form inputs a request can have. Craft's element picker emits one input per item, so lists over ~1000 items will silently lose items on save unless you raise the limit: ``` max_input_vars = 5000 post_max_size = 16M ``` Support ------- [](#support) If you have any issues then I'll aim to reply as soon as possible. If it's a site-breaking-oh-no-what-has-happened moment, hit me up on the Craft CMS Discord, @bymayo ### Health Score 40 — FairBetter than 86% of packages Maintenance97 Actively maintained with recent releases Popularity2 Limited adoption so far Community6 Small or concentrated contributor base Maturity47 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~0 days Total 2 Last Release 27d ago ### Community Maintainers ![](https://avatars.githubusercontent.com/u/522877?v=4)[Jason Mayo](/maintainers/bymayo)[@bymayo](https://github.com/bymayo) --- Top Contributors [![bymayo](https://avatars.githubusercontent.com/u/522877?v=4)](https://github.com/bymayo "bymayo (41 commits)") --- Tags sortfieldscraftcmscraft-pluginrelationsorderingcurated ### Embed Badge ![Health badge](/badges/bymayo-curated/health.svg) ``` [![Health](https://phpackages.com/badges/bymayo-curated/health.svg)](https://phpackages.com/packages/bymayo-curated) ``` ### Alternatives [verbb/formie The most user-friendly forms plugin for Craft. 100387.6k57](/packages/verbb-formie)[craftcms/feed-me Import content from XML, RSS, CSV or JSON feeds into entries, categories, Craft Commerce products, and more. 294943.4k27](/packages/craftcms-feed-me)[nystudio107/craft-seomatic SEOmatic facilitates modern SEO best practices & implementation for Craft CMS 5. It is a turnkey SEO system that is comprehensive, powerful, and flexible. 1741.5M51](/packages/nystudio107-craft-seomatic)[verbb/navigation Create navigation menus for your site. 92698.4k18](/packages/verbb-navigation)[verbb/workflow Enforce multi-step review processes for creating entries. 138123.0k1](/packages/verbb-workflow)[verbb/comments Add comments to your site. 13753.7k](/packages/verbb-comments) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)