Skip to content
Skills Library
Programming · Building & coding

pixarts/cms-modules

/pixarts/cms-modules

Pixarts CMS modules pattern - reservations, ecommerce, events, portfolio, newsletter. Use when adding functional modules to Payload CMS tenant, implementing reservations, e-commerce, or event management.

Repository
Synapse ↗
Licence
AGPL-3.0
Last repository change
15.09.2026

Assessment and security

90/ 100Class: good
Format15 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 15.09.2026, without references to retired models or APIs.

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

Pixarts CMS modules pattern - reservations, ecommerce, events, portfolio, newsletter. Use when adding functional modules to Payload CMS tenant, implementing reservations, e-commerce, or event management.

Original author description

Pixarts CMS modules pattern - reservations, ecommerce, events, portfolio, newsletter. Use when adding functional modules to Payload CMS tenant, implementing reservations, e-commerce, or event management.

How it works

  1. Architettura Moduli
  2. Moduli Disponibili
  3. Pattern di Installazione
  4. Access Control Standard per Moduli
Original SKILL.md headings · 171 lines, 678 words
SKILL.md preview
---
name: pixarts/cms-modules
description: Pixarts CMS modules pattern - reservations, ecommerce, events, portfolio, newsletter. Use when adding functional modules to Payload CMS tenant, implementing reservations, e-commerce, or event management.
version: 1.0.0
---

# Pixarts CMS Modules

Pattern per aggiungere moduli funzionali al CMS Payload multi-tenant.

## Architettura Moduli

Ogni modulo è un pacchetto self-contained che aggiunge:
1. **Collections** Payload con access control multi-tenant
2. **Fields** riutilizzabili
3. **Hooks** per side effects (email, revalidation, ecc.)
4. **Frontend components** per rendering

## Moduli Disponibili

### 1. Reservations (Prenotazioni)

**Use case**: Ristoranti, saloni, studi professionali, hotel

**Collections:**

```typescript
// collections/bookings.ts
export const Bookings: CollectionConfig = {
  slug: 'bookings',
  admin: { useAsTitle: 'customerName' },
  fields: [
    tenantField,
    { name: 'customerName', type: 'text', required: true },
    { name: 'customerEmail', type: 'email', required: true },
    { name: 'customerPhone', type: 'text' },
    { name: 'service', type: 'relationship', relationTo: 'services', required: true },
    { name: 'date', type: 'date', required: true },
    { name: 'timeSlot', type: 'text', required: true },
    { name: 'status', type: 'select', options: ['pending', 'confirmed', 'cancelled', 'completed'], defaultValue: 'pending' },
    { name: 'notes', type: 'textarea' },
  ],
  access: { read: tenantReadAccess, create: () => true, update: tenantWriteAccess },
}

// collections/services.ts
export const Services: CollectionConfig = {
  slug: 'services',
  fields: [
    tenantField,
    { name: 'name', type: 'text', required: true, localized: true },
    { name: 'description', type: 'textarea', localized: true },
    { name: 'duration', type: 'number', required: true }, // minuti
    { name: 'price', type: 'number' },
    { name: 'active', type: 'checkbox', defaultValue: true },
  ],
}

// collections/availability.ts
export const Availability: CollectionConfig = {
  slug: 'availability',
  fields: [
    tenantField,
    { name: 'dayOfWeek', type: 'select', options: ['mon','tue','wed','thu','fri','sat','sun'] },
    { name: 'startTime', type: 'text', required: true }, // "09:00"
    { name: 'endTime', type: 'text', required: true },   // "18:00"
    { name: 'slotDuration', type: 'number', defaultValue: 30 }, // minuti
    { name: 'active', type: 'checkbox', defaultValue: true },
  ],
}
```

### 2. E-commerce

**Use case**: Negozi online, vendita prodotti

**Collections:**
- `products`: name, slug, description, price, compareAtPrice, images, categories, inventory, variants, active
- `orders`: orderNumber, customer (name, email, phone, address), items[], total, status (pending/paid/shipped/delivered/cancelled), paymentMethod
- `customers`: name, email, phone, addresses[], orderHistory

### 3. Events (Eventi)

**Use case**: Teatri, conferenze, corsi, workshop

**Collections:**
- `events`: title, slug, description, date, endDate, location, capacity, price, image, categories, status (draft/published/cancelled)
- `registrations`: event (rel), attendee (name, email, phone), ticketType, quantity, status (pending/confirmed/cancelled), paymentStatus
- `tickets`: event (rel), type (name, price, quantity, description)

### 4. Portfolio

