diff --git a/datahub-cloud/Add sidebar navigation.md b/datahub-cloud/Add sidebar navigation.md
new file mode 100644
index 0000000..5b163f7
--- /dev/null
+++ b/datahub-cloud/Add sidebar navigation.md
@@ -0,0 +1,21 @@
+---
+title: "Add sidebar navigation"
+---
+
+
+
A well-structured sidebar can significantly enhance the usability and navigability of your documentation or data site. With Datahub Cloud, you can easily implement sidebar navigation to help users quickly find and access the content they need. This section will guide you through the steps to add and customize a sidebar for your site.
+
+
+## Add sidebar navigation
+
+You can enable the sidebar by adding config.json file in the root of your site's repository (or its subfolder if you're publishing only this subfolder with DH Cloud) with the following content:
+
+```
+{
+ "showSidebar": true
+}
+```
+
+Here's how it should look like:"
+
+![[./assets/Screenshot3.png]]
diff --git a/datahub-cloud/Add visuals and data-rich components.md b/datahub-cloud/Add visuals and data-rich components.md
new file mode 100644
index 0000000..7484750
--- /dev/null
+++ b/datahub-cloud/Add visuals and data-rich components.md
@@ -0,0 +1,618 @@
+---
+title: "Add visuals and data-rich components"
+---
+
+
+
With Datahub Cloud, you can easily add various visual and data-rich components to your datasets or data stories, making them more engaging and insightful. This section will guide you through the process of incorporating charts, graphs, and other visual elements to bring your data to life.
+
+
+> [!info] Github is playing the role of your Editor.
+> Any changes you want to make to your published site, you need to make in your GitHub repository first.
+> Once you hit "sync" on your Site dashboard, the changes get reflected on your published site (unless you turn on the Auto-sync)
+
+You can check the full list and API of the available features here [https://storybook.portaljs.org](https://storybook.portaljs.org)
+
+# Table of Contents
+
+# Inserting a component
+
+1. Select the desired component you want to add from the sidebar list:
+
+![[./assets/Screenshot1.png]]
+
+2. Click on "Docs"
+3. Hit "Show code" at the bottom right of the showcased feature
+
+![[./assets/Screenshot2.png]]
+
+6. Copy-paste the code into your markdown file in your GitHub repository
+7. Commit the changes made
+8. Navigate back to the App and hit "Sync"
+9. Visit your site or refresh the page in order to see the reflected changes
+
+> [!info] To import a feature from URL, simply upload your data file to your Github repository and replace the URL in the copied code. Relative paths are supported.
+> For concrete examples, please continue reading.
+
+## Different ways to insert a component
+
+Depending on the type of feature you selected from the list https://storybook.portaljs.org, you need to copy-paste the code block into your md file and:
+
+1) update the params _(refer to the params in the docs and their description)_ or
+2) update the CSV link with the link of your data file (you can also use a relative path) or
+3) update the URL to one of your own file and
+4) Publish it with Datahub Cloud and share it with the world!
+
+# What features are supported?
+
+You can use several data preview and data visualization components to make your dataset more insightful.
+
+> [!hint]
+> If the feature you need isn't on the list, ping us on [discord](https://discord.gg/KZSf3FG4EZ) or create an issue in the [datahub repository](https://github.com/datopian/datahub/issues) requesting it and we promise to look into it!
+
+## Catalog
+
+If your dataset is part of a larger dataset collection, you may want to start by listing the related datasets here in a catalog-like component with search and facets like this one:
+
+
+
+Simply copy and paste the following code snippet in the markdown file in your Github repository:
+
+```
+
+```
+
+Now update the values to reflect your datasets data (title, path) and the facet values relevant to your data.
+
+## Excel
+
+If you're working a lot with Excel files, you can embed a preview of your file such as this one:
+
+
+
+This component allows you to present all tabs in your Excel file. You can sort the rows by clicking on the Column name and you can also filter each column by clicking on the triple bar symbol next to the Column name.
+
+Simply copy and paste the following code snippet in the markdown file in your Github repository:
+
+```
+
+```
+
+Then upload your Excel file to your Github repository and replace the URL with the URL of the uploaded file (absolute and relative paths are supported).
+
+## Data Table
+
+Let's continue by adding a table of your data like the one below:
+
+
+
+Simply copy and paste the following code snippet in the markdown file in your Github repository:
+
+```
+
+```
+
+ To get this data replaced with your data, upload your csv file to your repository and update the URL
+
+## Iframe
+
+If you're working with Microsoft Power BI reports or Google Lookerstudio or any similar, you can embed them within your page as follows:
+
+
+
+Simply copy and paste the following code snippet in the markdown file in your GitHub repository:
+
+```
+
+```
+
+The only thing you need to do after that is to replace the URL with the correct one.
+
+
+## PdfViewer
+
+You can also embed a view of a PDF file such as this one:
+
+
+
+Simply copy and paste the following code snippet in the markdown file in your Github repository:
+
+```
+
+```
+
+Then update the url to lead to your pdf file.
+
+> [!tip]
+> The easiest way would be to upload it to the Github repository and use the relative/absolute path
+
+## Line and Bar Charts
+
+Here's a quick line chart:
+
+
+
+You can add this line chart component by simply:
+
+1) Uploading your data CSV file to your repository
+2) Copy-pasting the below snippet into the markdown file in your repository
+3) Updating the URL (relative path)
+4) Updating the params (data, title, xAxis, yAxis) to reflect the relevant data
+
+```
+
+```
+
+> [!note]
+> There are also other types of charts and graphs you can use to enhance your dataset. You can create charts with Plotly or VegaLite.
+
+### Plotly charts
+
+> [!info] Bar Chart
+
+You can insert a Plotly Bar Chart like this one:
+
+
+
+Simply copy and paste the following code snippet and update the URL and the title, xAxis, yAxis to reflect your data points:
+
+```
+
+```
+
+
+
+> [!info] Line Chart
+
+Same goes for this Line Chart:
+
+
+
+Copy and paste the following code snippet and update the URL and the title, xAxis, yAxis to reflect your data points:
+
+```
+
+```
+
+### VegaLite Charts
+
+> [!info] VegaLite Charts are also supported
+
+
+
+If you want to add it, copy paste the below snippet and insert it in your markdown file:
+
+```
+
+```
+
+Now update the values to reflect your data points and you're done!
+
+## Map
+
+In case you're dealing with geo data, you can visualize your data on a GeoJSON polygons and points map with auto zoom in the points layer:
+
+
+
+Just copy paste the following snippet and update the values and urls to reflect your data:
+
+```
+
+```
+
+> Make sure to upload your geoJSON file to the Github repository and update the params in the code.
+
diff --git a/datahub-cloud/Auto-Sync of your Site.md b/datahub-cloud/Auto-Sync of your Site.md
new file mode 100644
index 0000000..6edb698
--- /dev/null
+++ b/datahub-cloud/Auto-Sync of your Site.md
@@ -0,0 +1,11 @@
+---
+title: "Auto-Sync of your Site"
+---
+
+# Auto-Sync of your Site
+
+Auto-sync is enabled by default for newly created sites. This means the changes committed to your repository will automatically be reflected on your published site. You can choose to disable that if you want an additional layer of control before the changes get reflected on your published site.
+
+You can easily toggle this option on or off on your site's settings page.
+
+![[./assets/Auto-sync.png]]
diff --git a/datahub-cloud/Configuring Nav bar and SEO fields.md b/datahub-cloud/Configuring Nav bar and SEO fields.md
new file mode 100644
index 0000000..2061487
--- /dev/null
+++ b/datahub-cloud/Configuring Nav bar and SEO fields.md
@@ -0,0 +1,84 @@
+---
+title: How to Configure Basic SEO Fields and Nav Bar in Your DataHub Cloud Sites
+---
+
+You can now personalize your DataHub Cloud site by:
+- setting your own site-wide SEO title and description
+- changing the navbar's logo and title, and adding your own navigation links
+- switching from top navbar to sidebar with all your site's pages.
+
+## Meet `config.json` file
+
+Any site-wide configurations of your DataHub Cloud sites (other than the ones you can find in the dashboard's site settings page) can be applied via root-level `config.json` file. We'll explore each of the available config options below. If you want to follow, first create this file in your site's repo.
+
+> [!tip]
+> You can find a full `config.json` file example in our [template repository](https://github.com/datahubio/datahub-cloud-template/tree/main).
+
+## Improve SEO by Setting Your Site's Title and Description
+
+You can change your site's default SEO title and description by setting the following config fields:
+- `title`: default SEO title for your site (will be used as a fallback value for pages without a title set); **note**: this title will also be used in your site's navbar
+- `description`: default SEO title for your site (will be used as a fallback value for pages without a title set)
+
+For example, putting the following in the `config.json` file:
+
+```json
+{
+ "title": "Joe's Digital Garden",
+ "description": "Welcome to my personal travel blog, where I share my experiences and travel tips."
+}
+```
+
+...will result in the following SEO values (note, that `title` tag's value is set to the actual page title, which takes precedence over the site-wide title):
+
+![[./assets/Pasted image 20240520152158.png]]
+
+... and the following navbar title change:
+![[./assets/Pasted image 20240520152011.png]]
+
+## Changing Navbar's Logo, Title and Links
+
+As you just saw, setting the `title` field in `config.json` already changes/sets the navbar title. But the logo is still the default one. To change it, you can add a local path or an external URL to your logo in the `logo` field, like this:
+
+```json
+{
+ "logo": "logo.jpeg"
+}
+```
+
+Now we have the navbar title and logo changed, but there are still default DataHub links in there. To change those to your custom links you can include `navLinks` field in your `config.json` file, with each link having the following fields:
+- `name`: label of the link
+- `href`: the actual link
+
+For example:
+
+```json
+{
+ "navLinks": [
+ {
+ "href": "/blog",
+ "name": "Blog"
+ },
+ {
+ "href": "/about",
+ "name": "About"
+ },
+ {
+ "href": "https://twitter.com/datopian",
+ "name": "Follow me on twitter!"
+ }
+ ]
+}
+```
+
+![[./assets/Pasted image 20240520155132.png]]
+
+## Conclusion
+
+Congratulations! You've just learned how to configure basic SEO fields and the navigation bar of your DataHub Cloud site using `config.json` file.
+
+---
+
+If you encounter any issues or have questions, the DataHub Cloud community and support team are here to help.
+
+Happy hacking!
diff --git a/datahub-cloud/Create a dataset from scratch and publish it with Datahub Cloud.md b/datahub-cloud/Create a dataset from scratch and publish it with Datahub Cloud.md
new file mode 100644
index 0000000..5834f38
--- /dev/null
+++ b/datahub-cloud/Create a dataset from scratch and publish it with Datahub Cloud.md
@@ -0,0 +1,98 @@
+---
+title: Create a dataset from scratch and publish it with Datahub Cloud
+---
+
+In this tutorial, we're going to learn how to publish a dataset (multiple data files or a single data file) with DataHub Cloud.
+
+As an example we're going to use an example dataset with an analysis of the top 1000 global universities: https://www.kaggle.com/datasets/zahrayazdani81/univercitiesranking?resource=download
+
+## What You'll Need
+
+- GitHub account and basic knowledge of GitHub UI (especially editing and adding files)
+- A [DataHub Cloud](https://datahub.io/) account.
+
+### Step 1: Create a GitHub repository with the data files and `README.md` file
+
+Any DataHub Cloud site is built off of a GitHub repository. This is where you'd put all your dataset file(s) and any related markdown content that you want to publish. For the sake of simplicity, in this tutorial, we're only going to use a single `README.md` file. It's going to serve as a landing page for our site.
+
+> [!tip]
+> Any `README.md` or `index.md` file, either in a root of the repository or in a subfolder, will be treated as a "landing" page (of the whole site or a given folder) by the DataHub Cloud.
+
+Go to your GitHub account and create a new repository. Note, you can check "Add a README file" checkbox. This will make GitHub automatically add an empty `README.md` file to our repository.
+
+![[./assets/Pasted image 20240514091335.png]]
+
+> [!hint]
+> If you're new to GitHub, here are simple instructions on creating a repository: https://docs.github.com/en/repositories/creating-and-managing-repositories/quickstart-for-repositories
+
+Now, let's also add a short introduction about our dataset to the `README.md` file. We'll use the one from the original Kaggle dataset.
+
+![[./assets/Pasted image 20240515003021.png]]
+
+Now we need to add our dataset files to our repository. The universities dataset we're using only has a single `csv` file. Let's download it and upload it to our repository. We're going to name it `data.csv` but you can name it whatever you want.
+
+> [!hint]
+> If you have multiple data files, to keep things tidy, we recommend putting them in a subfolder, e.g. in `/data`.
+
+Here is how your repository should look like at this stage:
+
+![[./assets/Pasted image 20240517225336.png]]
+
+> [!hint]
+> If you're new to GitHub, here are simple instructions on uploading files to a repository: https://docs.github.com/en/repositories/working-with-files/managing-files/adding-a-file-to-a-repository
+
+### Step 2: Create a DataHub Cloud site
+
+We're not done yet, but let's first publish our repository with DataHub Cloud first to see how it works and what our site looks like.
+
+Go to your DataHub Cloud account and click on "Create New Site" button at the top of the screen. Then, select your newly created GitHub repository and submit the form. You should now be redirected to the settings page of your newly created DataHub Cloud site. Click on the "Visit" button to see how your site looks!
+
+![[./assets/Pasted image 20240515003051.png]]
+
+As you can see, there is no mention of your data file. The current landing page only shows our `README.md` page content. Obviously, this requires some more work. We need to describe our dataset for DataHub Cloud, so that it can display information about it to our site's visitors.
+
+### Step 3: Describe your dataset with Frictionless data standard
+
+In DataHub Cloud, we leverage Frictionless [data standard](https://specs.frictionlessdata.io/) for describing datasets.
+
+What is it and how does it fit in DataHub Cloud? In short, it's a standard format for describing and sharing datasets with others. DataHub Cloud understands it, and, by default, will render any `README.md` (or `index.md`) file that has a [Frictionless Data Package spec](https://specs.frictionlessdata.io/data-package/) in a `datapackage` frontmatter field using a special `dataset` layout. This layout combines markdown content from the `README.md` file with metadata from the `datapackage` frontmatter field and displays them in an elegant format.
+
+> [!tip]
+> You can also put your Data Package spec in a file named `datapackage.{json,yaml,yml}` next to your `README.md` (or `index.md`). This is especially useful if your dataset includes lots of files and your Data Package spec starts being really long.
+
+Note, that currently only a subset of Frictionless Data Package fields is displayed by DataHub Cloud's `dataset` layout. You can find the template Data Package with all the currently supported fields in [this template](https://github.com/datahubio/datahub-cloud-template/blob/main/README.md).
+
+In this tutorial we're only going to focus on the most important fields:
+- `title`
+- `description`
+- `resources` (**required**): describes all the data files included in the dataset. It is a list of objects with the following fields:
+ - `name`: unique identifier of the resource
+ - `path`: path to the resource file (relative or absolute path)
+ - (and some more, but your can explore them on your own)
+
+Now, based on the above information, let's create a `datapackage` yaml spec for our universities dataset and put it in the frontmatter of our `README.md` file, like so:
+
+```md
+---
+datapackage:
+ title: Top 1000 universities in the world
+ resources:
+ - name: universities-ranking
+ path: data.csv
+---
+
+...Rest of the README file content...
+```
+
+Now, commit your changes, go to your DataHub Cloud dashboard, and **"Sync" your site**.
+
+> [!note]
+> Note, instead of nesting the datapackage specification in a `datapackage` field, you can just put the whole spec in a separate `datapackage.yaml` (or json) file right next to the README file. Important: In this case you wouldn't nest it in a top level `datapackage` key!
+
+This is what the resulting site looks like:
+
+![[./assets/Pasted image 20240517224144.png]]
+![[./assets/Pasted image 20240515010236.png]]
+![[./assets/Pasted image 20240515010252.png]]
+
+Congratulations! You've just learned how to publish a dataset with DataHub Cloud. As you can see, some of the metadata fields in the layout are currently empty. The more information you provide is obviously the better, so we encourage you to explore the full set of currently supported fields in [our template](https://github.com/datahubio/datahub-cloud-template/tree/main).
diff --git a/datahub-cloud/Customize Your DataHub Cloud Site with CSS.md b/datahub-cloud/Customize Your DataHub Cloud Site with CSS.md
new file mode 100644
index 0000000..eb431c7
--- /dev/null
+++ b/datahub-cloud/Customize Your DataHub Cloud Site with CSS.md
@@ -0,0 +1,226 @@
+---
+title: Customize Your DataHub Cloud Site with CSS
+---
+
+## Introduction
+
+In this tutorial, we're going to explore how you can personalise the appearance of your DataHub Cloud site. By the end of this tutorial, you'll learn how to use a `custom.css` file to adjust existing styles and how to add and style a simple hero to your landing page.
+
+### What You'll Need
+
+- GitHub account and basic knowledge of GitHub UI (especially editing and adding files)
+- A [DataHub Cloud](https://datahub.io/) site you want to customise.
+- Basic knowledge of CSS (or more, depending on what you want to achieve)
+- Basic knowledge of browser developer tools.
+
+## Part 1: Adjusting Default Styles with `custom.css`
+
+Here is an example landing page of a site published with DataHub Cloud that we're going to style. You can use any of your DataHub Cloud sites.
+
+![[./assets/css-tutorial-1.png]]
+
+Here is the underlying markdown content:
+
+```md
+---
+title: My Musings & Memories 🧘♀️🏄♀️🏔️
+description: "Welcome to my personal corner of the web, where I'll be sharing my thoughts, travel experiences, coding projects, and much more!"
+date: 2024-04-24]
+---
+
+## Recent Posts
+
+- [[/life-lessons-learned|Life Lessons Learned]]
+- [[/travel-thailand#Bangkok at Night|Travel to Thailand]]
+- [[/blog/javascript-tips|Let's Talk JavaScript]]
+
+## Featured Content
+
+> [!info] Don't forget to check:
+> [[/blog/chasing-auroras-norway|Chasing Auroras in Norway]]
+
+---
+
+### Photo of the Week
+
+![[auroras.jpeg]]
+
+---
+
+...
+```
+
+### Step 1: Create the `custom.css` File
+
+In the root of your site's GitHub repository, create a file named `custom.css`.
+
+> [!important]
+> If you're site is published from a subfolder of your repository (i.e. you've specified "Root Directory" config field), the `custom.css` file should be placed in that subfolder.
+
+### Step 2: Change Background Colour & Heading Fonts
+
+Now, let's change the background colour and heading fonts a bit.
+
+Add the following CSS rules in your `custom.css` file and commit your changes. Then, go to your DataHub Cloud dashboard and **sync your site**.
+
+```css
+/* Change heading fonts and colors */
+.bg-background {
+ background: #f9f6f1 !important;
+}
+
+h1, h2, h3, h4, h5, h6 {
+ font-family: "Lucida Console", "Courier New", monospace !important;
+ font-weight: bold !important;
+}
+
+h1, h4 {
+ color: #d30c7b !important;
+}
+
+h2, h5 {
+ color: #ba5a31 !important;
+}
+
+h3, h6 {
+ color: #508484 !important;
+}
+```
+
+> [!note]
+> Note, that we needed to override the existing styles with `!important ` rule. This may not be needed each time, but if you're trying to tweak some styles and there is no effect, you may need to use it.
+
+Here is the end result on our example page. Pretty nice, huh?
+
+![[./assets/css-tutorial-2.png]]
+
+### Step 3: Style Anything You Want
+
+This was just a basic example of tweaking css on your DataHub Cloud site. But you can style virtually anything you can see on your page. You just need to find out how to properly "select" the HTML element you want to style in your `custom.css`.
+
+> [!note] Disclaimer
+> This is not a tutorial on CSS and CSS selectors, so you need to do your own research here 😉
+
+## Part 2: Adding a Simple HTML Hero
+
+Did you know that you can include HTML tags in your markdown? If not, let me show you how.
+Then, you'll be able to use the knowledge from Part 1 and style those elements too!
+
+Let's try replacing the current header (title, description, and date) in our example with a simple hero element.
+
+#### Step 1: Add a Simple HTML Hero
+
+Let's replace the current frontmatter with the following HTML snippet:
+
+```html
+
+
My Musings & Memories
🧘♀️🏄♀️🏔️
+
Welcome to my personal corner of the web, where I'll be sharing my thoughts, travel experiences, coding projects, and much more!
+
See my blog
+
+```
+
+The markdown file now looks like this:
+
+```md
+
+
My Musings & Memories 🧘♀️🏄♀️🏔️
+
Welcome to my personal corner of the web, where I'll be sharing my thoughts, travel experiences, coding projects, and much more!
+
See my blog
+
+
+## Recent Posts
+
+- [[/life-lessons-learned|Life Lessons Learned]]
+- [[/travel-thailand#Bangkok at Night|Travel to Thailand]]
+- [[/blog/javascript-tips|Let's Talk JavaScript]]
+
+## Featured Content
+
+> [!info] Don't forget to check:
+> [[/blog/chasing-auroras-norway|Chasing Auroras in Norway]]
+
+---
+
+### Photo of the Week
+
+![[auroras.jpeg]]
+
+---
+```
+
+Now, commit your changes.
+
+### Step 2: Style Your Hero with `custom.css`
+
+Back in your `custom.css` file, add the following styles (or other!) for your custom hero section:
+
+```css
+...
+
+.hero {
+ background-color: #508484;
+ height: 500px;
+ display: flex;
+ flex-direction: column;
+ justify-content: center;
+ align-items: center;
+ text-align: center;
+ color: #fff;
+ padding: 0 36px;
+}
+
+.hero-title {
+ font-size: 4rem;
+ color: #E35AA6 !important;
+ margin-bottom: 0px;
+}
+
+.hero-description {
+ font-size: 1.5rem;
+ margin-bottom: 30px;
+}
+
+.hero-button {
+ background-color: #fff;
+ color: #333;
+ padding: 10px 20px;
+ border-radius: 5px;
+ text-decoration: none;
+ font-weight: bold;
+ transition: all 0.3s ease-in-out;
+}
+
+.hero-button:hover {
+ background-color: #D679AC;
+ color: #fff;
+}
+```
+
+Once again, commit your changes. Now, head to your DataHub Cloud dashboard and **sync your site**. Now you can refresh your browser and you should see your landing page with the styled hero. Our example looks like this:
+
+![[./assets/css-tutorial-3.png]]
+
+You can also add this extra hack to make the hero break out of the parent container and span the whole site width:
+
+```css
+.hero {
+ ...
+ margin: 0 calc(min(28rem - 1.5rem - 50vw, 0px));
+ margin-top: -3rem;
+}
+```
+
+![[./assets/css-tutorial-4.png]]
+
+## Conclusion
+
+Congratulations! You've just learned how to customize the appearance of your DataHub Cloud site using a `custom.css` file for subtle and not-so-subtle tweaks of your sites style. Explore, experiment, and most importantly, have fun designing your site.
+
+---
+
+If you encounter any issues or have questions, the DataHub Cloud community and support team are here to help.
+
+Happy styling!
+
+
diff --git a/datahub-cloud/How to push an Obsidian vault to a Github repository.md b/datahub-cloud/How to push an Obsidian vault to a Github repository.md
new file mode 100644
index 0000000..c0fc51c
--- /dev/null
+++ b/datahub-cloud/How to push an Obsidian vault to a Github repository.md
@@ -0,0 +1,64 @@
+---
+title: How to push an Obsidian vault to a GitHub repository
+---
+
+This howto walks you through the process of setting up your Obsidian vault as a GitHub repository. Here are some of the benefits of doing so:
+
+1. Creating a backup of your notes, accessible from anywhere.
+2. Keeping track of your note-taking history, thereby enabling you to see the evolution of your ideas over time.
+3. Collaborating with others on your notes.
+
+In this howto, we will use the GitHub Desktop application, an easy-to-use interface for managing your Git repositories locally and on GitHub. This tool is particularly useful if you're not comfortable with Git's command line interface or if you just prefer a more visual representation of your Git operations.
+
+## Steps
+
+### Step 1: Setting Up GitHub Desktop App
+
+1.1. If you haven't already done so, create a GitHub account at https://github.com
+
+1.2. Download and install the GitHub Desktop app from https://desktop.github.com
+
+1.3. Once installed, open the GitHub Desktop app. You'll be prompted to sign in with your GitHub account.
+
+### Step 2: Setting Up Your Vault as a GitHub Repository
+
+2.1. In the GitHub Desktop app, click on "Add an Existing Repository from your Hard Drive"
+
+2.2. Navigate to your Obsidian vault's folder using the file explorer.
+
+2.3. After selecting it, you'll see a warning saying "This directory does not appear to be a Git repository. Would you like to create a repository here instead?" Click on the link "create a repository".
+
+2.4. You'll be brought to the "Create a New Repository" page with the vault's location already in the "Local Path" box.
+
+2.5. Choose a name for your repository. It's best to use lowercase and dashes. (For the sake of simplicity use the same or similar name to your vault's folder name.)
+
+2.6. Add an optional description.
+
+2.7. Make sure the checkbox "Initialise this repository with a README" is unchecked, and "Git Ignore" and "License" are set to "None".
+
+2.8. Click on "Create Repository".
+
+Great! Now you have your Obsidian vault set up as a git repository. Now, let's push it to GitHub.
+
+### Step 3: Pushing Your Vault to GitHub
+
+3.1. After you've created the repository, in the GitHub Desktop app you'll see a dashboard with the heading "No local changes". Below you'll see a suggestion with a button "Publish repository". Click on it. (You could also use "Publish repository" button in the top application bar.)
+
+3.2. A new window will appear. Choose a name (it will automatically suggest the one you chose during the creation process, and its best to leave it this way), add an optional description, and select whether you want it to be public or private.
+
+> [!Important]
+> Please be aware that if your GitHub repository is public, this process will make your Obsidian vault publicly accessible. If you wish to keep your vault private, you'll need to select "Private" when publishing the repository.
+
+3.3. Click on "Publish Repository".
+
+3.4. Wait for the process to finish. You'll see a small prompt when the upload is complete.
+
+3.5. You can now visit your repository on GitHub's website to see your uploaded Obsidian vault.
+
+## Summary
+
+Congratulations, you've now learned how to push an Obsidian vault to your Github repository.
+
+If anything is not clear to you, or you have suggestions on how we can make this 'How to' better, please don't hesitate to let us know.
+
+Happy editing!
diff --git a/datahub-cloud/Markdown syntax support.md b/datahub-cloud/Markdown syntax support.md
new file mode 100644
index 0000000..f630c43
--- /dev/null
+++ b/datahub-cloud/Markdown syntax support.md
@@ -0,0 +1,365 @@
+---
+title: Markdown syntax support
+---
+
+Datahub was designed with Obsidian users in mind, and so, it aims to fully support Obsidian syntax, including **CommonMark**, **GitHub Flavoured Markdown** and **Obsidian extensions**, like Wiki links.
+
+## CommonMark
+
+Here are some of the CommonMark syntax elements supported by Flowershow.
+
+### Thematic breaks
+
+Thematic breaks made with three `*`, `-` or `_` will be converted to HTML `
`
+
+**Example:**
+
+```md
+---
+---
+
+---
+```
+
+**Renders as:**
+
+---
+
+---
+
+---
+
+### Headings
+
+Markdown headings will be converted to HTML ``-`` tags.
+
+**Example:**
+
+```md
+# Heading 1
+
+...
+
+###### Heading 6
+```
+
+**Renders as:**
+All the headings on this page 🙂.
+
+### Emphasis
+
+**I'm Bold!** is done using `**I'm Bold!**`
+**I'm Bold!** is done using `__I'm Bold!__`
+
+*I'm Italic!* is done using `*I'm Italic!*`
+*I'm Italic!* is done using `_I'm Italic!_`
+
+### Fenced code blocks with code highlighting
+
+Code blocks created with backtics will be parsed as `pre` tags with support for code highlighting in respective languages and copy/paste button included on hover.
+
+**Javascript example:**
+
+```javascript {2}
+const ExampleCode = () => {
+ return
....
;
+};
+```
+
+**Python example:**
+
+```python {3}
+class Example:
+ def code(self,test):
+ return 'Code highlighter'
+```
+
+**Bash example:**
+
+```bash
+git commit && git push
+```
+
+### Blockquotes
+
+**Example:**
+
+```md
+> Roses are red, violets are blue.
+```
+
+**Renders as:**
+
+> Roses are red, violets are blue.
+
+### Lists
+
+**Example:**
+
+```md
+- one
+- two
+
+1. one
+2. two
+ - one
+ - two
+```
+
+**Renders as:**
+
+- one
+- two
+
+1. one
+2. two
+ - one
+ - two
+
+### Inline code
+
+**Example:**
+
+```md
+Here is some code: `print("hello world!")`
+```
+
+**Renders as:**
+
+Here is some code: `print("hello world!")`
+
+### Links
+
+**Example:**
+
+```md
+[Link to roadmap](/docs/roadmap)
+```
+
+**Renders as:**
+
+[Link to roadmap](/docs/roadmap)
+
+### Images
+
+**Example:**
+
+```md
+![tulip](https://images.fineartamerica.com/images/artworkimages/mediumlarge/2/abstract-flowers-rose-sciberras.jpg)
+```
+
+**Renders as:**
+
+![tulip](https://images.fineartamerica.com/images/artworkimages/mediumlarge/2/abstract-flowers-rose-sciberras.jpg)
+
+> [!NOTE]
+> 🔍 To learn more about the Markdown syntax refer to the [CommonMark specification](https://spec.commonmark.org/0.30/).
+
+---
+
+## GitHub Flavored Markdown (GFM) extensions
+
+### Tables
+
+**Example:**
+
+```md
+| Left | Center | Right |
+| :--- | :----: | ----: |
+| 1 | 2 | 3 |
+```
+
+**Renders as:**
+
+| Left | Center | Right |
+| :--- | :----: | ----: |
+| 1 | 2 | 3 |
+
+### Task lists
+
+**Example:**
+
+```md
+- [x] one thing to do
+- [ ] a second thing to do
+ - [ ] another thing to do!
+```
+
+**Renders as:**
+
+- [x] one thing to do
+- [ ] a second thing to do
+ - [ ] another thing to do!
+
+### Strikethrough
+
+~~I'm CrossedOut!~~ is done using `~~I'm CrossedOut!~~`
+
+### Autolinks
+
+**Example:**
+
+```md
+Check out Flowershow at https://flowershow.app!
+```
+
+**Renders as:**
+
+Check out Flowershow at https://flowershow.app!
+
+> [!NOTE]
+> 🔍 To learn more about the GitHub Flavored Markdown syntax refer to the [GFM specification](https://github.github.com/gfm/).
+
+---
+
+## Other extensions
+
+### Obisidian internal links (Wiki links)
+
+Wiki links are hyperlinks that give one-click access to other pages on the site. These are usually denoted with double square brackets `[[some_page]]` and Obsidian would generate the reference to that page automatically.
+
+Flowershow will convert internal links to HTML `a` tags, with their `href` attributes pointing to the location referenced by original internal links.
+
+**Internal link types**
+
+- Link to a page, e.g. `[[/docs/blog]]`, which renders as [[/docs/blog]]
+- Link to a page with a custom name, e.g. `[[/docs/blog|Blog support]]`, which renders as [[/docs/blog|Blog support]]
+- Link to a specific heading within a given page `[[/docs/blog#Blog author frontmatter fields]]`, which renders as [[/docs/blog#Blog author frontmatter fields]]
+- Link to a specific heading within a given page with a custom name, e.g. `[[/docs/blog#Blog author frontmatter fields|Some alias]]` which renders as [[/docs/blog#Blog author frontmatter fields|Some alias]]
+- Link to an image file with supported image formats - png, jpg and jpeg, eg. `![[/assets/images/park.png]]` which renders as:
+ ![[park.png]]
+- 🚧 Link to a specific block (paragraph) within a given page, e.g. `[[/docs/blog#f93ba0]]`
+
+> [!note]
+> Note, that Flowershow will also handle Obsidian wiki links with "shortest path when possible" setting.
+
+### Footnotes
+
+**Example:**
+
+```md
+Roses are red... [^1]
+
+[^1]: ...violets are blue.
+```
+
+Roses are red... [^1]
+
+[^1]: ...violets are blue.
+
+### Math
+
+**Example:**
+
+```md
+$$\begin{vmatrix}a & b\\ c & d \end{vmatrix}=ad-bc$$
+```
+
+**Renders as:**
+
+$$\begin{vmatrix}a & b\\ c & d \end{vmatrix}=ad-bc$$
+
+### Dashes/Ellipse
+
+Two '-' will convert to ndash. Three '-' will convert to mdash. Three '.' with or without spacing will convert to ellipse.
+
+**Example:**
+
+```md
+--ndash
+---mdash
+...ellipse
+. . .another ellipse
+```
+
+**Renders as:**\
+–ndash\
+—mdash\
+...ellipse\
+...another ellipse
+
+### PDF embedding
+
+**Example:**
+
+```md
+![[sample.pdf]]
+```
+
+**Renders as:**
+![[sample.pdf]]
+
+## Callouts
+
+**Example:**
+
+```md
+> [!info] This is cool!
+> Here's a callout block.
+> It supports **markdown** and [[Internal link|wikilinks]].
+```
+
+**Renders as:**
+
+> [!info] This is cool!
+> Here's a callout block.
+> It supports **markdown** and [[docs/index|wikilinks]].
+
+### Supported Types:
+
+Flowershow supports 13 different Obsidian callout types (with aliases) like note, abstract, todo, or tip. See this [Obsidian docs page](https://help.obsidian.md/How+to/Use+callouts) to learn more about different callout types.
+
+- note
+- tip (alias: hint, important)
+- warning (alias: caution, attention)
+- abstract (alias: summary, tldr)
+- info
+- todo
+- success (alias: check, done)
+- question (alias: help, faq)
+- failure (alias: fail, missing)
+- danger (alias: error)
+- bug
+- example
+- quote (alias: cite)
+
+### 🚧 Text highlighting
+
+==I'm Highlighted!== is done using `==I'm Highlighted!==`
+
+### 🚧 Excalidraw sketches support
+
+Displaying embedded [Excalidraw](https://excalidraw.com/) sketches.
+
+**Example:**
+
+```md
+![[customizability-vs-upgradeability-efficient-frontier-2022-06-26]]
+```
+
+**Renders as:**
+![[customizability-vs-upgradeability-efficient-frontier-2022-06-26]]
+
+### 🚧 Comments
+
+**Example:**
+
+```md
+Here is some inline comments: %%You can't see this text%%
+
+Here is a block comment:
+%%
+It can span
+multiple lines
+%%
+```
+
+**Renders as:**
+
+Here is some inline comments: %%You can't see this text%%
+
+Here is a block comment:
+%%
+It can span
+multiple lines
+%%
diff --git a/datahub-cloud/Publish data-rich stories.md b/datahub-cloud/Publish data-rich stories.md
new file mode 100644
index 0000000..fae6d8a
--- /dev/null
+++ b/datahub-cloud/Publish data-rich stories.md
@@ -0,0 +1,402 @@
+---
+title: Publish data-rich stories with DataHub Cloud
+---
+
+In this tutorial, we are going to cover the basics of creating and publishing data-rich documents.
+
+### But wait, what is a data-rich story?
+
+A data-rich story is a document in which the writer can easily mix formatted text content with data visualizations. This means that you don't have to code nor embed your charts and tables, those can be added to the document with a very simple syntax, passing inline-data or simply referencing your data files. What you end up with is a plain text, human-readable document which is simple to edit and looks awesome when rendered in DataHub!
+
+### What does this syntax look like?
+
+The structure and text formatting of the documents are created with markdown (take a look at [this guide](https://www.datopian.com/playbook/markdown) to learn more about markdown). But it's not simply markdown, it's markdown on steroids: writers are capable of easily adding tables of content, mathematical formulas, data visualizations and more!
+
+
+
+And guess what? What you are reading right now is a data-rich document powered by DataHub, that's why we can do this:
+
+
+
+Awesome, right? Even more awesome is that this chart is created by simply having the following snippet in this document:
+
+```
+
+```
+
+You can check out the full source of the data rich document you are reading [here](https://github.com/datahubio/tutorial).
+
+More on how to create charts and tables later, but now, this must be coming from somewhere, right?
+
+### What is a DataHub project?
+
+A DataHub project is simply a GitHub repo with a README and, potentially, data files. That's right: you can take advantage of everything that GitHub offers in terms of revisioning, changes history and so on and transform your repo into a data rich document.
+
+Imagine how cool it would be to store your reports, datasets and analysis in this format. Now, let's learn how to actually do it.
+
+
+## Steps
+
+### Create a GitHub repo
+
+First, create a repo under your organisation or user in GitHub. DataHub currently does not support private repos, so make sure this new repo is public.
+
+### Push a `README.md` file to the repo
+
+Now, let's start with creating a `README.md` file. In this file, feel free to use anything that markdown has to offer. For this tutorial, we are going to use the following basic structure:
+
+```markdown
+# Data-rich story
+
+## Table
+
+## Chart
+```
+
+### Add a table
+
+Let's add a table to the `README.md` file. Under the `## Table` header in your file, add the following snippet:
+
+```mdx
+
+```
+
+Here's what it's going to look like:
+
+
+
+### Add a chart
+
+Now, let's add a graph to the README file. To keep it simple, we are going to use the LineChart component in this tutorial. Add the following snippet to your README file under the `## Chart` header:
+
+```mdx
+
+```
+
+This is what it will look like when rendered:
+
+
+
+### Final document
+
+At this point, your document should look like this:
+
+```markdown
+# Data-rich story
+
+## Table
+
+
+
+## Chart
+
+
+```
+
+We now have a README file ready to be published with DataHub Cloud!
+
+### Optional steps
+
+You can add as many markdown files to your GitHub repository as you like, and you can freely nest them in subdirectories. You can also enhance your content with other data visualisation components and markdown features.
+
+
+
+
+
+
+### Publish with DataHub
+
+1. Sign in to https://cloud.datahub.io/
+2. Click on "Create new site".
+3. Select your GitHub user/organisation.
+4. Select the repository you've just created and the branch you want to build your site off of.
+5. Click on "Create Site".
+6. Done! Now visit your site by clicking on the URL at the top of the site settings page.
+
+[👀 See an example data-rich document rendered with DataHub](https://datahub.io/@Daniellappv/datarich-demo-newest/posts/story1)
+
+___
+
+Cool, isn't it? Get in contact with us and let us know what you think! [Join our Discord](https://discord.gg/URNSkepK7z)
diff --git a/datahub-cloud/README.md b/datahub-cloud/README.md
new file mode 100644
index 0000000..262713a
--- /dev/null
+++ b/datahub-cloud/README.md
@@ -0,0 +1,98 @@
+---
+title: ➡ Documentation
+---
+
+
+
Datahub Cloud is your stupidly simple and fast tool for turning your data stories or datasets on GitHub into a published, shareable site. It converts raw data and Markdown files into beautifully presented, interactive sites.
+
+
+>[!note]
+>The current version of Datahub Cloud runs only off Github.
+
+### Templates
+
+- [Data-rich story template](https://github.com/datahubio/datahub-cloud-template-story) that renders like [this](https://datahub.io/@Daniellappv/datahub-cloud-template-story)
+- [Dataset template](https://github.com/datahubio/datahub-cloud-template) that renders like [this](https://datahub.io/@Daniellappv/datahub-cloud-template-dataset)
+- [PKM template](https://github.com/datahubio/datahub-cloud-template-pkm) that renders like [this](https://datahub.io/@Daniellappv/datahub-cloud-template-pkm)
+
+### How to deploy your first site within seconds
+
+The quickest way to start publishing with Datahub Cloud is to publish our template and customize it to fit your needs. You can do that in 5 simple steps:
+
+1. Click on the selected template from the ones listed above and click "Use this template" at the top right to create a new repository
+2. Go to [the app](https://0613d040.sibforms.com/serve/MUIFAMLy5tXMDC-gFjXRxBEcvyVYV9O9KLVoKMp1n6WMXE4LBazZkkV78pTBf3FnJHdhQpJoOYL3KsAbAv9yDYJooerqar47yy2RQkuP_Vs0CEkHexRMrkWsbKtTIi_DMOa9KfzpRVFa959hSXqJByMY5Gj9OrZtEX3ZrfO5OJHh7fLxh3nYgnNIBwGTpxJ25XA_MxOKv_kHKNgM) and create a new site by selecting the repository you just created (leave the "Root Dir" field empty)
+3. Done, it is now published! Just hit the green "Visit" button at the top right to see what it looks like.
+
+### What to do after you publish your first site
+
+After publishing our template and getting a feel for how it works, you have several options to customize it:
+
+```mermaid
+ graph TD
+
+whattodoafter["❓What to do after that"]
+customize["👷♂️ Customize template"]
+addvisuals["📈 Add visuals"]
+publishrepo[" 🏖️ Publish another repo of your own"]
+newrepo[" 🆕 Create a new repo"]
+obsidian["🖋️ Publish your Obsidian notes"]
+
+whattodoafter-->customize
+whattodoafter-->addvisuals
+whattodoafter-->publishrepo
+whattodoafter-->newrepo
+whattodoafter-->obsidian
+```
+
+### Take the template to the next level
+
+> [!note]
+> The template works best for datasets. If you don't have any data files, we suggest starting from scratch (go to [Start from scratch](https://datahub.io/docs#start-from-the-scratch))
+
+
+
+
+
+
+
+### Start from the scratch
+
+Or if that's easier, you can start from scratch or from an existing repo in Github.
+
+If you haven't worked with Github or your project does not live there, go ahead and create a new repository in Github. Create a README.md file, add some intro to it and publish it with Datahub Cloud.
+
+
+
+You can also publish an existing repository of your own and see what it looks like when published with Datahub Cloud. For any issues or errors, please open an issue here https://github.com/datopian/datahub/issues
+
+### Publish your Obsidian vault
+
+You can also publish your Obsidian notes and create your handbook with Datahub Cloud. Eg. see this beautiful example https://datahub.io/@davidgasquez/handbook.
+
+
+
+### What syntax is supported
+
+Datahub Cloud supports CommonMark and GitHub Flavored Markdown, but also many Obsidian-specific syntax elements, like Wiki links or footnotes[^1].
+
+
+
+### Need help?
+
+For any questions or suggestions for improvement please ping us on [discord](https://discord.gg/URNSkepK7z)
+
+
+
+
diff --git a/datahub-cloud/assets/Auto-sync.png b/datahub-cloud/assets/Auto-sync.png
new file mode 100644
index 0000000..4374ccc
Binary files /dev/null and b/datahub-cloud/assets/Auto-sync.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240514091335.png b/datahub-cloud/assets/Pasted image 20240514091335.png
new file mode 100644
index 0000000..c8e977e
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240514091335.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240514091658.png b/datahub-cloud/assets/Pasted image 20240514091658.png
new file mode 100644
index 0000000..0b98315
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240514091658.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240514091853.png b/datahub-cloud/assets/Pasted image 20240514091853.png
new file mode 100644
index 0000000..bf7fa03
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240514091853.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240515003021.png b/datahub-cloud/assets/Pasted image 20240515003021.png
new file mode 100644
index 0000000..09d2600
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240515003021.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240515003051.png b/datahub-cloud/assets/Pasted image 20240515003051.png
new file mode 100644
index 0000000..5e55073
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240515003051.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240515010227.png b/datahub-cloud/assets/Pasted image 20240515010227.png
new file mode 100644
index 0000000..4a54e20
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240515010227.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240515010236.png b/datahub-cloud/assets/Pasted image 20240515010236.png
new file mode 100644
index 0000000..a4d1e0b
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240515010236.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240515010252.png b/datahub-cloud/assets/Pasted image 20240515010252.png
new file mode 100644
index 0000000..7d8045b
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240515010252.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240517224144.png b/datahub-cloud/assets/Pasted image 20240517224144.png
new file mode 100644
index 0000000..7f67e17
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240517224144.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240517225336.png b/datahub-cloud/assets/Pasted image 20240517225336.png
new file mode 100644
index 0000000..9f7c880
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240517225336.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240520152011.png b/datahub-cloud/assets/Pasted image 20240520152011.png
new file mode 100644
index 0000000..3b786ec
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240520152011.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240520152158.png b/datahub-cloud/assets/Pasted image 20240520152158.png
new file mode 100644
index 0000000..f82e9e5
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240520152158.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240520154639.png b/datahub-cloud/assets/Pasted image 20240520154639.png
new file mode 100644
index 0000000..adbf023
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240520154639.png differ
diff --git a/datahub-cloud/assets/Pasted image 20240520155132.png b/datahub-cloud/assets/Pasted image 20240520155132.png
new file mode 100644
index 0000000..c39fc27
Binary files /dev/null and b/datahub-cloud/assets/Pasted image 20240520155132.png differ
diff --git a/datahub-cloud/assets/Screenshot1.png b/datahub-cloud/assets/Screenshot1.png
new file mode 100644
index 0000000..1067f6c
Binary files /dev/null and b/datahub-cloud/assets/Screenshot1.png differ
diff --git a/datahub-cloud/assets/Screenshot2.png b/datahub-cloud/assets/Screenshot2.png
new file mode 100644
index 0000000..5be79bb
Binary files /dev/null and b/datahub-cloud/assets/Screenshot2.png differ
diff --git a/datahub-cloud/assets/Screenshot3.png b/datahub-cloud/assets/Screenshot3.png
new file mode 100644
index 0000000..e010473
Binary files /dev/null and b/datahub-cloud/assets/Screenshot3.png differ
diff --git a/datahub-cloud/assets/config.json b/datahub-cloud/assets/config.json
new file mode 100644
index 0000000..3a275e1
--- /dev/null
+++ b/datahub-cloud/assets/config.json
@@ -0,0 +1,3 @@
+{
+ "showSidebar": true
+}
diff --git a/datahub-cloud/assets/css-tutorial-1.png b/datahub-cloud/assets/css-tutorial-1.png
new file mode 100644
index 0000000..58ac09c
Binary files /dev/null and b/datahub-cloud/assets/css-tutorial-1.png differ
diff --git a/datahub-cloud/assets/css-tutorial-2.png b/datahub-cloud/assets/css-tutorial-2.png
new file mode 100644
index 0000000..b014e9d
Binary files /dev/null and b/datahub-cloud/assets/css-tutorial-2.png differ
diff --git a/datahub-cloud/assets/css-tutorial-3.png b/datahub-cloud/assets/css-tutorial-3.png
new file mode 100644
index 0000000..728a334
Binary files /dev/null and b/datahub-cloud/assets/css-tutorial-3.png differ
diff --git a/datahub-cloud/assets/css-tutorial-4.png b/datahub-cloud/assets/css-tutorial-4.png
new file mode 100644
index 0000000..ce8d5f4
Binary files /dev/null and b/datahub-cloud/assets/css-tutorial-4.png differ
diff --git a/datahub-cloud/config.json b/datahub-cloud/config.json
new file mode 100644
index 0000000..3a275e1
--- /dev/null
+++ b/datahub-cloud/config.json
@@ -0,0 +1,3 @@
+{
+ "showSidebar": true
+}
diff --git a/datahub-cloud/custom.css b/datahub-cloud/custom.css
new file mode 100644
index 0000000..8b87e97
--- /dev/null
+++ b/datahub-cloud/custom.css
@@ -0,0 +1,81 @@
+/* Change heading fonts and colors */
+.bg-background {
+ background: #fff !important;
+}
+
+h1, h2, h3, h4, h5, h6 {
+ font-family: "Open Sans", sans-serif !important;
+ font-weight: bold !important;
+}
+
+h1, h4 {
+ color: #ed9e0c !important;
+}
+
+h2, h5 {
+ color: #ed9e0c !important;
+}
+
+h3, h6 {
+ color: #ed9e0c !important;
+}
+
+...
+
+.hero {
+ background-color: #fff;
+ height: 500px;
+ display: flex;
+ flex-direction: column;
+ justify-content: center;
+ align-items: center;
+ text-align: center;
+ color: #ed9e0c;
+ padding: 0 36px;
+}
+
+.hero-title {
+ font-size: 4rem;
+ color: #ed9e0c !important;
+ margin-bottom: 0px;
+}
+
+.hero-description {
+ font-size: 1rem;
+ margin-bottom: 30px;
+}
+
+.hero-button {
+ background-color: #d4e4ff;
+ color: #333;
+ padding: 10px 20px;
+ border-radius: 5px;
+ text-decoration: none;
+ font-weight: bold;
+ transition: all 0.3s ease-in-out;
+}
+
+.hero-button:hover {
+ background-color: #d4e4ff;
+ color: #ebdcf7;
+}
+
+.middle-button-container {
+ text-align: center;
+ margin: 30px 0;
+ }
+
+.middle-button {
+ background-color: #d4e4ff;
+ color: #333;
+ padding: 10px 20px;
+ border-radius: 5px;
+ text-decoration: none;
+ font-weight: bold;
+ transition: all 0.3s ease-in-out;
+ }
+
+.middle-button:hover {
+ background-color: #ed9e0c;
+ color: #333;
+ }
diff --git a/datahub-cloud/data.csv b/datahub-cloud/data.csv
new file mode 100644
index 0000000..3ce7b81
--- /dev/null
+++ b/datahub-cloud/data.csv
@@ -0,0 +1,8 @@
+year,co2
+1960,316
+1970,325
+1980,338
+1990,354
+2000,369
+2010,388
+2020,412