Merge pull request #12 from VGVentures/fix/asides

fix: no need for component to use an aside

src/content/docs/development/philosophy.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 0
 ---
 
-import { Aside, TabItem, Tabs } from "@astrojs/starlight/components";
+import { TabItem, Tabs } from "@astrojs/starlight/components";
 import Diagram from "~/components/diagram.astro";
 import goodCodeDark from "./diagrams/good_code_dark.png";
 import goodCodeLight from "./diagrams/good_code_light.png";
@@ -118,14 +118,13 @@ mappedStream.listen((value) {
 
 ````
 
-<Aside type="caution">
+:::caution
 We introduce reactive code cautiously, typically only leveraging it at the domain layer to broadcast data changes to view-specific business logic. While reactive code is technically "declarative", it describes how the data is transformed, not necessarily the business logic itself: i.e., it should be the underlying plumbing of the business logic.
 
 Additionally, complex data transformations are known for being difficult to grasp. Because of their tremendous power and flexibility, reactive tools make it easy to accidentally introduce coupling between components in the same architecture layer. In our experience, unintended coupling is by far the most common architectural pain point.
 
 For this reason, we consider reactive programming to be like glue — it's extremely strong, but it's sticky and it gets everywhere if you're not careful.
-
-</Aside>
+:::
 
 ## 💪 Consistency