camox 0.60.2 → 0.62.0
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.
- package/dist/core/createApp.d.ts +8 -8
- package/dist/core/createBlock.d.ts +1 -2
- package/dist/core/createLayout.d.ts +10 -2
- package/dist/core/createLayout.js +1 -3
- package/dist/core/editing/BlockEditingRuntime.d.ts +1 -0
- package/dist/core/editing/CompleteBlockEditingRuntime.js +12 -9
- package/dist/core/editing/createEditableBlock.d.ts +4 -4
- package/dist/core/editing/createEditableBlock.js +19 -25
- package/dist/core/lib/artifactData.js +2 -2
- package/dist/core/lib/contentType.js +5 -4
- package/dist/features/content/CamoxContent.js +40 -32
- package/dist/features/renderer/rendererHost.js +23 -16
- package/dist/features/renderer/studioConnection.js +8 -4
- package/dist/features/sdkBundle/buildSdkBundle.js +0 -1
- package/dist/features/sdkBundle/localSdkBundle.js +2 -2
- package/dist/features/sdkBundle/sdkBundleName.d.ts +0 -1
- package/dist/features/sdkBundle/sdkBundleName.js +0 -1
- package/dist/features/settings/CamoxSettings.js +5 -0
- package/dist/features/settings/ExperimentalFeaturesSettings.js +74 -0
- package/dist/features/settings/useProjectMutation.js +6 -5
- package/dist/features/vite/vite.d.ts +0 -2
- package/dist/features/vite/vite.js +0 -2
- package/dist/lib/queries.js +1 -0
- package/dist/package.js +1 -1
- package/dist/studio.css +1 -1
- package/package.json +4 -4
- package/skills/camox/references/field-styling.md +2 -2
- package/skills/camoxify/SKILL.md +1 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "camox",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.62.0",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"bin": {
|
|
6
6
|
"camox": "./bin/camox.mjs"
|
|
@@ -148,9 +148,9 @@
|
|
|
148
148
|
"unhead": "^3.4.3",
|
|
149
149
|
"yaml": "^2.9.0",
|
|
150
150
|
"zod": "^4.6.7",
|
|
151
|
-
"@camox/
|
|
152
|
-
"@camox/ui": "0.
|
|
153
|
-
"@camox/
|
|
151
|
+
"@camox/api-contract": "0.62.0",
|
|
152
|
+
"@camox/ui": "0.62.0",
|
|
153
|
+
"@camox/cli": "0.62.0"
|
|
154
154
|
},
|
|
155
155
|
"devDependencies": {
|
|
156
156
|
"@earendil-works/pi-ai": "1.3.0",
|
|
@@ -14,7 +14,7 @@ Spread the field's render-prop `props` onto the element to preserve inline editi
|
|
|
14
14
|
<myBlock.Field name="title">{(props) => <h1 {...props} />}</myBlock.Field>
|
|
15
15
|
```
|
|
16
16
|
|
|
17
|
-
Camox owns inline markup so editing and published output have the same appearance. Customize appearance with `textStyle` and `linkStyle` (these replace the old `components` prop). Utilities below, such as `text-
|
|
17
|
+
Camox owns inline markup so editing and published output have the same appearance. Customize appearance with `textStyle` and `linkStyle` (these replace the old `components` prop). Utilities below, such as `text-accent`, are examples; use the ones the project's Theme defines:
|
|
18
18
|
|
|
19
19
|
```tsx
|
|
20
20
|
<myBlock.Field
|
|
@@ -31,7 +31,7 @@ Camox owns inline markup so editing and published output have the same appearanc
|
|
|
31
31
|
};
|
|
32
32
|
}
|
|
33
33
|
return {
|
|
34
|
-
className: bold ? "text-
|
|
34
|
+
className: bold ? "text-accent" : undefined,
|
|
35
35
|
style: bold && italic ? { letterSpacing: "0.02em" } : undefined,
|
|
36
36
|
};
|
|
37
37
|
}}
|
package/skills/camoxify/SKILL.md
CHANGED
|
@@ -39,7 +39,7 @@ Learn the project's **Theme** before styling: read its main stylesheet, the CSS
|
|
|
39
39
|
|
|
40
40
|
Reuse the project's **Components**, such as its button or card, and compose or extend them to match the reference. Build a new Component only when none fits.
|
|
41
41
|
|
|
42
|
-
Style through the Theme's utilities rather than raw colors or stock palette classes, so a rebrand stays one stylesheet edit. To match the reference's colors, fonts and radii, change the Theme's values in the stylesheet
|
|
42
|
+
Style through the Theme's utilities rather than raw colors or stock palette classes, so a rebrand stays one stylesheet edit. To match the reference's colors, fonts and radii, change the Theme's values in the stylesheet: its main color for buttons and links becomes the **Brand Color**, and a second color it uses for emphasis or decoration becomes the **Accent Color**; when the reference needs a role the Theme lacks, add a token there with a comment explaining it.
|
|
43
43
|
|
|
44
44
|
If the reference uses another styling system, recreate its appearance and behavior with the project's Components and Tailwind utilities; do not copy or introduce the reference's styling dependencies.
|
|
45
45
|
|