postnhost 0.1.0 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f12e20da143bbf828f95af42951dcfc1bbce4e9152dd47630ea8a668b73b8a6b
-  data.tar.gz: 8ae19423f07e68ec8fef6ba7a4014751b25b658e218a939bf802157247b96c05
+  metadata.gz: 627ae55fdce85eb1586f9dd686b9b637a83443c5b3752bb9b932f563d972cc72
+  data.tar.gz: 29b259e49deacd46af93786df0bb5ee347a91ebc5ec8902d1b56cceb16c0a7d7
 SHA512:
-  metadata.gz: c40643ed0fd03ec5bc35a717c08a50a7942f9b64df50e397ab4de7217a46090c60d3ae2f25684fb8c5629bb264a1fb4ca87ab6119a819512db90eb84d0f6b2ff
-  data.tar.gz: af8cd76fde91eaad7ac5c175721ca1b7b5a26a80caad882fcfe404ce5bd486252a57dd3681ed108fa51d90d8c500c969e05863b234c4034804502937971186db
+  metadata.gz: e163ba13b11fed2c1840ccedb5d48523f89ea9039f5bf3b2d9fccc3ca02f2c2d82ed1d25133d08b6c5a0856ad3ff1df4b8ef0ba168603d3c9600862317a15ad3
+  data.tar.gz: f85efaf4ef237bb6119101c673ef8f57f1623f79e94fd488637590342b58b2c8c994d8189436f41bb8a7be9e41d068d069cd6e5a683e9f005dc83d6e0f60af03

data/CHANGELOG.md

@@ -2,6 +2,40 @@
 
 All notable changes to PostnHost are documented in this file.
 
+## [0.2.0] - 2026-10-24
+
+### Added
+
+- Versioned JSON management API and Streamable HTTP MCP endpoint at `/api/v1/mcp`, relative to the engine mount path.
+- 89 shared commands for CMS content, publishing, versions, uploads, translations, users, navigation, and settings, with command discovery and OpenAPI schemas.
+- API & MCP dashboard for creating and revoking personal bearer tokens, with hashed token storage and one-time secret display.
+
+### Improved
+
+- Paginated management lists use compact summaries and bounded database queries; full content remains available through individual record commands.
+- UI and management commands share translation enqueueing, preserving successfully queued work and cleaning up placeholders when enqueueing fails.
+
+### Upgrading existing blogs
+
+From your host application's directory, update any Gemfile constraint to allow PostnHost 0.2.0, then run:
+
+```bash
+bundle update postnhost
+bin/rails postnhost:install:migrations
+bin/rails db:migrate
+```
+
+Commit the copied `db/migrate/*_create_api_tokens.postnhost.rb` migration and updated schema with your application. During production deployment, run `RAILS_ENV=production bin/rails db:migrate` before restarting the app.
+
+The new `CreateApiTokens` migration creates the `postnhost_api_tokens` table. Existing blog content requires no backfill.
+
+## [0.1.1] - 2026-08-31
+
+### Fixed
+
+- Scoped packaged and host-generated CSS to PostnHost layouts and replaced competing stylesheets with one combined host build that transparently shadows the packaged logical asset.
+- Corrected installer, template customization, Tailwind setup, and production checklist instructions.
+
 ## [0.1.0] - 2026-08-29
 
 First open source release of PostnHost.
@@ -22,4 +56,6 @@ First open source release of PostnHost.
 
 Authored by Kirill Shevchenko (Ruby/Rails engineering) and Maxim Sova (technical SEO expertise).
 
+[0.2.0]: https://github.com/postnhost/postnhost/compare/v0.1.1...v0.2.0
+[0.1.1]: https://github.com/postnhost/postnhost/compare/v0.1.0...v0.1.1
 [0.1.0]: https://github.com/postnhost/postnhost/releases/tag/v0.1.0

data/README.md

