@symbiosis-lab/moss-plugin-matters 1.4.2

package/features/sync/article-sync.feature

@@ -0,0 +1,49 @@
+Feature: Article Sync from Matters
+  As a content creator
+  I want to sync my Matters articles locally
+  So that I can edit them offline
+
+  Background:
+    Given a mock Tauri environment
+    And an in-memory filesystem
+
+  Scenario: Sync creates markdown files with frontmatter
+    Given sample articles with titles and content
+    When I sync articles to local files
+    Then markdown files should be created in "article/" folder
+    And each file should have frontmatter with title and date
+    And each file should have the article content as markdown
+
+  Scenario: Sync respects Chinese language preference
+    Given a user with language preference "zh_hant"
+    And sample articles with titles and content
+    When I sync articles to local files
+    Then articles should be in the localized folder
+    And drafts folder should use localized name
+
+  Scenario: Sync skips unchanged articles
+    Given an existing article file with matching date
+    And a remote article with the same date
+    When I sync articles to local files
+    Then the article should be skipped
+    And the result should report 1 skipped
+
+  Scenario: Sync updates newer remote articles
+    Given an existing article file from yesterday
+    And a remote article revised today
+    When I sync articles to local files
+    Then the article should be updated
+    And the result should report 1 updated
+
+  Scenario: Sync creates homepage with user profile
+    Given a user profile with displayName "Test User"
+    When I sync to local files
+    Then index.md should be created at project root
+    And the homepage should have the displayName as title
+
+  Scenario: Sync handles collections in folder mode
+    Given articles that each belong to one collection
+    When I sync to local files
+    Then collection folders should be created
+    And articles should be placed inside their collection folder
+    And collection index.md should be created with title and description

package/features/sync/homepage-grid.feature

@@ -0,0 +1,43 @@
+Feature: Homepage Grid from Pinned Works
+  As a content creator using Matters.town
+  I want my homepage to show pinned works as a grid
+  So that visitors see my featured content prominently
+
+  Background:
+    Given a mock Tauri environment
+    And an in-memory filesystem
+
+  Scenario: Homepage grid from pinned collections
+    Given a user profile with pinned collections "Travel Notes" and "Tech Essays"
+    And no existing homepage
+    When I sync to local files
+    Then index.md should contain ":::grid 3"
+    And index.md should link to each pinned collection
+
+  Scenario: Homepage grid with mixed pinned works
+    Given a user profile with a pinned collection "My Series" and a pinned article "Featured Post"
+    And no existing homepage
+    When I sync to local files
+    Then index.md should contain ":::grid 3"
+    And index.md should link to both the collection and article
+
+  Scenario: No grid when no pinned works
+    Given a user profile with no pinned works
+    And no existing homepage
+    When I sync to local files
+    Then index.md should NOT contain ":::grid"
+    And index.md should contain the user bio
+
+  Scenario: Skip homepage when already exists
+    Given a user profile with pinned collections
+    And an existing homepage with custom content
+    When I sync to local files
+    Then the existing homepage should be preserved
+    And index.md should NOT contain ":::grid"
+
+  Scenario: Collection order in folder mode
+    Given a collection "My Series" with ordered articles "first", "second", "third"
+    When I sync to local files
+    Then the collection index.md should have an order field
+    And the order should list articles as bare slugs
+    And the order should match the Matters API ordering

package/features/sync/incremental-sync.feature

@@ -0,0 +1,28 @@
+@e2e @real-api
+Feature: Incremental Article Sync
+  As a user, I want to sync only articles modified since my last sync
+  So that I save bandwidth and time
+
+  Background:
+    Given I am using the Matters test environment
+    And I have a test user with articles
+
+  Scenario: First sync fetches all articles and saves timestamp
+    Given I have no previous sync timestamp
+    When I run the sync process
+    Then all articles should be fetched
+    And the config should contain a lastSyncedAt timestamp
+
+  Scenario: Subsequent sync only fetches newer articles
+    Given I have a lastSyncedAt timestamp from 1 hour ago
+    And the test user has multiple articles
+    When I run the sync process
+    Then only recently modified articles should be fetched
+    And the lastSyncedAt timestamp should be updated
+
+  Scenario: Sync skips unchanged articles when no modifications
+    Given I have synced all articles recently
+    And no articles have been modified since
+    When I run the sync process again
+    Then 0 articles should be fetched
+    And existing local files should remain unchanged

