create-nextly-app 0.0.2-alpha.4 → 0.0.2-alpha.41

package/templates/blank/src/access/README.md

@@ -1,22 +0,0 @@
-# Access
-
-Access-control functions used by `defineCollection({ access: ... })`
-and `defineSingle({ access: ... })`. Each function decides whether the
-current user can perform an action (read, create, update, delete) on a
-collection or single.
-
-Conventions:
-
-- One function per file. File name matches the function name.
-- Export the function as a named export.
-- Type signature: `AccessControlFunction` from `nextly`.
-
-Common patterns shipped in the blog template (for reference):
-
-- `anyone.ts` — always allow (use for public reads).
-- `authenticated.ts` — require any logged-in user.
-- `is-admin.ts` — require the `admin` role.
-- `is-author-or-editor.ts` — require one of several roles.
-
-Add your own here as your project grows. Wire them up in your
-collections / singles config.

package/templates/blank/src/collections/README.md

@@ -1,22 +0,0 @@
-# Collections
-
-Code-first collections. Each collection is defined via
-`defineCollection({ ... })` from `nextly/config` and wired into the
-root `nextly.config.ts` as part of the `collections: [...]` array.
-
-Conventions:
-
-- Trivial collections (a few scalar fields, no hooks): single file
-  named after the collection (e.g. `Categories.ts`).
-- Complex collections (many fields, hooks, or per-collection helpers):
-  folder named after the collection, with `index.ts` exporting the
-  collection definition and a `hooks/` subdir for hooks specific to
-  that collection (e.g. `Posts/index.ts` + `Posts/hooks/`).
-- Imports inside collection files use relative paths (`../access/...`)
-  rather than the `@/` alias because `nextly.config.ts` is loaded by
-  the CLI through plain Node.js module resolution, which does not
-  honour TypeScript path aliases.
-
-Skip this folder if you're using the Visual Schema Builder (admin UI)
-to manage your schemas — UI-built collections live in the database, not
-on disk.

package/templates/blank/src/lib/README.md

@@ -1,15 +0,0 @@
-# Lib
-
-Project-wide helpers and utilities. Add files here for things that get
-imported across multiple components or routes.
-
-Examples (from the blog template, for inspiration):
-
-- `format-date.ts` — locale-aware date formatting.
-- `site-url.ts` — resolves canonical URLs for OG / sitemap.
-- `queries/` — cached Direct-API wrappers (e.g. `getPostBySlug`).
-- `rss.ts` — RSS feed builder.
-
-Use the `@/` path alias (`import { ... } from "@/lib/foo"`) inside
-your `src/app/`, `src/components/`, etc. Do not use the alias inside
-`nextly.config.ts` or files transitively loaded by it.

package/templates/blank/src/singles/README.md

@@ -1,19 +0,0 @@
-# Singles
-
-Code-first singles (formerly "globals"). Each single is defined via
-`defineSingle({ ... })` from `nextly/config` and wired into the root
-`nextly.config.ts` as part of the `singles: [...]` array.
-
-A single is a one-of content record — Site Settings, Homepage layout,
-Footer config, etc. Use Singles when there is exactly one record of a
-given type, and use Collections when the type has many records.
-
-Conventions:
-
-- One file or folder per single. Folder if the single has hooks or
-  helpers; flat file if it's a small scalar definition.
-- Imports inside single files use relative paths (`../access/...`)
-  rather than the `@/` alias because `nextly.config.ts` is loaded by
-  the CLI through plain Node.js module resolution.
-
-Skip this folder if you're using the Visual Schema Builder.