**Use case**: Agenzie, freelancer, studi creativi

**Collections:**
- `projects`: title, slug, client, description, featuredImage, gallery[], technologies[], url, year, featured, order

### 5. FAQ

**Use case**: Qualsiasi sito con domande frequenti

**Collections:**
- `faqs`: question (localized), answer (richText, localized), category (rel), order, active
- `faq-categories`: name (localized), slug, order

### 6. Newsletter

**Use case**: Blog, marketing, e-commerce

**Collections:**
- `subscribers`: email, name, status (active/unsubscribed), source, subscribedAt
- `campaigns`: subject, content, sentAt, status (draft/sent), recipientCount

### 7. Reviews (Recensioni)

**Use case**: E-commerce, ristoranti, servizi

**Collections:**
- `reviews`: author, email, rating (1-5), title, content, product/service (rel), status (pending/approved/rejected), featured

### 8. Jobs (Lavoro)

**Use case**: Aziende che assumono

**Collections:**
- `job-listings`: title, slug, department, location, type (full-time/part-time/contract/remote), description (richText), requirements, salary, active
- `applications`: job (rel), name, email, phone, coverLetter, resume (upload), status (new/reviewed/interviewed/hired/rejected)

### 9. Memberships

**Use case**: Palestre, club, SaaS

**Collections:**
- `plans`: name, slug, description, price, interval (monthly/yearly), features[], active, order
- `subscriptions`: user (rel), plan (rel), status (active/cancelled/expired), startDate, endDate, stripeId

### 10. Affiliates

**Use case**: E-commerce, SaaS

**Collections:**
- `affiliates`: name, email, code, commissionRate, status (active/inactive), totalEarnings
- `referrals`: affiliate (rel), order (rel), commission, status (pending/paid)

---

## Pattern di Installazione

```bash
# Comando
/cms-module <modulo> <tenant-slug>
```

**Workflow:**
1. Crea le collection files in `cms/collections/modules/<modulo>/`
2. Registra le collections in `payload.config.ts`
3. Aggiungi access control multi-tenant
4. Crea hooks per notifiche/revalidation
5. Genera i tipi TypeScript
6. Crea i componenti frontend per il rendering

## Access Control Standard per Moduli

```typescript
// Tutti i moduli usano lo stesso pattern
import { tenantField, tenantReadAccess, tenantWriteAccess } from '../fields/tenant';

// Lettura pubblica (sito frontend)
const publicRead: Access = ({ req }) => {
  // Utenti autenticati: filtro tenant
  if (req.user?.tenant) return { tenant: { equals: req.user.tenant } };
  // Utenti non autenticati: solo dati pubblicati
  return { _status: { equals: 'published' } };
};
```
Files in this package (4)
  • SKILL.md 6 KB
  • learnings.md 1 KB
  • evals/evals.json 1 KB
  • evals/trigger_evals.json 1 KB

Versions

The database has no other skills named pixarts/cms-modules.

Database snapshot: 13.11.2026 · package version 95dde6a803e6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90pixarts/multitenancy
    Payload CMS multi-tenancy guide for Pixarts - tenant structure, access control, collections, hooks. Use when setting up multi-tenant CMS, configuring tenant access control, or implementing tenant-scoped data.
  • 85pixarts/client-site
    Pixarts client site stack - Next.js, Payload CMS, shadcn/ui, i18n, Tailwind. Use when building frontend for Pixarts client projects, setting up standard stack, or implementing multi-tenant architecture.
  • 100payload-cms
    Payload is an open-source, code-first headless CMS and application framework that runs inside a Next.js app, with collections defined in TypeScript. Use this skill when defining collections in TypeScript, configuring access control, customizing the admin panel, or integrating…
  • 95payloadcms
    Operate Payload CMS (Next.js-native headless CMS) in repo workflows: bootstrap a Payload app, configure collections/globals, run local dev + migrations, and ship safe content-model changes. Use when the request mentions Payload CMS, payload config, collection schema, admin…
  • 100payloadcms-ops
    Payload CMS 3 (Next.js-native) architecture - collections, globals, fields, access control, hooks, Local API, storage adapters, and database (Postgres/MongoDB/SQLite). Use for: payload, payloadcms, payload cms, payload 3, collection config, access control, payload hooks, local…
  • 90payload-cms
    Build, extend, deploy and debug websites on Payload CMS (payloadcms.com): collections, blocks and layout builder, live preview, drafts, plugins, Postgres or Mongo, Vercel, migrations, plus cloning or rebuilding an existing site (including payloadcms.com itself) onto Payload. Use…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.