@@ -42,8 +42,9 @@ Mount this engine into an existing Rails app, or use the <a href="https://github
   - [Replacing favicon](#replacing-favicon)
   - [Host app i18n](#host-app-i18n-optional)
   - [Static pages](#static-pages-terms-privacy-etc)
+- [API and MCP](#api-and-mcp)
 - [Routes](#routes)
-- [Manual configuration](#manual-configuration)
+  - [Production checklist](#production-checklist)
 - [Development](#development)
 - [License](#license)
 
@@ -194,7 +195,6 @@ bin/dev
 
 This generator creates:
 
-- `postnhost.tailwind.config.js`
 - `app/assets/stylesheets/postnhost/host.tailwind.css`
 - `Procfile.dev` watcher entry:
   - `postnhost_css: bundle exec rails postnhost:tailwindcss:watch`
@@ -202,8 +202,9 @@ This generator creates:
   - `postnhost:tailwindcss`
   - `postnhost:tailwindcss:watch`
 
-When host-tailwind mode files are present, PostnHost layouts automatically include `postnhost/host.css` after `postnhost/application.css`.
-You do not need to edit layout tags.
+Host-tailwind mode builds one combined stylesheet from the engine and host view sources at `app/assets/builds/postnhost/application.css`. That host-owned file transparently overrides the packaged asset with the same logical path; the engine always requests `postnhost/application`. This avoids competing Tailwind builds and lets copied views use ordinary classes such as `bg-red-500` or `md:grid`.
+
+If the host build is absent, Rails uses the packaged engine asset automatically. Both packaged and combined stylesheets are limited to PostnHost layouts through the `data-postnhost` root attribute. You do not need to edit layout tags or prefix Tailwind classes. Host customization requires Tailwind CSS 4.
 
 ### Robots.txt sitemap URL (required)
 
@@ -295,6 +296,16 @@ Link helpers:
 <%= link_to "Terms", postnhost.public_static_page_path(slug: "terms") %>
 ```
 
+## API and MCP
+
+Manage CMS content and settings through the versioned JSON command API and the
+Streamable HTTP MCP endpoint. Open **API & MCP** in the CMS to create or revoke
+bearer tokens. The API and MCP share the same discoverable commands, input schemas,
+and publishing workflows.
+
+Discover commands at `/api/v1/commands`, OpenAPI at `/api/v1/openapi`, and
+connect MCP clients to `/api/v1/mcp`, relative to the engine mount path.
+
 ## Routes
 
 The engine mounts at `/blog` by default. You can change this in `config/routes.rb`:
@@ -319,13 +330,15 @@ mount Postnhost::Engine, at: "/blog"
 - `GET /sitemap.xml` - XML sitemap
 - `GET /sitemap.xsl` - Sitemap stylesheet
 
-## Manual configuration
+## Production checklist
 
-Some parts must still be configured manually in code:
+Review these host-application settings before deployment:
 
-- Favicons
-- Robots.txt
-- Error pages 404/500 etc.
+- Replace the host app’s favicon and related icon files if needed.
+- Update `public/robots.txt` so its sitemap URL matches the production domain and engine mount path.
+- Review the host app’s static `public/404.html` and `public/500.html` pages.
+- Configure the generated CarrierWave initializer for S3-compatible production storage, or replace it with another storage configuration.
+- If you customize the public templates, copy the required views and enable host Tailwind support when your changes introduce new utility classes.
 
 ## Development
 

data/Rakefile

@@ -2,6 +2,34 @@ require "bundler/setup"
 require "fileutils"
 
 require "bundler/gem_tasks"
+require_relative "lib/postnhost/css_build"
+
+css_build = lambda do |watch:|
+  root = __dir__
+  unscoped_path = File.join(root, "app/assets/builds/postnhost/application.unscoped.css")
+  output_path = File.join(root, "app/assets/builds/postnhost/application.css")
+  command = [
+    File.join(root, "node_modules/.bin/tailwindcss"),
+    "-i", File.join(root, "app/assets/stylesheets/application.tailwind.css"),
+    "-o", unscoped_path,
+    "--minify"
+  ]
+  command << "--watch" if watch
+
+  Postnhost::CssBuild.run(command:, unscoped_path:, output_path:, watch:)
+end
+
+namespace :css do
+  desc "Build the engine stylesheet"
+  task build: :environment do
+    css_build.call(watch: false)
+  end
+
+  desc "Build the engine stylesheet and watch for changes"
+  task watch: :environment do
+    css_build.call(watch: true)
+  end
+end
 
 # Load dummy app so the Rails `environment` task exists (required by prepare_test_db).
 require_relative "spec/dummy/config/application"