docs tweaks

bridgetownrb · Mar 17, 2024 · c2cc31d · c2cc31d
1 parent b7b59fa
commit c2cc31d
Show file tree

Hide file tree

Showing 5 changed files with 13 additions and 13 deletions.
diff --git a/bridgetown-website/Gemfile.lock b/bridgetown-website/Gemfile.lock
@@ -1,13 +1,13 @@
 PATH
   remote: ../bridgetown-builder
   specs:
-    bridgetown-builder (1.3.2)
-      bridgetown-core (= 1.3.2)
+    bridgetown-builder (1.3.3)
+      bridgetown-core (= 1.3.3)
 
 PATH
   remote: ../bridgetown-core
   specs:
-    bridgetown-core (1.3.2)
+    bridgetown-core (1.3.3)
       activemodel (>= 6.0, < 8.0)
       activesupport (>= 6.0, < 8.0)
       addressable (~> 2.4)
@@ -34,16 +34,16 @@ PATH
 PATH
   remote: ../bridgetown-paginate
   specs:
-    bridgetown-paginate (1.3.2)
-      bridgetown-core (= 1.3.2)
+    bridgetown-paginate (1.3.3)
+      bridgetown-core (= 1.3.3)
 
 PATH
   remote: ../bridgetown
   specs:
-    bridgetown (1.3.2)
-      bridgetown-builder (= 1.3.2)
-      bridgetown-core (= 1.3.2)
-      bridgetown-paginate (= 1.3.2)
+    bridgetown (1.3.3)
+      bridgetown-builder (= 1.3.3)
+      bridgetown-core (= 1.3.3)
+      bridgetown-paginate (= 1.3.3)
 
 GEM
   remote: https://rubygems.org/

diff --git a/bridgetown-website/frontend/styles/syntax.css b/bridgetown-website/frontend/styles/syntax.css
@@ -343,7 +343,7 @@ div.highlighter-rouge {
 
 /* Name.Other */
 .highlight .py {
-  color: #272421;
+  color: #f57900;
 }
 
 /* Name.Property */

diff --git a/bridgetown-website/frontend/styles/theme-dark.css b/bridgetown-website/frontend/styles/theme-dark.css
@@ -114,7 +114,7 @@
     color: var(--color-syntax-light-gray);
   }
 
-  & .highlight :is(.c, .c1, .nx, .nl) {
+  & .highlight :is(.c, .c1, .nx, .nl, .py) {
     color: var(--color-syntax-charcoal);
   }
 

diff --git a/bridgetown-website/src/_docs/content/dsd.md b/bridgetown-website/src/_docs/content/dsd.md
@@ -71,7 +71,7 @@ Oops, this isn't what we want. By simply styling the `header` tag, we've affecte
 
 This is better, but our page layout styles and our "component" styles are still too intermingled. We could remedy this by creating components for things like the article tag, but in more advanced components keeping styles of a component's "internals" and its public-facing child content from colliding with each other can get tricky. And what if you wanted each layout also to have some unique styles but you don't want to add override `<style>` tags or mess around with scoping to body IDs which can land you in specificity wars. Which of these would win?
 
-```style
+```css
 body#fancy-layout article > header {
   font-weight: 600;
 }

diff --git a/bridgetown-website/src/_docs/islands.md b/bridgetown-website/src/_docs/islands.md
@@ -53,7 +53,7 @@ With `<is-land>`, of course!
 
 ## Installing the Island
 
-Bridgetown comes with a [bundled configuration][/docs/bundled-configurations] to set up the `<is-land>` web component, [a tiny package](https://is-land.11ty.dev) which lets you _lazy-load_ islands just as they become visible on-screen or are interacted with (aka clicked).
+Bridgetown comes with a [bundled configuration](/docs/bundled-configurations) to set up the `<is-land>` web component, [a tiny package](https://is-land.11ty.dev) which lets you _lazy-load_ islands just as they become visible on-screen or are interacted with (aka clicked).
 
 Run this command to add it to your main JavaScript bundle: