@se-studio/project-build 1.0.65 → 1.0.66

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/CHANGELOG.md +6 -0
  2. package/package.json +1 -1
  3. package/skills/se-marketing-sites/cms-routes-and-appshared/SKILL.md +1 -1
  4. package/skills/se-marketing-sites/create-page/SKILL.md +2 -0
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @se-studio/project-build
2
2
 
3
+ ## 1.0.66
4
+
5
+ ### Patch Changes
6
+
7
+ - Bulk version bump: patch for all packages
8
+
3
9
  ## 1.0.65
4
10
 
5
11
  ### Patch Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@se-studio/project-build",
3
- "version": "1.0.65",
3
+ "version": "1.0.66",
4
4
  "description": "Build tools and management scripts for SE Studio projects",
5
5
  "repository": {
6
6
  "type": "git",
package/skills/se-marketing-sites/cms-routes-and-appshared/SKILL.md CHANGED
@@ -91,7 +91,7 @@ export default async function (props: PageProps<'/[level1]'>) {
91
91
  }
92
92
  ```
93
93
 
94
- For article routes, use `converterContext.urlCalculators.article`, `articleType`, `articleTypeTag` from `@/lib/cms-server` to compute the path.
94
+ For article routes, use `converterContext.urlCalculators.article`, `articleType`, `articleTypeTag` to compute the path. Import `converterContext` from `@/lib/converter-context` when that module exists (so route files don't pull in cms-server); otherwise from `@/lib/cms-server`.
95
95
 
96
96
  ## See Also
97
97
 
package/skills/se-marketing-sites/create-page/SKILL.md CHANGED
@@ -101,6 +101,8 @@ The appShared modules render content with:
101
101
  - `rendererConfig` – from `@/lib/cms-server`
102
102
  - `pageContext` – provides page/article/customType to child components
103
103
 
104
+ For route files that only need `converterContext` or `buildInformation` (e.g. `generateStaticParams`, sitemap, path computation), import from `@/lib/converter-context` when that module exists, so you don't pull in cms-server.
105
+
104
106
  ## Creating a Specialized Route
105
107
 
106
108
  For a route that behaves differently from standard CMS pages (e.g. search, dashboard):