@spree/docs 0.1.237 → 0.1.239

package/dist/developer/tutorial/admin-api.md

@@ -1,13 +0,0 @@
----
-title: Admin API
-description: Add a ProductFaq endpoint to the Admin API — resource controller conventions, an admin serializer, and a permission catalog entry.
----
-
-Staff manage FAQs through the Admin API — the same API the dashboard, integrations and scripts use. This chapter adds the endpoint following the conventions every Spree resource follows, which is what makes the dashboard plugin in the next chapter nearly free.
-
-## What this chapter covers
-
-- The resource controller: full CRUD from one small controller declaring its model, serializer and permitted attributes
-- The admin serializer and prefixed IDs
-- Registering the resource in the permission catalog so roles and API key scopes cover it
-- Exercising the endpoint with the Admin CLI

package/dist/developer/tutorial/dashboard-plugin.md

@@ -1,14 +0,0 @@
----
-title: Dashboard Plugin
-description: Scaffold a dashboard plugin for ProductFaqs — a table, a form, and navigation, generated by the CLI and wired to the Admin API endpoint.
----
-
-With the Admin API in place, the back-office UI is a dashboard plugin: a table listing FAQs, a form to create and edit them, and a navigation entry — scaffolded by the CLI and customized from there.
-
-## What this chapter covers
-
-- Scaffolding the plugin with the CLI
-- The resource table: columns, search and pagination against the Admin API
-- The form: fields, validation errors mapped from API responses
-- Registering navigation and permissions-aware visibility
-- Running it against your development store

package/dist/developer/tutorial/model.md

@@ -1,13 +0,0 @@
----
-title: Model
-description: Generate the ProductFaq model — migration, associations, validations and store scoping — the foundation both tracks build on.
----
-
-Every feature starts with a model. This chapter generates `ProductFaq` — question, answer, position, attached to a product and scoped to the store.
-
-## What this chapter covers
-
-- Generating the model and migration from the command line
-- Store scoping — why every store-owned record belongs to a store, and what that buys you
-- The association to products, validations, and ordering
-- Running the migration and creating a record in the console

package/dist/developer/tutorial/store-api.md

@@ -1,13 +0,0 @@
----
-title: Store API
-description: Expose FAQs to customers — a read-only Store API endpoint with a serializer that shows only what shoppers should see.
----
-
-Customers read FAQs through the Store API. This chapter adds the customer-facing endpoint — read-only, scoped to the current store, with a serializer deliberately smaller than the admin one.
-
-## What this chapter covers
-
-- The store resource controller: read-only by default, and why
-- The store serializer: public fields only — no timestamps, no internal data
-- Scoping: only FAQs for purchasable products of the current store
-- Nesting under the product endpoint