package/features/syndication/create-draft.feature

@@ -0,0 +1,35 @@
+@e2e @real-api
+Feature: Create Draft on Matters
+  As a user, I want to syndicate my local articles to Matters
+  So that I can publish to both platforms
+
+  Background:
+    Given I am authenticated with the Matters test environment
+
+  Scenario: Create draft via API
+    Given I have an article with title "E2E Test Article"
+    And the article has content and tags
+    When I create a draft on Matters
+    Then a draft should be created with the correct title
+    And the draft should have publishState "unpublished"
+    And I should receive a draft ID
+
+  Scenario: Draft includes canonical link
+    Given I have an article with canonical URL "https://my-site.com/test-article"
+    And add_canonical_link is enabled
+    When I create a draft on Matters
+    Then the draft content should contain the canonical URL
+    And it should be formatted as a link at the end
+
+  Scenario: Fetch draft by ID
+    Given I have created a draft on Matters
+    When I fetch the draft by ID
+    Then I should receive the draft details
+    And the draft should have the correct title
+    And the publishState should be present
+
+  Scenario: Skip already syndicated articles
+    Given I have an article with syndicated URL for Matters
+    When I check if the article should be syndicated
+    Then the article should be skipped
+    And no new draft should be created

package/package.json

@@ -0,0 +1,58 @@
+{
+  "name": "@symbiosis-lab/moss-plugin-matters",
+  "version": "1.4.2",
+  "description": "Syndicate articles between local system and Matters.town",
+  "main": "dist/main.bundle.js",
+  "keywords": [
+    "moss",
+    "plugin",
+    "matters.town",
+    "syndication"
+  ],
+  "author": "Symbiosis Lab",
+  "license": "MIT",
+  "publishConfig": {
+    "access": "public",
+    "registry": "https://registry.npmjs.org/",
+    "provenance": false
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/Symbiosis-Lab/moss-plugins.git",
+    "directory": "matters"
+  },
+  "devDependencies": {
+    "@amiceli/vitest-cucumber": "^5.2.1",
+    "@graphql-codegen/cli": "^6.1.0",
+    "@graphql-codegen/schema-ast": "^5.0.0",
+    "@graphql-codegen/typescript": "^5.0.7",
+    "@graphql-codegen/typescript-operations": "^5.0.7",
+    "@tauri-apps/api": "^2.9.1",
+    "@types/node": "^20.0.0",
+    "@vitest/coverage-v8": "^3.2.4",
+    "chokidar-cli": "^3.0.0",
+    "concurrently": "^8.2.0",
+    "esbuild": "^0.27.0",
+    "ethers": "^6.13.0",
+    "happy-dom": "^20.0.11",
+    "typescript": "^5.3.0",
+    "vitest": "^3.2.4",
+    "@symbiosis-lab/moss-api": "0.10.0"
+  },
+  "scripts": {
+    "build": "npm run clean && npm run bundle && npm run copy-assets",
+    "dev": "npm run clean && npm run copy-assets && concurrently \"esbuild src/main.ts --bundle --format=iife --global-name=MattersPlugin --outfile=dist/main.bundle.js --watch\" \"npm run watch-assets\"",
+    "bundle": "esbuild src/main.ts --bundle --format=iife --global-name=MattersPlugin --outfile=dist/main.bundle.js",
+    "clean": "rm -rf dist && mkdir -p dist",
+    "copy-assets": "cp assets/* dist/",
+    "watch-assets": "chokidar 'assets/**/*' -c 'npm run copy-assets'",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "test:coverage": "vitest run --project unit --coverage",
+    "test:unit": "vitest run --project unit",
+    "test:features": "vitest run --project features",
+    "test:e2e": "vitest run --project e2e",
+    "codegen": "graphql-codegen --config codegen.ts",
+    "codegen:watch": "graphql-codegen --config codegen.ts --watch"
+  }
+}