Merge pull request #66 from cardano-foundation/staging

blog/2024-05-18-media-governance-workshop-san-diego/index.md

@@ -0,0 +1,14 @@
+---
+slug: 2024-05-18-media-governance-workshop-san-diego
+title: Governance Workshop San Diego with Adam Dean
+authors: [community]
+tags: [media, governance]
+---
+
+Video of the Governance Workshop held in San Diego, focusing on best practices and strategies for effective governance in organizations. Key topics include the importance of transparency, stakeholder engagement, and the implementation of robust governance frameworks. The workshop also covers case studies and real-world examples to illustrate successful governance practices. The session aims to provide actionable insights for enhancing governance in various organizational contexts.
+
+<div style={{ textAlign: 'right' }}>
+[**Watch now**](https://www.youtube.com/watch?v=-DGqW0KN0Bg)
+</div>
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/-DGqW0KN0Bg?si=yrJYjW-ydNGne1Zn" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

blog/2024-05-23-research-paper-utxo-based-coin-select/index.md

@@ -0,0 +1,15 @@
+---
+slug: 2024-05-23-research-paper-utxo-based-coin-select
+title: "Research on MACS Algorithm Enhancing UTxO Coin Selection"
+authors: [cf]
+tags: [research]
+---
+
+The Cardano Foundation emphasizes innovation and research in blockchain technology. Their research paper, “MACS: A Multi-Asset Coin Selection Algorithm for UTxO-based Blockchains,” presented at the 2023 IEEE International Conference on Blockchain, highlights the benefits of the MACS algorithm. MACS optimizes transaction fees, UTxO pool size, and user privacy, improving UTxO-based blockchains. Though tested in simulations, it shows promise for enhancing cost, speed, and privacy in blockchain transactions, with further real-world testing needed.
+
+<div style={{ textAlign: 'right' }}>
+ [**Read more**](https://cardanofoundation.org/blog/MACS-a-new-approach-to-multi-asset-coin-selection) 
+ </div>
+
+ ![banner](./image.avif)
+

blog/2024-05-27-community-digest/index.md

@@ -0,0 +1,15 @@
+---
+slug: 2024-05-27-community-digest
+title: "Community Digest"
+authors: [cf]
+tags: [community digest, governance]
+---
+
+On May 23, 2024, Cardano’s SanchoNet achieved a historic milestone by initiating its first hard fork using CIP-1694 governance. Intersect seeks community input for drafting the Cardano Constitution with workshops worldwide. The Cardano Foundation introduced the MACS algorithm for efficient coin selection on UTxO blockchains at the IEEE conference. Other news includes updates from Dr. Lars Brünjes, CNTools, RealFi, leaderlogs, Catalyst Working Group, and SanchoNet.
+
+<div style={{ textAlign: 'right' }}>
+ [**Read more**](https://forum.cardano.org/t/digest-may-27-2024-another-milestone-on-sanchonet-intersect-seeking-community-input-for-drafting-cardano-constitution-cardano-foundation-introduces-a-new-algorithm-for-efficient-coin-selection-on-utxo-blockchains/132175) 
+</div>
+
+ ![community digest](./community-digest.png)
+

blog/2024-05-28-governance-takes-another-step-forward/index.md

@@ -0,0 +1,15 @@
+---
+slug: 2024-05-28-governance-takes-another-step-forward
+title: "Community-led governance takes another step forward"
+authors: [intersect]
+tags: [governance]
+---
+
+Cardano’s minimum viable on-chain governance framework outlines the transition towards on-chain governance, starting with an interim period for bootstrapping via formal rules. Key dates for community involvement include May 28 for registration opening, June 10 for closing, and June 13-23 for voting. An interim Constitutional Committee of seven members, including three elected community members, will oversee the initial phase. Community members passionate about governance are encouraged to apply.
+
+<div style={{ textAlign: 'right' }}>
+ [**Read more**](https://www.intersectmbo.org/news/community-led-governance-takes-another-step) 
+ </div>
+
+ ![banner](./banner.webp)
+

blog/authors.yml

@@ -38,6 +38,11 @@ devportal:
   url: https://developers.cardano.org
   image_url: /img/authors/devportal.svg
 
+community:
+  name: Cardano Community
+  url: https://www.youtube.com/c/CardanoCommunity
+  image_url: /img/authors/cardano-community.jpg
+
 
 # note: don't use relative links here, as this data is built into different paths
 #       for example /news/tags/developers vs /news

docs/components/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "Components",
+  "position": 3,
+  "link": {
+    "type": "generated-index",
+    "description": "Get to know the components with which you can create pages."
+  }
+}

docs/components/background-wrapper.md

@@ -0,0 +1,119 @@
+import BackgroundWrapper from "@site/src/components/Layout/BackgroundWrapper";
+
+# Background Wrapper
+
+[`<BackgroundWrapper>`](/docs/components/background-wrapper) applies a selectable background style to its child components. 
+
+:::info
+
+Most of the time you do not want to put a [`<BackgroundWrapper>`](/docs/components/background-wrapper) inside a [`<BoundaryBox>`](/docs/components/boundary-box) because it would add a margin around it. However, it is common to place a [`<BoundaryBox>`](/docs/components/boundary-box) inside a [`<BackgroundWrapper>`](/docs/components/background-wrapper).
+
+:::
+
+## Background Styles
+
+You can select between different background types by passing the backgroundType to the component. 
+
+### Solid Grey
+```
+<BackgroundWrapper backgroundType="solidGrey">
+```
+
+#### Result
+<BackgroundWrapper backgroundType="solidGrey">
+  This is how<br />
+  the selected<br />
+  background style<br />
+  looks like.
+</BackgroundWrapper>
+
+### Solid Blue
+```
+<BackgroundWrapper backgroundType="solidBlue">
+```
+
+#### Result
+<BackgroundWrapper backgroundType="solidBlue">
+  This is how<br />
+  the selected<br />
+  background style<br />
+  looks like.
+</BackgroundWrapper>
+
+### Zoom
+```
+<BackgroundWrapper backgroundType="zoom">
+```
+
+#### Result
+<BackgroundWrapper backgroundType="zoom">
+  This is how<br />
+  the selected<br />
+  background style<br />
+  looks like.<br />
+  <br />
+  This needs<br />
+  more space<br />
+  to breathe.<br />
+  <br />
+  Way more.  
+</BackgroundWrapper>
+
+### gradientLight
+```
+<BackgroundWrapper backgroundType="gradientLight">
+```
+
+#### Result
+<BackgroundWrapper backgroundType="gradientLight">
+  This is how<br />
+  the selected<br />
+  background style<br />
+  looks like.
+</BackgroundWrapper>
+
+### gradientDark
+```
+<BackgroundWrapper backgroundType="gradientDark">
+```
+
+#### Result
+<BackgroundWrapper backgroundType="gradientDark">
+  This is how<br />
+  the selected<br />
+  background style<br />
+  looks like.
+</BackgroundWrapper>
+
+### ada
+```
+<BackgroundWrapper backgroundType="ada">
+```
+
+#### Result
+<BackgroundWrapper backgroundType="ada">
+  This is how<br />
+  the selected<br />
+  background style<br />
+  looks like.<br />
+  <br />
+  This needs<br />
+  more space<br />
+  to breathe.<br />
+  <br />
+  Way more. 
+</BackgroundWrapper>
+
+### none (default)
+<BackgroundWrapper>
+  This is how<br />
+  the selected<br />
+  background style<br />
+  looks like.
+</BackgroundWrapper>
+
+ :::info
+
+For the sake of simplicity, no other elements were used here as children of [`<BackgroundWrapper>`](/docs/components/background-wrapper). Get to know the [`<BoundaryBox>`](/docs/components/boundary-box) with which you could have made it look even better.
+
+:::

docs/components/boundary-box.md

@@ -0,0 +1,31 @@
+import BoundaryBox from "@site/src/components/Layout/BoundaryBox";
+
+# Boundary Box
+
+
+[`<BoundaryBox>`](/docs/components/boundary-box) ensures consistent boundaries of its children on all screen sizes. 
+
+:::info
+
+Usually you put everything inside a [`<BoundaryBox>`](/docs/components/boundary-box) except a [`<BackgroundWrapper>`](/docs/components/background-wrapper).
+
+:::
+
+## Example
+
+[`<BoundaryBox>`](/docs/components/boundary-box) is just a wrapper component. It is used to wrap other elements or components as shown:
+
+```
+<BoundaryBox>
+  This is how<br />
+  text looks like<br />
+  in a boundary box.
+</BoundaryBox>  
+```
+
+### Result
+<BoundaryBox>
+  This is how<br />
+  text looks like<br />
+  in a boundary box.
+</BoundaryBox>  

docs/components/divider.md

@@ -0,0 +1,87 @@
+import Divider from "@site/src/components/Layout/Divider";
+import BackgroundWrapper from "@site/src/components/Layout/BackgroundWrapper";
+import BoundaryBox from "@site/src/components/Layout/BoundaryBox";
+
+# Divider
+
+
+The [`<Divider>`](/docs/components/divider) component adds a horizontal line with spacing and optional text. You can assign an optional `id` to it for linking to a specific anchor, such as [`#hello`](#hello). It can also be used invisibly, serving solely as an anchor like [`#hidden`](#hidden).
+
+
+
+## Simple Divider
+
+Example of a simple [`<Divider>`](/docs/components/divider) with a text.
+
+```
+<Divider text="Hello World"/>
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do 
+eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim 
+ad minim veniam, quis nostrud exercitation ullamco laboris nisi 
+ut aliquip ex ea commodo consequat.
+```
+
+### Result
+<Divider text="Hello World"/>
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
+
+## Divider with Link
+
+Example of a [`<Divider>`](/docs/components/divider) with a text and the anchor link [`hello`](#hello).  [Try jumping to `#hello` ](#hello).
+
+```
+<Divider text="Hello World" id="hello"/>
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do 
+eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim 
+ad minim veniam, quis nostrud exercitation ullamco laboris nisi 
+ut aliquip ex ea commodo consequat.
+```
+
+### Result
+<Divider text="Hello World" id="hello"/>
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
+
+## Divider without Text
+
+If you use [`<Divider>`](/docs/components/divider) without text it will act as an invisible anchor that you can use to link to positions. [Try jumping to `#hidden` ](#hidden).
+
+```
+<Divider id="hidden" />
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do 
+eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim 
+ad minim veniam, quis nostrud exercitation ullamco laboris nisi 
+ut aliquip ex ea commodo consequat.
+```
+
+### Result
+<Divider id="hidden" />
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do 
+eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim 
+ad minim veniam, quis nostrud exercitation ullamco laboris nisi 
+ut aliquip ex ea commodo consequat.
+
+:::info
+
+Do not set your own #anchor links in `/src/pages/` as you might in plain HTML because they do not work as expected in React due to its handling of routing and navigation. Instead, use the [`<Divider>`](/docs/components/divider) component.
+
+:::
+
+## Divider with Forced White Text
+
+Normally, the [`<Divider>`](/docs/components/divider) component itself takes care of the color of the text depending on dark mode or light mode. However, you may find yourself in a situation where you need to force the color, e.g. if you use [`<Divider>`](/docs/components/divider) within a dark [`<BackgroundWrapper>`](/docs/components/background-wrapper):
+
+```
+<BackgroundWrapper backgroundType="gradientDark">
+  <BoundaryBox>
+    <Divider text="Hello World" id="hello" white= {true}/>
+  </BoundaryBox>
+</BackgroundWrapper>
+```
+
+### Result
+
+<BackgroundWrapper backgroundType="gradientDark">
+  <BoundaryBox>
+    <Divider text="White Divider Text" id="white" white= {true}/>
+  </BoundaryBox>
+</BackgroundWrapper>

docs/components/index.md

@@ -0,0 +1,18 @@
+---
+sidebar_position: 1
+---
+
+# Overview
+
+The component documentation is still being finalized. However, you can find all available components in the `src/components` directory, as shown in the [folder structure](/docs/#folder-structure). To start exploring the components, begin with those in the `src/components/Layout` directory, as these are the ones you will reuse the most.
+
+```sh
+cardano-org
+├── ...
+│   
+├── src
+│   └── components
+│       ├── ...
+│       └── Layout
+└── ...
+```