@refrakt-md/skeleton 0.25.0 → 0.25.1

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/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@refrakt-md/skeleton",
3
3
  "description": "The structural cascade layer + layer-order contract every refrakt theme builds on — ships `@layer skeleton` and the `@layer skeleton, skin;` order declaration, plus the token-name contract",
4
- "version": "0.25.0",
4
+ "version": "0.25.1",
5
5
  "type": "module",
6
6
  "license": "MIT",
7
7
  "repository": {
@@ -29,7 +29,7 @@
29
29
  "styles"
30
30
  ],
31
31
  "dependencies": {
32
- "@refrakt-md/types": "0.25.0"
32
+ "@refrakt-md/types": "0.25.1"
33
33
  },
34
34
  "scripts": {
35
35
  "build": "tsc"
@@ -80,8 +80,17 @@ html:has(.rf-docs-header) { scroll-padding-top: 5rem; }
80
80
  @media (max-width: 768px) {
81
81
  .rf-docs-header { position: sticky; top: 0; }
82
82
  .rf-docs-header__inner p ~ p { display: none; }
83
- .rf-docs-toolbar { display: flex; position: sticky; top: var(--rf-header-height, 3.5rem); z-index: 100; }
84
- /* header height + ~2.75rem toolbar */
85
- .rf-mobile-panel--nav { top: calc(var(--rf-header-height, 3.5rem) + 2.75rem); }
83
+ /* Pin the toolbar to a known height (border-box, so padding + border are
84
+ included) so the docked nav panel can offset against it exactly. A
85
+ content-driven height let the panel's hardcoded guess undershoot the real
86
+ toolbar, and the toolbar's higher z-index then covered the panel's first
87
+ link. */
88
+ .rf-docs-toolbar { display: flex; position: sticky; top: var(--rf-header-height, 3.5rem); z-index: 100; height: var(--rf-docs-toolbar-height, 3.25rem); box-sizing: border-box; }
89
+ /* Two classes (0,2,0) so this beats the base `.rf-mobile-panel { top }` rule
90
+ in mobile.css — both live in @layer skeleton and mobile.css is imported
91
+ later, so an equal-specificity single-class override would lose on source
92
+ order and the panel would dock under the site header (hiding its first
93
+ link behind the toolbar) instead of under the toolbar. */
94
+ .rf-mobile-panel.rf-mobile-panel--nav { top: calc(var(--rf-header-height, 3.5rem) + var(--rf-docs-toolbar-height, 3.25rem)); }
86
95
  .rf-docs-sidebar { display: none; }
87
96
  }
@@ -48,7 +48,10 @@
48
48
  .rf-step h4,
49
49
  .rf-step h5,
50
50
  .rf-step h6,
51
- .rf-step strong {
51
+ /* A leading bold opening the step body acts as its title (list-based steps),
52
+ * so it blocks onto its own line. Scoped to the first inline `strong` of the
53
+ * first paragraph — inline bold elsewhere in the body must stay inline. */
54
+ .rf-step__content > p:first-child > strong:first-child {
52
55
  display: block;
53
56
  }
54
57