Merge branch 'main' into luccas_experimenting

.gitignore

@@ -39,8 +39,4 @@ testem.log
 Thumbs.db
 
 # Next.js
-.next
-
-# Env
-.env
-**/.env
+.next

README.md

@@ -1,3 +1,5 @@
+> :warning: **This documentation is outdated**: In the coming months this repo has been and will continue to experience a major revamping, this is all in the effort of modernizing and expanding the framework, with that said, not everything shown in the documentation below is going to still be aplicable so thread carefully
+
 <h1 align="center">
 🌀 Portal.JS
 <br />
@@ -7,48 +9,821 @@ Rapidly build rich data portals using a modern frontend framework
 * [What is Portal.JS ?](#What-is-Portal.JS)
     * [Features](#Features)
       * [For developers](#For-developers)
-* [Docs](#Docs)
-* [Community](#Community)
+* [Installation and setup](#Installation-and-setup)
+* [Getting Started](#Getting-Started)
+* [Tutorial](#Tutorial)
+    * [Build a single Frictionless dataset portal](#Build-a-single-Frictionless-dataset-portal)
+    * [Build a CKAN powered dataset portal](#Build-a-CKAN-powered-dataset-portal)
+* [Architecture / Reference](#Architecture--Reference)
+    * [Component List](#Component-List)
+        * [UI Components](#UI-Components)
+        * [Dataset Components](#Dataset-Components)
+        * [View Components](#View-Components)
+        * [Search Components](#Search-Components)
+        * [Blog Components](#Blog-Components)
+        * [Misc Components](#Misc-Components)
+    * [Concepts and Terms](#Concepts-and-Terms)
+        * [Dataset](#Dataset)
+        * [Resource](#Resource)
+        * [View Spec](#view-spec)
 * [Appendix](#Appendix)
     * [What happened to Recline?](#What-happened-to-Recline?)
 
 # What is Portal.JS
+🌀 `portal.js` is a framework for rapidly building rich data portal frontends using a modern frontend approach. `portal.js` can be used to present a single dataset or build a full-scale data catalog/portal.
 
-🌀 Portal.JS is a framework for rapidly building rich data portal frontends using a modern frontend approach. Portal.JS can be used to present a single dataset or build a full-scale data catalog/portal.
-
-Built in JavaScript and React on top of the popular [Next.js](https://nextjs.com/) framework. Portal.JS assumes a "decoupled" approach where the frontend is a separate service from the backend and interacts with backend(s) via an API. It can be used with any backend and has out of the box support for [CKAN](https://ckan.org/).
+`portal.js` is built in Javascript and React on top of the popular [Next.js](https://nextjs.com/) framework. `portal` assumes a "decoupled" approach where the frontend is a separate service from the backend and interacts with backend(s) via an API. It can be used with any backend and has out of the box support for [CKAN](https://ckan.org/).
 
 ## Features
 
-- 🗺️ Unified sites: present data and content in one seamless site, pulling datasets from a DMS (e.g. CKAN) and content from a CMS (e.g. Wordpress) with a common internal API.
-- 👩‍💻 Developer friendly: built with familiar frontend tech (JavaScript, React, Next.js).
-- 🔋 Batteries included: full set of portal components out of the box e.g. catalog search, dataset showcase, blog, etc.
+- 🗺️ Unified sites: present data and content in one seamless site, pulling datasets from a DMS (e.g. CKAN) and content from a CMS (e.g. wordpress) with a common internal API.
+- 👩‍💻 Developer friendly: built with familiar frontend tech Javascript, React etc
+- 🔋 Batteries included: Full set of portal components out of the box e.g. catalog search, dataset showcase, blog etc.
 - 🎨 Easy to theme and customize: installable themes, use standard CSS and React+CSS tooling. Add new routes quickly.
 - 🧱 Extensible: quickly extend and develop/import your own React components
-- 📝 Well documented: full set of documentation plus the documentation of Next.js and Apollo.
+- 📝 Well documented: full set of documentation plus the documentation of NextJS and Apollo.
 
 ### For developers
 
-- 🏗 Build with modern, familiar frontend tech such as JavaScript and React.
-- 🚀 Next.js framework: so everything in Next.js for free: Server Side Rendering, Static Site Generation, huge number of examples and integrations, etc.
-  - Server Side Rendering (SSR) => Unlimited number of pages, SEO and more whilst still using React.
-  - Static Site Generation (SSG) => Ultra-simple deployment, great performance, great lighthouse scores and more (good for small sites)
+- 🏗 Build with modern, familiar frontend tech such as Javascript and React.
+- 🚀 NextJS framework: so everything in NextJS for free React, SSR, static site generation, huge number of examples and integrations etc.
+  - SSR => unlimited number of pages, SEO etc whilst still using React.
+  - Static Site Generation (SSG) (good for small sites) => ultra-simple deployment, great performance and lighthouse scores etc
 
-#### **Check out the [Portal.JS website](https://portaljs.org/) for a gallery of live portals**
+# Installation and setup
+Before installation, ensure your system satisfies the following requirements:
+
+- Node.js 10.13 or later
+- Nextjs 10.0.3
+- MacOS, Windows (including WSL), and Linux are supported
+
+> Note: We also recommend instead of npm using `yarn` instead of `npm`.
+> 
+Portal.js is built with React on top of Nextjs framework, so for a quick setup, you can bootstrap a  Nextjs app and install portal.js as demonstrated in the code below:
+
+```bash=
+## Create a react app
+npx create-next-app
+# or
+yarn create next-app
+```
+After the installation is complete, follow the instructions to start the development server. Try editing pages/index.js and see the result on your browser.
+
+> For more information on how to use create-next-app, you can review the [create-next-app](https://nextjs.org/docs/api-reference/create-next-app) documentation.
+
+Once you have Nextjs created, you can install portal.js:
+
+```bash=
+yarn add https://github.com/datopian/portal.js.git
+```
+
+You're now ready to use portal.js in your next app. To test portal.js, open your `index.js` file in the pages folder. By default you should have some autogenerated code in the `index.js` file:
+
+
+Which outputs a page with the following content:
+
+![](https://i.imgur.com/GVh0P6p.png)
+
+Now, we are going to do some clean up and add a table component. In the `index.js` file, import a [Table]() component from portal as shown below:
+
+```javascript
+import Head from 'next/head'
+import { Table } from 'portal' //import Table component
+import styles from '../styles/Home.module.css'
+
+export default function Home() {
+
+  const columns = [
+    { field: 'id', headerName: 'ID' },
+    { field: 'firstName', headerName: 'First name' },
+    { field: 'lastName', headerName: 'Last name' },
+    { field: 'age', headerName: 'Age' }
+  ];
+
+  const rows = [
+    { id: 1, lastName: 'Snow', firstName: 'Jon', age: 35 },
+    { id: 2, lastName: 'Lannister', firstName: 'Cersei', age: 42 },
+    { id: 3, lastName: 'Lannister', firstName: 'Jaime', age: 45 },
+    { id: 4, lastName: 'Stark', firstName: 'Arya', age: 16 },
+    { id: 7, lastName: 'Clifford', firstName: 'Ferrara', age: 44 },
+    { id: 8, lastName: 'Frances', firstName: 'Rossini', age: 36 },
+    { id: 9, lastName: 'Roxie', firstName: 'Harvey', age: 65 },
+  ];
+
+  return (
+    <div className={styles.container}>
+      <Head>
+        <title>Create Portal App</title>
+        <link rel="icon" href="/favicon.ico" />
+      </Head>
+
+      <h1 className={styles.title}>
+        Welcome to <a href="https://nextjs.org">Portal.JS</a>
+      </h1>
+
+      {/* Use table component */}
+      <Table data={rows} columns={columns} />
+
+    </div>
+  )
+}
+```
+
+Now, your page should look like the following:
+
+![](https://i.imgur.com/n0vSjY4.png)
+
+> **Note**: You can learn more about individual portal components, as well as their prop types in the [components reference](#Component-List).
 
 ___
 
-# Docs
+# Getting Started
 
-Access the Portal.JS documentation at:
+If you're new to Portal.js we recommend that you start with the step-by-step guide below. You can also check out the following examples of projects built with portal.js.
 
-https://portaljs.org/docs
+* [A portal for a single Frictionless dataset](#Build-a-single-Frictionless-dataset-portal)
+* [A portal with a CKAN backend](#Build-a-CKAN-powered-dataset-portal)
 
-- [Examples](https://portaljs.org/docs#examples)
+> The [`examples` directory](https://github.com/datopian/portal.js/tree/main/examples) is regularly updated with different portal examples. 
 
-# Community
+If you have questions about anything related to Portal.js, you're always welcome to ask our community on [GitHub Discussions](https://github.com/datopian/portal.js/discussions).
+___
 
-If you have questions about anything related to Portal.JS, you're always welcome to ask our community on [GitHub Discussions](https://github.com/datopian/portal.js/discussions) or on our [Discord server](https://discord.gg/An7Bu5x8).
+# Tutorial
+
+## Build a single Frictionless dataset portal
+This tutorial will guide you through building a portal for a single Frictionless dataset.
+
+[Here’s](https://portal-js.vercel.app/) an example of the final result.
+
+### Setup
+The dataset should be a Frictionless Dataset i.e. it should have a [datapackage.json](https://specs.frictionlessdata.io/data-package/).
+
+Create a frictionless dataset portal app from the template:
+```
+npx create-next-app -e https://github.com/datopian/portal.js/tree/main/examples/dataset-frictionless
+#choose a name for your portal when prompted e.g. your-portal 
+```
+Go into your portal's directory and set the path to your dataset directory that contains the `datapackage.json`:
+```
+cd <your-portal>
+export PORTAL_DATASET_PATH=<path/to/your/dataset>
+```
+Start the server:
+```
+yarn dev
+```
+Visit the Page to view your dataset portal.
+
+## Build a CKAN powered dataset portal
+
+See [the CKAN Portal.JS example](./examples/ckan).
+
+___
+
+
+# Architecture / Reference
+
+## Component List
+
+Portal.js supports many components that can help you build amazing data portals similar to [this](https://catalog-portal-js.vercel.app/) and [this](https://portal-js.vercel.app/). 
+
+In this section, we'll cover all supported components in depth, and help you understand their use as well as the expected properties. 
+
+Components are grouped under the following sections:
+* [UI](https://github.com/datopian/portal.js/tree/main/src/components/ui): Components like Nav bar, Footer, e.t.c 
+* [Dataset](https://github.com/datopian/portal.js/tree/main/src/components/dataset): Components used for displaying a Frictionless dataset and resources
+* [Search](https://github.com/datopian/portal.js/tree/main/src/components/search): Components used for building a search interface for datasets
+* [Blog](https://github.com/datopian/portal.js/tree/main/src/components/blog): Components for building a simple blog for datasets
+* [Views](https://github.com/datopian/portal.js/tree/main/src/components/views): Components like charts, tables, maps for generating data views
+* [Misc](https://github.com/datopian/portal.js/tree/main/src/components/misc): Miscellaneous components like errors, custom links, etc used for extra design. 
+
+### UI Components
+
+In the UI we group all components that can be used for building generic page sections. These are components for building sections like the Navigation bar, Footer, Side pane, Recent datasets, e.t.c.  
+
+#### [Nav Component](https://github.com/datopian/portal.js/blob/main/src/components/ui/Nav.js)
+
+To build a navigation bar, you can use the `Nav` component as demonstrated below:
+
+```javascript
+import { Nav } from 'portal'
+
+export default function Home(){
+
+ const navMenu = [{ title: 'Blog', path: '/blog' },
+                 { title: 'Search', path: '/search' }]
+ 
+ return (
+   <>
+    <Nav logo="/images/logo.png" navMenu={navMenu}/>
+    ...
+   </>
+ 
+ )
+}
+```
+
+#### Nav Component Prop Types
+
+Nav component accepts two properties:
+* **logo**: A string to an image path. Can be relative or absolute.
+* **navMenu**: An array of objects with title and path. E.g : [{ title: 'Blog', path: '/blog' },{ title: 'Search', path: '/search' }]
+
+
+#### [Recent Component](https://github.com/datopian/portal.js/blob/main/src/components/ui/Recent.js)
+
+The `Recent` component is used to display a list of recent [datasets](#Dataset) in the home page. This useful if you want to display the most recent dataset users have interacted with in your home page. 
+To build a recent dataset section, you can use the `Recent` component as demonstrated below:
+
+```javascript
+import { Recent } from 'portal'
+
+export default function Home() {
+
+  const datasets = [
+    {
+      organization: {
+        name: "Org1",
+        title: "This is the first org",
+        description: "A description of the organization 1"
+      },
+      title: "Data package title",
+      name: "dataset1",
+      description: "description of data package",
+      resources: [],
+    },
+    {
+      organization: {
+        name: "Org2",
+        title: "This is the second org",
+        description: "A description of the organization 2"
+      },
+      title: "Data package title",
+      name: "dataset2",
+      description: "description of data package",
+      resources: [],
+    },
+  ]
+
+  return (
+    <div>
+      {/* Use Recent component */}
+      <Recent datasets={datasets} />
+    </div>
+  )
+}
+
+```
+
+Note: The `Recent` component is hyperlinked with the dataset name of the organization and the dataset name in the following format: 
+
+> `/@<org name>/<dataset name>`
+
+For instance, using the example dataset above, the first component will be link to page:
+
+> `/@org1/dataset1`
+
+and the second will be linked to:
+
+> `/@org2/dataset2` 
+
+This is useful to know when generating dynamic pages for each dataset. 
+
+#### Recent Component Prop Types
+
+The `Recent` component accepts the following properties:
+* **datasets**: An array of [datasets](#Dataset)
+
+### Dataset Components
+
+The dataset component groups together components that can be used for building a dataset UI. These includes components for displaying info about a dataset, resources in a dataset as well as dataset ReadMe.
+
+#### [KeyInfo Component](https://github.com/datopian/portal.js/blob/main/src/components/dataset/KeyInfo.js)
+
+The `KeyInfo` components displays key properties like the number of resources, size, format, licences of in a dataset in tabular form. See example in the `Key Info` section [here](https://portal-js.vercel.app/). To use it, you can import the `KeyInfo` component as demonstrated below:
+```javascript
+import { KeyInfo } from 'portal'
+
+export default function Home() {
+
+  const datapackage = {
+    "name": "finance-vix",
+    "title": "VIX - CBOE Volatility Index",
+    "homepage": "http://www.cboe.com/micro/VIX/",
+    "version": "0.1.0",
+    "license": "PDDL-1.0",
+    "sources": [
+      {
+        "title": "CBOE VIX Page",
+        "name": "CBOE VIX Page",
+        "web": "http://www.cboe.com/micro/vix/historical.aspx"
+      }
+    ],
+    "resources": [
+      {
+        "name": "vix-daily",
+        "path": "vix-daily.csv",
+        "format": "csv",
+        "size": 20982,
+        "mediatype": "text/csv",
+      }
+    ]
+  }
+
+  return (
+    <div>
+      {/* Use KeyInfo component */}
+      <KeyInfo descriptor={datapackage} resources={datapackage.resources} />
+    </div>
+  )
+}
+
+```
+
+#### KeyInfo Component Prop Types
+
+KeyInfo component accepts two properties:
+* **descriptor**: A [Frictionless data package descriptor](https://specs.frictionlessdata.io/data-package/#descriptor)
+* **resources**: An [Frictionless data package resource](https://specs.frictionlessdata.io/data-resource/#introduction)
+
+
+#### [ResourceInfo Component](https://github.com/datopian/portal.js/blob/main/src/components/dataset/ResourceInfo.js)
+
+The `ResourceInfo` components displays key properties like the name, size, format, modification dates, as well as a download link in a resource object. See an example of a `ResourceInfo` component in the `Data Files` section [here](https://portal-js.vercel.app/).
+
+You can import and use the `ResourceInfo` component as demonstrated below:
+```javascript
+import { ResourceInfo } from 'portal'
+
+export default function Home() {
+
+  const resources = [
+    {
+      "name": "vix-daily",
+      "path": "vix-daily.csv",
+      "format": "csv",
+      "size": 20982,
+      "mediatype": "text/csv",
+    },
+    {
+      "name": "vix-daily 2",
+      "path": "vix-daily2.csv",
+      "format": "csv",
+      "size": 2082,
+      "mediatype": "text/csv",
+    }
+  ]
+
+  return (
+    <div>
+      {/* Use Recent component */}
+      <ResourceInfo resources={resources} />
+    </div>
+  )
+}
+```
+
+#### ResourceInfo Component Prop Types
+
+ResourceInfo component accepts a single property:
+* **resources**: An [Frictionless data package resource](https://specs.frictionlessdata.io/data-resource/#introduction)
+
+
+#### [ReadMe Component](https://github.com/datopian/portal.js/blob/main/src/components/dataset/Readme.js)
+
+The `ReadMe` component is used for displaying a compiled dataset Readme in a readable format. See example in the `README` section [here](https://portal-js.vercel.app/).
+
+> Note: By compiled ReadMe, we mean ReadMe that has been converted to plain string using a package like [remark](https://www.npmjs.com/package/remark).
+
+You can import and use the `ReadMe` component as demonstrated below:
+```javascript
+import { ReadMe } from 'portal'
+import remark from 'remark'
+import html from 'remark-html'
+import { useEffect, useState } from 'react'
+
+
+const readMeMarkdown = `
+    CBOE Volatility Index (VIX) time-series dataset including daily open, close,
+    high and low. The CBOE Volatility Index (VIX) is a key measure of market
+    expectations of near-term volatility conveyed by S&P 500 stock index option
+    prices introduced in 1993.
+
+    ## Data
+
+    From the [VIX FAQ][faq]:
+
+    > In 1993, the Chicago Board Options Exchange® (CBOE®) introduced the CBOE
+    > Volatility Index®, VIX®, and it quickly became the benchmark for stock market
+    > volatility. It is widely followed and has been cited in hundreds of news
+    > articles in the Wall Street Journal, Barron's and other leading financial
+    > publications. Since volatility often signifies financial turmoil, VIX is
+    > often referred to as the "investor fear gauge".
+
+    [faq]: http://www.cboe.com/micro/vix/faq.aspx
+
+    ## License
+
+    No obvious statement on [historical data page][historical]. Given size and
+    factual nature of the data and its source from a US company would imagine this
+    was public domain and as such have licensed the Data Package under the Public
+    Domain Dedication and License (PDDL).
+
+    [historical]: http://www.cboe.com/micro/vix/historical.aspx
+`
+
+export default function Home() {
+  const [readMe, setreadMe] = useState("")
+
+  useEffect(() => {
+    async function processReadMe() {
+      const processed = await remark()
+        .use(html)
+        .process(readMeMarkdown)
+      setreadMe(processed.toString())
+    }
+    processReadMe()
+  }, [])
+
+  return (
+    <div>
+      <ReadMe readme={readMe} />
+    </div>
+  )
+}
+
+```
+
+#### ReadMe Component Prop Types
+
+The `ReadMe` component accepts a single property:
+* **readme**: A string of a compiled ReadMe in html format. 
+
+### [View Components](https://github.com/datopian/portal.js/tree/main/src/components/views)
+
+View components is a set of components that can be used for displaying dataset views like charts, tables, maps, e.t.c. 
+
+#### [Chart Component](https://github.com/datopian/portal.js/blob/main/src/components/views/Chart.js)
+
+The `Chart` components exposes different chart components like Plotly Chart, Vega charts, which can be used for showing graphs. See example in the `Graph` section [here](https://portal-js.vercel.app/). 
+To use a chart component, you need to compile and pass a view spec as props to the chart component. 
+Each Chart type have their specific spec, as explained in this [doc](https://specs.frictionlessdata.io/views/#graph-spec).
+
+In the example below, we assume there's a compiled Plotly spec:
+
+```javascript
+import { PlotlyChart } from 'portal'
+
+export default function Home({plotlySpec}) {
+
+  return (
+    < div >
+      <PlotlyChart spec={plotlySpec} />
+    </div>
+  )
+}
+
+```
+> Note: You can compile views using the [datapackage-render](https://github.com/datopian/datapackage-views-js) library, as demonstrated in [this example](https://github.com/datopian/portal.js/blob/main/examples/dataset-frictionless/lib/utils.js).
+
+
+#### Chart Component Prop Types
+
+KeyInfo component accepts two properties:
+* **spec**: A compiled view spec depending on the chart type. 
+
+#### [Table Component](https://github.com/datopian/portal.js/blob/main/examples/dataset-frictionless/components/Table.js)
+
+The `Table` component is used for displaying dataset resources as a tabular grid. See example in the `Data Preview` section [here](https://portal-js.vercel.app/). 
+To use a Table component, you have to pass an array of data and columns as demonstrated below:
+
+```javascript
+import { Table } from 'portal' //import Table component
+
+export default function Home() {
+
+  const columns = [
+    { field: 'id', headerName: 'ID' },
+    { field: 'firstName', headerName: 'First name' },
+    { field: 'lastName', headerName: 'Last name' },
+    { field: 'age', headerName: 'Age' }
+  ];
+
+  const data = [
+    { id: 1, lastName: 'Snow', firstName: 'Jon', age: 35 },
+    { id: 2, lastName: 'Lannister', firstName: 'Cersei', age: 42 },
+    { id: 3, lastName: 'Lannister', firstName: 'Jaime', age: 45 },
+    { id: 4, lastName: 'Stark', firstName: 'Arya', age: 16 },
+    { id: 7, lastName: 'Clifford', firstName: 'Ferrara', age: 44 },
+    { id: 8, lastName: 'Frances', firstName: 'Rossini', age: 36 },
+    { id: 9, lastName: 'Roxie', firstName: 'Harvey', age: 65 },
+  ];
+
+  return (
+    <Table data={data} columns={columns} />
+  )
+}
+
+```
+> Note: Under the hood, Table component uses the [DataGrid Material UI table](https://material-ui.com/components/data-grid/), and as such all supported params in data and columns are supported. 
+
+
+#### Table Component Prop Types
+
+Table component accepts two properties:
+* **data**: An array of column names with properties: e.g [{field: "col1", headerName: "col1"}, {field: "col2", headerName: "col2"}]
+* **columns**: An array of data objects e.g. [ {col1: 1, col2: 2}, {col1: 5, col2: 7} ]
+
+
+### [Search Components](https://github.com/datopian/portal.js/tree/main/src/components/search)
+
+Search components groups together components that can be used for creating a search interface. This includes search forms, search item as well as search result list. 
+
+#### [Form Component](https://github.com/datopian/portal.js/blob/main/src/components/search/Form.js)
+
+The search`Form` component is a simple search input and submit button. See example of a search form [here](https://catalog-portal-js.vercel.app/search). 
+
+The search `form` requires a submit handler (`handleSubmit`). This handler function receives the search term, and handles actual search. 
+
+In the example below, we demonstrate how to use the `Form` component.
+
+```javascript
+import { Form } from 'portal'
+
+export default function Home() {
+
+  const handleSearchSubmit = (searchQuery) => {
+    // Write your custom code to perform search in db
+    console.log(searchQuery);
+  }
+
+  return (
+    <Form
+      handleSubmit={handleSearchSubmit} />
+  )
+}
+```
+
+#### Form Component Prop Types
+
+The `Form` component accepts a single property:
+* **handleSubmit**: A function that receives the search text, and can be customize to perform the actual search. 
+
+#### [Item Component](https://github.com/datopian/portal.js/blob/main/src/components/search/Item.js)
+
+The search`Item` component can be used to display a single search result. 
+
+In the example below, we demonstrate how to use the `Item` component.
+
+```javascript
+import { Item } from 'portal'
+
+export default function Home() {
+  const datapackage = {
+    "name": "finance-vix",
+    "title": "VIX - CBOE Volatility Index",
+    "homepage": "http://www.cboe.com/micro/VIX/",
+    "version": "0.1.0",
+    "description": "This is a test organization description",
+    "resources": [
+      {
+        "name": "vix-daily",
+        "path": "vix-daily.csv",
+        "format": "csv",
+        "size": 20982,
+        "mediatype": "text/csv",
+      }
+    ]
+  }
+
+  return (
+    <Item dataset={datapackage} />
+  )
+}
+```
+
+#### Item Component Prop Types
+
+The `Item` component accepts a single property:
+* **dataset**: A [Frictionless data package descriptor](https://specs.frictionlessdata.io/data-package/#descriptor)
+
+
+#### [ItemTotal Component](https://github.com/datopian/portal.js/blob/main/src/components/search/Item.js)
+
+The search`ItemTotal` is a simple component for displaying the total search result 
+
+In the example below, we demonstrate how to use the `ItemTotal` component.
+
+```javascript
+import { ItemTotal } from 'portal'
+
+export default function Home() {
+  //do some custom search to get results
+  const search = (text) => {
+    return [{ name: "data1" }, { name: "data2" }]
+  }
+  //get the total result count
+  const searchTotal = search("some text").length
+
+  return (
+    <ItemTotal count={searchTotal} />
+  )
+}
+```
+
+#### ItemTotal Component Prop Types
+
+The `ItemTotal` component accepts a single property:
+* **count**: An integer of the total number of results. 
+
+
+### [Blog Components](https://github.com/datopian/portal.js/tree/main/src/components/blog)
+
+These are group of components for building a portal blog. See example of portal blog [here](https://catalog-portal-js.vercel.app/blog)
+
+#### [PostList Components](https://github.com/datopian/portal.js/tree/main/src/components/misc)
+
+The `PostList` component is used to display a list of blog posts with the title and a short excerpts from the content.
+
+In the example below, we demonstrate how to use the `PostList` component.
+
+```javascript
+import { PostList } from 'portal'
+
+export default function Home() {
+
+  const posts = [
+    { title: "Blog post 1", excerpt: "This is the first blog excerpts in this list." },
+    { title: "Blog post 2", excerpt: "This is the second blog excerpts in this list." },
+    { title: "Blog post 3", excerpt: "This is the third blog excerpts in this list." },
+  ]
+  return (
+    <PostList posts={posts} />
+  )
+}
+```
+
+#### PostList Component Prop Types
+
+The `PostList` component accepts a single property:
+* **posts**: An array of post list objects with the following properties:
+    ```javascript
+    [
+        { 
+          title: "The title of the blog post",
+          excerpt: "A short excerpt from the post content",
+        },
+    ]
+    ```
+
+#### [Post Components](https://github.com/datopian/portal.js/tree/main/src/components/misc)
+
+The `Post` component is used to display a blog post. See an example of a blog post [here](https://catalog-portal-js.vercel.app/blog/nyt-pa-platformen-opdateringsfrekvens-og-andres-data)
+
+In the example below, we demonstrate how to use the `Post` component.
+
+```javascript
+import { Post } from 'portal'
+import * as dayjs from 'dayjs' //For converting UTC time to relative format
+import relativeTime from 'dayjs/plugin/relativeTime'
+
+dayjs.extend(relativeTime)
+
+export default function Home() {
+
+  const post = {
+    title: "This is a sample blog post",
+    content: `<h1>A simple header</h1>
+    The PostList component is used to display a list of blog posts
+              with the title and a short excerpts from the content.
+              In the example below, we demonstrate how to use the PostList component.`,
+    createdAt: dayjs().to(dayjs(1620649596902)),
+    featuredImage: "https://pixabay.com/get/ge9a766d1f7b5fe0eccbf0f439501a2cf2b191997290e7ab15e6a402574acc2fdba48a82d278dca3547030e0202b7906d_640.jpg"
+  }
+
+  return (
+    <Post post={post} />
+  )
+}
+```
+
+#### Post Component Prop Types
+
+The `Post` component accepts a single property:
+* **post**: An object with the following properties:
+```javascript
+  {
+    title: <The title of the blog post>
+    content: <The body of the blog post. Can be plain text or html>
+    createdAt: <The utc date when the post was last modified>
+    featuredImage: < Url/relative url to post cover image>
+  }
+```
+
+
+### [Misc Components](https://github.com/datopian/portal.js/tree/main/src/components/misc)
+
+These are group of miscellaneous/extra components for extending your portal. They include components like Errors, custom links, etc.
+
+#### [Error Component](https://github.com/datopian/portal.js/blob/main/src/components/misc/Error.js)
+
+The `Error` component is used to display a custom error message.
+
+In the example below, we demonstrate how to use the `Error` component.
+
+```javascript
+import { Error } from 'portal'
+
+export default function Home() {
+
+  return (
+    <Error message="An error occured when loading the file!" />
+  )
+}
+```
+
+#### Error Component Prop Types
+
+The `Error` component accepts a single property:
+* **message**: A string with the error message to display. 
+    
+    
+#### [Custom Component](https://github.com/datopian/portal.js/blob/main/src/components/misc/Error.js)
+
+The `CustomLink` component is used to create a link with a consistent style to other portal components. 
+
+In the example below, we demonstrate how to use the `CustomLink` component.
+
+```javascript
+import { CustomLink } from 'portal'
+
+export default function Home() {
+
+  return (
+    <CustomLink url="/blog" title="Goto Blog" />
+  )
+}
+```
+
+#### CustomLink Component Prop Types
+
+The `CustomLink` component accepts the following properties:
+
+* **url**: A string. The relative or absolute url of the link. 
+* **title**: A string. The title of the link
+
+
+___
+
+## Concepts and Terms
+In this section, we explain some of the terms and concepts used throughtout the portal.js documentation. 
+> Some of these concepts are part of official specs, and when appropriate, we'll link to the sources where you can get more details. 
+### Dataset
+A dataset extends the [Frictionless data package](https://specs.frictionlessdata.io/data-package/#metadata) to add an extra organization property. The organization property describes the organization the dataset belongs to, and it should have the following properties:
+```javascript
+organization = {
+ name: "some org name",
+ title: "Some optional org title",
+ description: "A description of the organization"
+}
+```
+An example of dataset with organization properties is given below:
+```javascript
+datasets = [{
+    organization: {
+     name: "some org name",
+     title: "Some optional org title",
+     description: "A description of the organization"
+    },
+    title: "Data package title",
+    name:  "Data package name",
+    description: "description of data package",
+    resources: [...],
+    licences: [...],
+    sources: [...]
+    }
+]
+```
+
+### Resource
+TODO
+
+### view spec
+
+---
+
+## Deploying portal build to github pages
+
+[Deploying single frictionless dataset to Github](https://portaljs.org/publish)
+
+## Showcases
+
+### Single Dataset with Default Theme
+
+![Single Dataset Example](./examples/dataset-frictionless/assets/demo.gif)
+
+---
 
 # Appendix
 

examples/ckan-2021/README.md

@@ -1,8 +1,262 @@
-# 🌀 PortalJS example with CKAN and Apollo
+<h1 align="center">
 
-**🚩 UPDATE April 2023: This example is now deprecated - though still works!. Please use the [new CKAN examples](https://github.com/datopian/portaljs/tree/main/examples)**
+🌀 Portal.JS<br/>
+The javascript framework for<br/>
+data portals
 
-This example shows how you can build a full data portal using a CKAN Backend with a Next.JS Frontend powered by Apollo, a full fledged guide is available as a [blog post](https://portaljs.org/blog/example-ckan-2021)
+</h1>
+
+🌀 `Portal` is a framework for rapidly building rich data portal frontends using a modern frontend approach (javascript, React, SSR).
+
+`Portal` assumes a "decoupled" approach where the frontend is a separate service from the backend and interacts with backend(s) via an API. It can be used with any backend and has out of the box support for [CKAN][]. `portal` is built in Javascript and React on top of the popular [Next.js][] framework.
+
+[ckan]: https://ckan.org/
+[next.js]: https://nextjs.com/
+
+Live DEMO: https://catalog-portal-js.vercel.app
+
+## Features
+
+- 🗺️ Unified sites: present data and content in one seamless site, pulling datasets from a DMS (e.g. CKAN) and content from a CMS (e.g. wordpress) with a common internal API.
+- 👩‍💻 Developer friendly: built with familiar frontend tech Javascript, React etc
+- 🔋 Batteries included: Full set of portal components out of the box e.g. catalog search, dataset showcase, blog etc.
+- 🎨 Easy to theme and customize: installable themes, use standard CSS and React+CSS tooling. Add new routes quickly.
+- 🧱 Extensible: quickly extend and develop/import your own React components
+- 📝 Well documented: full set of documentation plus the documentation of NextJS and Apollo.
+
+### For developers
+
+- 🏗 Build with modern, familiar frontend tech such as Javascript and React.
+- 🚀 NextJS framework: so everything in NextJS for free React, SSR, static site generation, huge number of examples and integrations etc.
+  - SSR => unlimited number of pages, SEO etc whilst still using React.
+  - Static Site Generation (SSG) (good for small sites) => ultra-simple deployment, great performance and lighthouse scores etc
+- 📋 Typescript support
+
+## Getting Started
+
+### Setup
+
+Install a recent version of Node. You'll need Node 10.13 or later.
+
+### Create a Portal app
+
+To create a Portal app, open your terminal, cd into the directory you'd like to create the app in, and run the following command:
+
+```console
+npm init portal-app my-data-portal
+```
+
+> NB: Under the hood, this uses the tool called create-next-app, which bootstraps a Next.js app for you. It uses this template through the --example flag.
+>
+> If it doesn’t work, please open an issue.
+
+## Guide
+
+### Styling 🎨
+
+We use Tailwind as a CSS framework. Take a look at `/styles/index.css` to see what we're importing from Tailwind bundle. You can also configure Tailwind using `tailwind.config.js` file.
+
+Have a look at Next.js support of CSS and ways of writing CSS:
+
+https://nextjs.org/docs/basic-features/built-in-css-support
+
+### Backend
+
+So far the app is running with mocked data behind. You can connect CMS and DMS backends easily via environment variables:
+
+```console
+$ export DMS=http://ckan:5000
+$ export CMS=http://myblog.wordpress.com
+```
+
+> Note that we don't yet have implementations for the following CKAN features:
+>
+> - Activities
+> - Auth
+> - Groups
+> - Facets
+
+### Routes
+
+These are the default routes set up in the "starter" app.
+
+- Home `/`
+- Search `/search`
+- Dataset `/@org/dataset`
+- Resource `/@org/dataset/r/resource`
+- Organization `/@org`
+- Collection (aka group in CKAN) (?) - suggest to merge into org
+- Static pages, eg, `/about` etc. from CMS or can do it without external CMS, e.g., in Next.js
+
+### New Routes
+
+TODO
+
+### Data fetching
+
+We use Apollo client which allows us to query data with GraphQL. We have setup CKAN API for the demo (it uses demo.ckan.org as DMS):
+
+http://portal.datopian1.now.sh/
+
+Note that we don't have Apollo Server but we connect CKAN API using [`apollo-link-rest`](https://www.apollographql.com/docs/link/links/rest/) module. You can see how it works in [lib/apolloClient.ts](https://github.com/datopian/portal/blob/master/lib/apolloClient.ts) and then have a look at [pages/\_app.tsx](https://github.com/datopian/portal/blob/master/pages/_app.tsx).
+
+For development/debugging purposes, we suggest installing the Chrome extension - https://chrome.google.com/webstore/detail/apollo-client-developer-t/jdkknkkbebbapilgoeccciglkfbmbnfm.
+
+#### i18n configuration
+
+Portal.js is configured by default to support both `English` and `French` subpath for language translation. But for subsequent users, this following steps can be used to configure i18n for other languages;
+
+1.  Update `next.config.js`, to add more languages to the i18n locales
+
+```js
+i18n: {
+  locales: ['en', 'fr', 'nl-NL'], // add more language to the list
+  defaultLocale: 'en',  // set the default language to use
+},
+```
+
+2. Create a folder for the language in `locales` --> `locales/en-Us`
+
+3. In the language folder, different namespace files (json) can be created for each translation. For the `index.js` use-case, I named it `common.json`
+
+```json
+// locales/en/common.json
+{
+   "title" : "Portal js in English",
+}
+
+// locales/fr/common.json
+{
+   "title" : "Portal js in French",
+}
+```
+
+4. To use on pages using Server-side Props.
+
+```js
+import { loadNamespaces } from './_app';
+import useTranslation from 'next-translate/useTranslation';
+
+const Home: React.FC = ()=> {
+  const { t } = useTranslation();
+  return (
+    <div>{t(`common:title`)}</div> // we use common and title base on the common.json data
+  );
+};
+
+export const getServerSideProps: GetServerSideProps = async ({ locale }) => {
+      ........  ........
+  return {
+    props : {
+      _ns:  await loadNamespaces(['common'], locale),
+    }
+  };
+};
+
+```
+
+5. Go to the browser and view the changes using language subpath like this `http://localhost:3000` and `http://localhost:3000/fr`. **Note** The subpath also activate chrome language Translator
+
+#### Pre-fetch data in the server-side
+
+When visiting a dataset page, you may want to fetch the dataset metadata in the server-side. To do so, you can use `getServerSideProps` function from NextJS:
+
+```javascript
+import { GetServerSideProps } from 'next';
+import { initializeApollo } from '../lib/apolloClient';
+import gql from 'graphql-tag';
+
+const QUERY = gql`
+  query dataset($id: String) {
+    dataset(id: $id) @rest(type: "Response", path: "package_show?{args}") {
+      result
+    }
+  }
+`;
+
+...
+
+export const getServerSideProps: GetServerSideProps = async (context) => {
+  const apolloClient = initializeApollo();
+
+  await apolloClient.query({
+    query: QUERY,
+    variables: {
+      id: 'my-dataset'
+    },
+  });
+
+  return {
+    props: {
+      initialApolloState: apolloClient.cache.extract(),
+    },
+  };
+};
+```
+
+This would fetch the data from DMS and save it in the Apollo cache so that we can query it again from the components.
+
+#### Access data from a component
+
+Consider situation when rendering a component for org info on the dataset page. We already have pre-fetched dataset metadata that includes `organization` property with attributes such as `name`, `title` etc. We can now query only organization part for our `Org` component:
+
+```javascript
+import { useQuery } from '@apollo/react-hooks';
+import gql from 'graphql-tag';
+
+export const GET_ORG_QUERY = gql`
+  query dataset($id: String) {
+    dataset(id: $id) @rest(type: "Response", path: "package_show?{args}") {
+      result {
+        organization {
+          name
+          title
+          image_url
+        }
+      }
+    }
+  }
+`;
+
+export default function Org({ variables }) {
+  const { loading, error, data } = useQuery(
+    GET_ORG_QUERY,
+    {
+      variables: { id: 'my-dataset' }
+    }
+  );
+
+  ...
+
+  const { organization } = data.dataset.result;
+
+  return (
+    <>
+      {organization ? (
+        <>
+          <img
+            src={
+              organization.image_url
+            }
+            className="h-5 w-5 mr-2 inline-block"
+          />
+          <Link href={`/@${organization.name}`}>
+            <a className="font-semibold text-primary underline">
+              {organization.title || organization.name}
+            </a>
+          </Link>
+        </>
+      ) : (
+        ''
+      )}
+    </>
+  );
+}
+```
+
+#### Add a new data source
+
+TODO
 
 ## Developers
 
@@ -49,5 +303,4 @@ yarn run e2e
 
 ### Key Pages
 
-See https://datahub.io/docs/dms/frontend/
-
+See https://tech.datopian.com/frontend/

examples/ckan-example/.env

@@ -1 +0,0 @@
-DMS=https://demo.dev.datopian.com

examples/ckan-example/.eslintrc.json

@@ -1,33 +0,0 @@
-{
-  "extends": [
-    "next",
-    "next/core-web-vitals",
-    "../../.eslintrc.json"
-  ],
-  "ignorePatterns": ["!**/*", ".next/**/*"],
-  "overrides": [
-    {
-      "files": ["*.ts", "*.tsx", "*.js", "*.jsx"],
-      "rules": {
-        "@next/next/no-html-link-for-pages": [
-          "error",
-          "examples/ckan-example/pages"
-        ]
-      }
-    },
-    {
-      "files": ["*.ts", "*.tsx"],
-      "rules": {}
-    },
-    {
-      "files": ["*.js", "*.jsx"],
-      "rules": {}
-    }
-  ],
-  "rules": {
-    "@next/next/no-html-link-for-pages": "off"
-  },
-  "env": {
-    "jest": true
-  }
-}

examples/ckan-example/README.md

@@ -1,46 +0,0 @@
-This is a repo intended to serve as an example of a data catalog that get its data from a CKAN Instance.
-
-```
-npx create-next-app <app-name> --example https://github.com/datopian/portaljs/tree/main/examples/ckan-example
-cd <app-name>
-```
-
-- This project uses CKAN as a backend, so you need to point the project to the CKAN Url desired, you can do so by setting up the `DMS` env variable in your terminal or adding a `.env` file with the following content:
-
-```
-DMS=<ckan url>
-```
-
-- Run the app using:
-
-```
-npm run dev
-```
-
-Congratulations, you now have something similar to this running on `http://localhost:4200`
-![](https://media.discordapp.net/attachments/1069718983604977754/1098252297726865408/image.png?width=853&height=461)
-If yo go to any one of those pages by clicking on `More info` you will see something similar to this
-![](https://media.discordapp.net/attachments/1069718983604977754/1098252298074988595/image.png?width=853&height=461)
-
-## Deployment
-
-[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Fdatopian%2Fportaljs%2Ftree%2Fmain%2Fexamples%2Fckan-example&env=DMS&envDescription=URL%20For%20the%20CKAN%20Backend%20Ex%3A%20https%3A%2F%2Fdemo.dev.datopian.com)
-
-By clicking on this button, you will be redirected to a page which will allow you to clone the content into your own github/gitlab/bitbucket account and automatically deploy everything.
-
-
-
-## Extra commands
-
-You can also build the project for production with
-
-```
-npm run build
-```
-
-And run using the production build like so:
-
-```
-npm run start
-```
-

examples/ckan-example/index.d.ts

@@ -1,6 +0,0 @@
-/* eslint-disable @typescript-eslint/no-explicit-any */
-declare module '*.svg' {
-  const content: any;
-  export const ReactComponent: any;
-  export default content;
-}

examples/ckan-example/next-env.d.ts

@@ -1,5 +0,0 @@
-/// <reference types="next" />
-/// <reference types="next/image-types/global" />
-
-// NOTE: This file should not be edited
-// see https://nextjs.org/docs/basic-features/typescript for more information.

examples/ckan-example/next.config.js

@@ -1,17 +0,0 @@
-const nextConfig = {
-  publicRuntimeConfig: {
-    DMS: process.env.DMS ? process.env.DMS : '',
-  },
-  async rewrites() {
-    return {
-      beforeFiles: [
-        {
-          source: '/@:org/:project*',
-          destination: '/@org/:org/:project*',
-        },
-      ],
-    };
-  },
-};
-
-module.exports = nextConfig;

examples/ckan-example/package.json

@@ -1,33 +0,0 @@
-{
-  "name": "my-app",
-  "version": "0.1.0",
-  "private": true,
-  "scripts": {
-    "dev": "next dev",
-    "build": "next build",
-    "start": "next start",
-    "lint": "next lint"
-  },
-  "dependencies": {
-    "@heroicons/react": "^2.0.17",
-    "@types/node": "18.16.0",
-    "@types/react": "18.0.38",
-    "@types/react-dom": "18.0.11",
-    "eslint": "8.39.0",
-    "eslint-config-next": "13.3.1",
-    "next": "13.3.1",
-    "next-seo": "^6.0.0",
-    "octokit": "^2.0.14",
-    "react": "18.2.0",
-    "react-dom": "18.2.0",
-    "react-markdown": "^8.0.7",
-    "remark-gfm": "^3.0.1",
-    "typescript": "5.0.4"
-  },
-  "devDependencies": {
-    "@tailwindcss/typography": "^0.5.9",
-    "autoprefixer": "^10.4.14",
-    "postcss": "^8.4.23",
-    "tailwindcss": "^3.3.1"
-  }
-}

examples/ckan-example/pages/@org/[org]/[dataset]/index.tsx

@@ -1,188 +0,0 @@
-import { GetServerSideProps } from 'next';
-import getConfig from 'next/config';
-import React from 'react';
-import {
-  CalendarIcon,
-  CloudArrowUpIcon,
-  FolderOpenIcon,
-  LockClosedIcon,
-  MapPinIcon,
-  PaperClipIcon,
-  ServerIcon,
-  UserIcon,
-} from '@heroicons/react/20/solid';
-
-const dms = getConfig().publicRuntimeConfig.DMS;
-
-const formatter = new Intl.DateTimeFormat('en-US', {
-  year: 'numeric',
-  month: 'long',
-  day: 'numeric',
-  hour: 'numeric',
-  minute: 'numeric',
-  second: 'numeric',
-  timeZone: 'UTC',
-});
-
-export const getServerSideProps: GetServerSideProps = async (context) => {
-  const { dataset } = context.query;
-  const response = await fetch(
-    `${dms}/api/3/action/package_show?id=${dataset}`
-  );
-  const _dataset = await response.json();
-  return {
-    props: {
-      dataset: _dataset.result,
-    },
-  };
-};
-
-const positions = [
-  {
-    id: 1,
-    title: 'Back End Developer',
-    type: 'Full-time',
-    location: 'Remote',
-    department: 'Engineering',
-    closeDate: '2020-01-07',
-    closeDateFull: 'January 7, 2020',
-  },
-  {
-    id: 2,
-    title: 'Front End Developer',
-    type: 'Full-time',
-    location: 'Remote',
-    department: 'Engineering',
-    closeDate: '2020-01-07',
-    closeDateFull: 'January 7, 2020',
-  },
-  {
-    id: 3,
-    title: 'User Interface Designer',
-    type: 'Full-time',
-    location: 'Remote',
-    department: 'Design',
-    closeDate: '2020-01-14',
-    closeDateFull: 'January 14, 2020',
-  },
-];
-
-export default function DatasetPage({ dataset }) {
-  return (
-    <div className="overflow-hidden bg-white py-24 sm:py-32">
-      <div className="mx-auto max-w-7xl px-6 lg:px-8">
-        <div className="mx-auto grid max-w-2xl grid-cols-1 gap-x-8 gap-y-16 sm:gap-y-20 lg:mx-0 lg:max-w-none lg:grid-cols-2">
-          <div className="lg:pr-8 lg:pt-4">
-            <div className="lg:max-w-lg">
-              <h2 className="text-base font-semibold leading-7 text-indigo-600">
-                {dataset.organization.title
-                  ? dataset.organization.title
-                  : dataset.organization.name}
-              </h2>
-              <p className="mt-2 text-3xl font-bold tracking-tight text-gray-900 sm:text-4xl">
-                {dataset.title ? dataset.title : dataset.name}
-              </p>
-              <p className="mt-6 leading-8 text-gray-600">
-                {dataset.notes ? dataset.notes : 'No description'}
-              </p>
-              <div className="mt-6 border-t border-gray-100">
-                <dl className="divide-y divide-gray-100">
-                  {dataset.tags.length > 0 && (
-                    <div className="px-4 py-6 sm:grid sm:grid-cols-3 sm:gap-4 sm:px-0">
-                      <dt className="text-sm font-medium leading-6 text-gray-900">
-                        Tags
-                      </dt>
-                      <dd className="mt-1 text-sm leading-6 text-gray-700 sm:col-span-2 sm:mt-0">
-                        {dataset.tags.map((tag) => tag.display_name).join(', ')}
-                      </dd>
-                    </div>
-                  )}
-                  {dataset.url && (
-                    <div className="px-4 py-6 sm:grid sm:grid-cols-3 sm:gap-4 sm:px-0">
-                      <dt className="text-sm font-medium leading-6 text-gray-900">
-                        Url
-                      </dt>
-                      <dd className="mt-1 text-sm leading-6 text-gray-700 sm:col-span-2 sm:mt-0">
-                        {dataset.url}
-                      </dd>
-                    </div>
-                  )}
-                  <div className="px-4 py-6 sm:grid sm:grid-cols-3 sm:gap-4 sm:px-0">
-                    <dt className="text-sm font-medium leading-6 text-gray-900">
-                      Created
-                    </dt>
-                    <dd className="mt-1 text-sm leading-6 text-gray-700 sm:col-span-2 sm:mt-0">
-                      {formatter.format(new Date(dataset.metadata_created))}
-                    </dd>
-                  </div>
-                  <div className="px-4 py-6 sm:grid sm:grid-cols-3 sm:gap-4 sm:px-0">
-                    <dt className="text-sm font-medium leading-6 text-gray-900">
-                      Modified
-                    </dt>
-                    <dd className="mt-1 text-sm leading-6 text-gray-700 sm:col-span-2 sm:mt-0">
-                      {formatter.format(new Date(dataset.metadata_modified))}
-                    </dd>
-                  </div>
-                </dl>
-              </div>
-            </div>
-          </div>
-          <div className="lg:pr-8 lg:pt-4">
-            <h2 className="text-base font-semibold leading-7 text-indigo-600">
-              Resources
-            </h2>
-            <div className="overflow-hidden bg-white shadow sm:rounded-md mt-2">
-              <ul role="list" className="divide-y divide-gray-200">
-                {dataset.resources.map((resource) => (
-                  <li key={resource.id}>
-                    <a href={resource.url} className="block hover:bg-gray-50">
-                      <div className="px-4 py-4 sm:px-6">
-                        <div className="flex items-center justify-between">
-                          <p className="truncate text-sm font-medium text-indigo-600">
-                            {resource.name}
-                          </p>
-                          {resource.datastore_active && (
-                            <div className="ml-2 flex flex-shrink-0">
-                              <p className="inline-flex rounded-full bg-green-100 px-2 text-xs font-semibold leading-5 text-green-800">
-                                Datastore active
-                              </p>
-                            </div>
-                          )}
-                        </div>
-                        <div className="mt-2 sm:flex sm:justify-between">
-                          <div className="sm:flex">
-                            <p className="flex items-center text-sm text-gray-500">
-                              <FolderOpenIcon
-                                className="mr-1.5 h-5 w-5 flex-shrink-0 text-gray-400"
-                                aria-hidden="true"
-                              />
-                              {resource.format}
-                            </p>
-                          </div>
-                          <div className="mt-2 flex items-center text-sm text-gray-500 sm:mt-0">
-                            <CalendarIcon
-                              className="mr-1.5 h-5 w-5 flex-shrink-0 text-gray-400"
-                              aria-hidden="true"
-                            />
-                            <p>
-                              Last modified:{' '}
-                              <time dateTime={resource.metadata_modified}>
-                                {formatter.format(
-                                  new Date(resource.metadata_modified)
-                                )}
-                              </time>
-                            </p>
-                          </div>
-                        </div>
-                      </div>
-                    </a>
-                  </li>
-                ))}
-              </ul>
-            </div>
-          </div>
-        </div>
-      </div>
-    </div>
-  );
-}

examples/ckan-example/pages/_app.tsx

@@ -1,18 +0,0 @@
-import { AppProps } from 'next/app';
-import Head from 'next/head';
-import './styles.css'
-
-function CustomApp({ Component, pageProps }: AppProps) {
-  return (
-    <>
-      <Head>
-        <title>Welcome to ckan-example!</title>
-      </Head>
-      <main className="app">
-        <Component {...pageProps} />
-      </main>
-    </>
-  );
-}
-
-export default CustomApp;

examples/ckan-example/pages/index.tsx

@@ -1,114 +0,0 @@
-import getConfig from 'next/config';
-import styles from './index.module.css';
-
-const dms = getConfig().publicRuntimeConfig.DMS
-
-const formatter = new Intl.DateTimeFormat('en-US', {
-  year: 'numeric',
-  month: 'long',
-  day: 'numeric',
-  hour: 'numeric',
-  minute: 'numeric',
-  second: 'numeric',
-  timeZone: 'UTC',
-});
-
-
-export async function getServerSideProps() {
-  const response = await fetch(`${dms}/api/3/action/package_search`)
-  const datasets = await response.json()
-  const datasetsWithDetails = await Promise.all(datasets.result.results.map(async (dataset) => {
-    const response = await fetch(`${dms}/api/3/action/package_show?id=` + dataset.name)
-    const json = await response.json()
-    return json.result
-  }))
-
-  return {
-    props: {
-      datasets: datasetsWithDetails
-    }
-  }
-}
-
-export function Index({ datasets }) {
-  return (
-    <div className="bg-white">
-      <div className="mx-auto max-w-7xl px-6 py-16 sm:py-24 lg:px-8">
-        <h2 className="text-2xl font-bold leading-10 tracking-tight text-indigo-500">
-          My Datasets
-        </h2>
-        <p className="mt-6 max-w-2xl text-base leading-7 text-gray-600">
-          Here is a list of all my datasets for easy access and sharing, they
-          are all available in the following{' '}
-          <a
-            href="#"
-            className="font-semibold text-indigo-600 hover:text-indigo-500"
-          >
-            CKAN Instance
-          </a>
-        </p>
-        <div className="mt-20">
-          <div className="-mx-4 -my-2 overflow-x-auto sm:-mx-6 lg:-mx-8">
-            <div className="inline-block min-w-full py-2 align-middle sm:px-6 lg:px-8">
-              <table className="min-w-full divide-y divide-gray-300">
-                <thead>
-                  <tr>
-                    <th
-                      scope="col"
-                      className="px-3 py-3.5 text-left text-sm font-semibold text-gray-900"
-                    >
-                      Title
-                    </th>
-                    <th
-                      scope="col"
-                      className="px-3 py-3.5 text-left text-sm font-semibold text-gray-900"
-                    >
-                      Description
-                    </th>
-                    <th
-                      scope="col"
-                      className="px-3 py-3.5 text-left text-sm font-semibold text-gray-900"
-                    >
-                      Last updated
-                    </th>
-                    <th
-                      scope="col"
-                      className="relative py-3.5 pl-3 pr-4 sm:pr-0"
-                    ></th>
-                  </tr>
-                </thead>
-                <tbody className="divide-y divide-gray-200">
-                  {datasets.map((dataset) => (
-                    <tr>
-                      <td className="px-3 py-4 text-sm text-gray-500">
-                          {dataset.title}
-                      </td>
-                      <td className="px-3 py-4 text-sm text-gray-500">
-                        {dataset.notes}
-                      </td>
-                      <td className="whitespace-nowrap px-3 py-4 text-sm text-gray-500">
-                        {formatter.format(
-                          new Date(dataset.metadata_modified)
-                        )}
-                      </td>
-                      <td className="relative whitespace-nowrap py-4 pl-3 pr-4 text-right text-sm font-medium sm:pr-0">
-                        <a
-                          href={`/@${dataset.organization.name}/${dataset.name}`}
-                          className="text-indigo-600 hover:text-indigo-900"
-                        >
-                          More info
-                        </a>
-                      </td>
-                    </tr>
-                  ))}
-                </tbody>
-              </table>
-            </div>
-          </div>
-        </div>
-      </div>
-    </div>
-  );
-}
-
-export default Index;

examples/ckan-example/pages/styles.css

@@ -1,3 +0,0 @@
-@tailwind base;
-@tailwind components;
-@tailwind utilities;

examples/ckan-example/postcss.config.js

@@ -1,6 +0,0 @@
-module.exports = {
-  plugins: {
-    tailwindcss: {},
-    autoprefixer: {},
-  },
-}

examples/ckan-example/tailwind.config.js

@@ -1,15 +0,0 @@
-/** @type {import('tailwindcss').Config} */
-module.exports = {
-  content: [
-    "./app/**/*.{js,ts,jsx,tsx,mdx}",
-    "./pages/**/*.{js,ts,jsx,tsx,mdx}",
-    "./components/**/*.{js,ts,jsx,tsx,mdx}",
-  ],
-  theme: {
-    extend: {},
-  },
-  plugins: [
-    require('@tailwindcss/typography')
-  ],
-}
-

examples/ckan-example/tsconfig.json

@@ -1,20 +0,0 @@
-{
-  "compilerOptions": {
-    "target": "es5",
-    "lib": ["dom", "dom.iterable", "esnext"],
-    "allowJs": true,
-    "skipLibCheck": true,
-    "strict": false,
-    "forceConsistentCasingInFileNames": true,
-    "noEmit": true,
-    "esModuleInterop": true,
-    "module": "esnext",
-    "moduleResolution": "node",
-    "resolveJsonModule": true,
-    "isolatedModules": true,
-    "jsx": "preserve",
-    "incremental": true
-  },
-  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"],
-  "exclude": ["node_modules"]
-}

examples/simple-example-e2e/.eslintrc.json

@@ -0,0 +1,10 @@
+{
+  "extends": ["plugin:cypress/recommended", "../../.eslintrc.json"],
+  "ignorePatterns": ["!**/*"],
+  "overrides": [
+    {
+      "files": ["*.ts", "*.tsx", "*.js", "*.jsx"],
+      "rules": {}
+    }
+  ]
+}

examples/simple-example-e2e/cypress.config.ts

@@ -0,0 +1,6 @@
+import { defineConfig } from 'cypress';
+import { nxE2EPreset } from '@nrwl/cypress/plugins/cypress-preset';
+
+export default defineConfig({
+  e2e: nxE2EPreset(__dirname),
+});

examples/simple-example-e2e/project.json

@@ -0,0 +1,30 @@
+{
+  "name": "simple-example-e2e",
+  "$schema": "../../node_modules/nx/schemas/project-schema.json",
+  "sourceRoot": "examples/simple-example-e2e/src",
+  "projectType": "application",
+  "targets": {
+    "e2e": {
+      "executor": "@nrwl/cypress:cypress",
+      "options": {
+        "cypressConfig": "examples/simple-example-e2e/cypress.config.ts",
+        "devServerTarget": "simple-example:serve:development",
+        "testingType": "e2e"
+      },
+      "configurations": {
+        "production": {
+          "devServerTarget": "simple-example:serve:production"
+        }
+      }
+    },
+    "lint": {
+      "executor": "@nrwl/linter:eslint",
+      "outputs": ["{options.outputFile}"],
+      "options": {
+        "lintFilePatterns": ["examples/simple-example-e2e/**/*.{js,ts}"]
+      }
+    }
+  },
+  "tags": [],
+  "implicitDependencies": ["simple-example"]
+}

examples/simple-example-e2e/src/e2e/app.cy.ts

@@ -0,0 +1,13 @@
+import { getGreeting } from '../support/app.po';
+
+describe('simple-example', () => {
+  beforeEach(() => cy.visit('/'));
+
+  it('should display welcome message', () => {
+    // Custom command example, see `../support/commands.ts` file
+    cy.login('my-email@something.com', 'myPassword');
+
+    // Function helper example, see `../support/app.po.ts` file
+    getGreeting().contains('Welcome simple-example');
+  });
+});

examples/simple-example-e2e/src/fixtures/example.json

@@ -0,0 +1,4 @@
+{
+  "name": "Using fixtures to represent data",
+  "email": "hello@cypress.io"
+}

examples/simple-example-e2e/src/support/app.po.ts

@@ -0,0 +1 @@
+export const getGreeting = () => cy.get('h1');

examples/simple-example-e2e/src/support/commands.ts

@@ -0,0 +1,33 @@
+// ***********************************************
+// This example commands.js shows you how to
+// create various custom commands and overwrite
+// existing commands.
+//
+// For more comprehensive examples of custom
+// commands please read more here:
+// https://on.cypress.io/custom-commands
+// ***********************************************
+
+// eslint-disable-next-line @typescript-eslint/no-namespace
+declare namespace Cypress {
+  // eslint-disable-next-line @typescript-eslint/no-unused-vars
+  interface Chainable<Subject> {
+    login(email: string, password: string): void;
+  }
+}
+//
+// -- This is a parent command --
+Cypress.Commands.add('login', (email, password) => {
+  console.log('Custom command example: Login', email, password);
+});
+//
+// -- This is a child command --
+// Cypress.Commands.add("drag", { prevSubject: 'element'}, (subject, options) => { ... })
+//
+//
+// -- This is a dual command --
+// Cypress.Commands.add("dismiss", { prevSubject: 'optional'}, (subject, options) => { ... })
+//
+//
+// -- This will overwrite an existing command --
+// Cypress.Commands.overwrite("visit", (originalFn, url, options) => { ... })

examples/simple-example-e2e/src/support/e2e.ts

@@ -0,0 +1,17 @@
+// ***********************************************************
+// This example support/index.js is processed and
+// loaded automatically before your test files.
+//
+// This is a great place to put global configuration and
+// behavior that modifies Cypress.
+//
+// You can change the location of this file or turn off
+// automatically serving support files with the
+// 'supportFile' configuration option.
+//
+// You can read more here:
+// https://on.cypress.io/configuration
+// ***********************************************************
+
+// Import commands.js using ES2015 syntax:
+import './commands';

examples/simple-example-e2e/tsconfig.json

@@ -0,0 +1,10 @@
+{
+  "extends": "../../tsconfig.base.json",
+  "compilerOptions": {
+    "sourceMap": false,
+    "outDir": "../../dist/out-tsc",
+    "allowJs": true,
+    "types": ["cypress", "node"]
+  },
+  "include": ["src/**/*.ts", "src/**/*.js", "cypress.config.ts"]
+}

examples/simple-example/.eslintrc.json

@@ -1,7 +1,9 @@
 {
   "extends": [
+    "plugin:@nrwl/nx/react-typescript",
     "next",
-    "next/core-web-vitals"
+    "next/core-web-vitals",
+    "../../.eslintrc.json"
   ],
   "ignorePatterns": ["!**/*", ".next/**/*"],
   "overrides": [

examples/simple-example/README.md

@@ -1,75 +0,0 @@
-This is a repo intended to serve as a simple example of a data catalog that get its data from a series of github repos, you can init an example just like this one by.
-
-- Creating a new project with `create-next-app` like so:
-
-```
-npx create-next-app <app-name> --example https://github.com/datopian/portaljs/tree/main/examples/simple-example
-cd <app-name>
-```
-
-- This project uses the github api, which for anonymous users will cap at 50 requests per hour, so you might want to get a [Personal Access Token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) and add it to a `.env` file inside the folder like so
-
-```
-GITHUB_PAT=<github token>
-```
-
-- Edit the file `datasets.json` to your liking, some examples can be found inside this [repo](https://github.com/datasets)
-- Run the app using:
-
-```
-npm run dev
-```
-
-Congratulations, you now have something similar to this running on `http://localhost:3000`
-![](https://i.imgur.com/jAljJ9C.png)
-If yo go to any one of those pages by clicking on `More info` you will see something similar to this
-![](https://i.imgur.com/AoJd4O0.png)
-
-## Deployment
-
-[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Fdatopian%2Fportaljs%2Ftree%2Fmain%2Fexamples%2Fsimple-example)
-
-By clicking on this button, you will be redirected to a page which will allow you to clone the content into your own github/gitlab/bitbucket account and automatically deploy everything.
-
-
-## Structure of `datasets.json`
-
-The `datasets.json` file is simply a list of datasets, below you can see a minimal example of a dataset
-
-```json
-{
-  "owner": "fivethirtyeight",
-  "repo": "data",
-  "branch": "master",
-  "files": ["nba-raptor/historical_RAPTOR_by_player.csv", "nba-raptor/historical_RAPTOR_by_team.csv"],
-  "readme": "nba-raptor/README.md"
-}
-```
-
-It has
-
-- A `owner` which is going to be the github repo owner
-- A `repo` which is going to be the github repo name
-- A `branch` which is going to be the branch to which we need to get the files and the readme
-- A list of `files` which is going to be a list of paths with files that you want to show to the world
-- A `readme` which is going to be the path to your data description, it can also be a subpath eg: `example/README.md`
-
-You can also add
-
-- A `description` which is useful if you have more than one dataset for each repo, if not provided we are just going to use the repo description
-- A `Name` which is useful if you want to give your dataset a nice name, if not provided we are going to use the junction of the `owner` the `repo` + the path of the README, in the exaple above it will be `fivethirtyeight/data/nba-raptor`
-
-## Extra commands
-
-You can also build the project for production with
-
-```
-npm run build
-```
-
-And run using the production build like so:
-
-```
-npm run start
-```
-

examples/simple-example/components/Footer.tsx

@@ -1,16 +0,0 @@
-export default function Footer() {
-  return (
-    <footer className="bg-white">
-      <div className="mx-auto max-w-7xl overflow-hidden px-6 py-8 sm:py-12 lg:px-8">
-        <div className="mt-10 flex justify-center space-x-10">
-          <span className="text-gray-400 hover:text-gray-500 flex gap-4 items-center">
-            <span className="mt-2">Powered by</span>
-            <a href="https://datopian.com">
-              <img src="/logo.png" className="w-32 h-10" />
-            </a>
-          </span>
-        </div>
-      </div>
-    </footer>
-  );
-}

examples/simple-example/components/MDLayout.tsx

@@ -0,0 +1,85 @@
+import FrictionlessViewFactory from "./drd/FrictionlessView";
+import Table from "./drd/Table";
+
+/* eslint import/no-default-export: off */
+function DatapackageLayout({ children, project, excerpt }) {
+  const { metadata } = project;
+
+  const title = metadata.title;
+  const resources = metadata.resources;
+  const views = metadata.views;
+
+  const FrictionlessView = FrictionlessViewFactory({ views, resources });
+
+  return (
+    <article className="docs prose text-primary dark:text-primary-dark dark:prose-invert prose-headings:font-headings prose-a:break-words mx-auto p-6">
+      <header>
+        {title && <h1 className="mb-4">{title}</h1>}
+        <a
+          className="font-semibold mb-4"
+          target="_blank"
+          href={project.github_repo}
+        >
+          @{project.owner} / {project.name}
+        </a>
+        {excerpt && <p className="text-md">{excerpt}</p>}
+      </header>
+      <section className="mt-10">
+        {views.map((view, i) => {
+          return (
+            <div key={`visualization-${i}`}>
+              <FrictionlessView viewId={i} />
+            </div>
+          );
+        })}
+      </section>
+      <section className="mt-10">
+        <h2>Data files</h2>
+        <table className="table-auto">
+          <thead>
+            <tr>
+              <th>File</th>
+              <th>Title</th>
+              <th>Format</th>
+            </tr>
+          </thead>
+          <tbody>
+            {resources.map((r) => {
+              return (
+                <tr key={`resources-list-${r.name}`}>
+                  <td>
+                    <a
+                      target="_blank"
+                      href={`https://github.com/${project.owner}/${project.name}/blob/main/${r.path}`}
+                    >
+                      {r.path}
+                    </a>
+                  </td>
+                  <td>{r.title}</td>
+                  <td>{r.format.toUpperCase()}</td>
+                </tr>
+              );
+            })}
+          </tbody>
+        </table>
+        {resources.slice(0, 5).map((resource) => {
+          return (
+            <div key={`resource-preview-${resource.name}`} className="mt-10">
+              <h3>{resource.title || resource.name || resource.path}</h3>
+              <Table url={resource.path} />
+            </div>
+          );
+        })}
+      </section>
+      <hr />
+      <section>
+        <h2>Read me</h2>
+        {children}
+      </section>
+    </article>
+  );
+}
+
+export default function MDLayout({ children, layout, ...props }) {
+  return <DatapackageLayout project={props.project} excerpt={props.excerpt}>{children}</DatapackageLayout>;
+}

examples/simple-example/components/NavBar.tsx

@@ -1,31 +0,0 @@
-export default function NavBar() {
-  return (
-    <div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
-      <div className="flex h-16 justify-between">
-        <div className="flex">
-          <div className="flex flex-shrink-0 items-center">
-            <img
-              className="block h-8 w-auto lg:hidden"
-              src="/logo.png"
-              alt="Your Company"
-            />
-            <img
-              className="hidden h-8 w-auto lg:block mt-4"
-              src="/logo.png"
-              alt="Your Company"
-            />
-          </div>
-          <div className="hidden sm:ml-6 sm:flex sm:space-x-8">
-            {/* Current: "border-indigo-500 text-gray-900", Default: "border-transparent text-gray-500 hover:border-gray-300 hover:text-gray-700" */}
-            <a
-              href="/"
-              className="inline-flex items-center border-b-2 border-indigo-500 px-1 pt-1 text-sm font-medium text-gray-900"
-            >
-              Home
-            </a>
-          </div>
-        </div>
-      </div>
-    </div>
-  );
-}

examples/simple-example/components/drd/DRD.tsx

@@ -0,0 +1,40 @@
+import { MDXRemote } from "next-mdx-remote";
+import dynamic from "next/dynamic";
+import { Mermaid } from "@flowershow/core";
+
+import FrictionlessViewFactory from "./FrictionlessView";
+
+// Custom components/renderers to pass to MDX.
+// Since the MDX files aren't loaded by webpack, they have no knowledge of how
+// to handle import statements. Instead, you must include components in scope
+// here.
+const components = {
+  Table: dynamic(() => import("./Table")),
+  mermaid: Mermaid,
+  // Excel: dynamic(() => import('../components/Excel')),
+  // TODO: try and make these dynamic ...
+  Vega: dynamic(() => import("./Vega")),
+  VegaLite: dynamic(() => import("./VegaLite")),
+  LineChart: dynamic(() => import("./LineChart")),
+} as any;
+
+export default function DRD({
+  source,
+  frictionless = {
+    views: [],
+    resources: [],
+  },
+}: {
+  source: any;
+  frictionless?: any;
+}) {
+  //  dynamic() can't be used inside of React rendering
+  //  as it needs to be marked in the top level of the
+  //  module for preloading to work
+  components.FrictionlessView = FrictionlessViewFactory({
+    views: frictionless.views,
+    resources: frictionless.resources,
+  });
+
+  return <MDXRemote {...source} components={components} />;
+}

examples/simple-example/components/drd/DebouncedInput.tsx

@@ -0,0 +1,33 @@
+import { useEffect, useState } from "react";
+
+const DebouncedInput = ({
+  value: initialValue,
+  onChange,
+  debounce = 500,
+  ...props
+}) => {
+  const [value, setValue] = useState(initialValue);
+
+  useEffect(() => {
+    setValue(initialValue);
+  }, [initialValue]);
+
+  useEffect(() => {
+    const timeout = setTimeout(() => {
+      onChange(value);
+    }, debounce);
+
+    return () => clearTimeout(timeout);
+  }, [value]);
+
+  return (
+    <input
+      {...props}
+      value={value}
+      onChange={(e) => setValue(e.target.value)}
+    />
+  );
+};
+
+export default DebouncedInput;
+

examples/simple-example/components/drd/FrictionlessView.tsx

@@ -0,0 +1,55 @@
+// FrictionlessView is a factory because we have to
+// set the views and resources lists before using it
+
+import { convertSimpleToVegaLite } from "../../lib/viewSpecConversion";
+import VegaLite from "./VegaLite";
+
+export default function FrictionlessViewFactory({
+  views = [],
+  resources = [],
+}): ({
+  viewId,
+  fullWidth,
+}: {
+  viewId: number;
+  fullWidth?: boolean;
+}) => JSX.Element {
+  return ({ viewId, fullWidth = false }) => {
+    if (!(viewId in views)) {
+      console.error(`View ${viewId} not found`);
+      return <></>;
+    }
+    const view = views[viewId];
+
+    let resource;
+    if (resources.length > 1) {
+      resource = resources.find((r) => r.name === view.resourceName);
+    } else {
+      resource = resources[0];
+    }
+
+    if (!resource) {
+      console.error(`Resource not found for view id ${viewId}`);
+      return <></>;
+    }
+
+    let vegaSpec;
+    switch (view.specType) {
+      case "simple":
+        vegaSpec = convertSimpleToVegaLite(view, resource);
+        break;
+      // ... other conversions
+    }
+
+    vegaSpec.data = { url: resource.path };
+
+    return (
+      <VegaLite
+        fullWidth={fullWidth}
+        spec={vegaSpec}
+        actions={{ editor: false }}
+        downloadFileName={resource.name}
+      />
+    );
+  };
+}

examples/simple-example/components/drd/LineChart.tsx

@@ -0,0 +1,49 @@
+import { VegaLite } from "react-vega";
+
+export default function LineChart({
+  data = [],
+  fullWidth = false,
+  title = "",
+}) {
+  var tmp = data;
+  if (Array.isArray(data)) {
+    tmp = data.map((r, i) => {
+      return { x: r[0], y: r[1] };
+    });
+  }
+  const vegaData = { table: tmp };
+  const spec = {
+    $schema: "https://vega.github.io/schema/vega-lite/v5.json",
+    title,
+    width: "container" as "container",
+    height: 300,
+    mark: {
+      type: "line" as "line",
+      color: "black",
+      strokeWidth: 1,
+      tooltip: true,
+    },
+    data: {
+      name: "table",
+    },
+    selection: {
+      grid: {
+        type: "interval" as "interval",
+        bind: "scales",
+      },
+    },
+    encoding: {
+      x: {
+        field: "x",
+        timeUnit: "year",
+        type: "temporal" as "temporal",
+      },
+      y: {
+        field: "y",
+        type: "quantitative" as "temporal",
+      },
+    },
+  };
+
+  return <VegaLite data={vegaData} spec={spec} />;
+}

examples/simple-example/components/drd/Table.tsx

@@ -0,0 +1,188 @@
+import {
+  createColumnHelper,
+  FilterFn,
+  flexRender,
+  getCoreRowModel,
+  getFilteredRowModel,
+  getPaginationRowModel,
+  getSortedRowModel,
+  useReactTable,
+} from "@tanstack/react-table";
+
+import {
+  ArrowDownIcon,
+  ArrowUpIcon,
+  ChevronDoubleLeftIcon,
+  ChevronDoubleRightIcon,
+  ChevronLeftIcon,
+  ChevronRightIcon,
+} from "@heroicons/react/24/solid";
+
+import React, { useEffect, useMemo, useState } from "react";
+
+import loadUrlProxied from "../../lib/loadUrlProxied";
+import parseCsv from "../../lib/parseCsv";
+import DebouncedInput from "./DebouncedInput";
+
+const Table = ({
+  data: ogData = [],
+  cols: ogCols = [],
+  csv = "",
+  url = "",
+}) => {
+  if (csv) {
+    const out = parseCsv(csv);
+    ogData = out.rows;
+    ogCols = out.fields;
+  }
+
+  const [data, setData] = React.useState(ogData);
+  const [cols, setCols] = React.useState(ogCols);
+  const [error, setError] = React.useState(""); //  TODO: add error handling
+
+  const tableCols = useMemo(() => {
+    const columnHelper = createColumnHelper();
+    return cols.map((c) =>
+      columnHelper.accessor(c.key, {
+        header: () => c.name,
+        cell: (info) => info.getValue(),
+      })
+    );
+  }, [data, cols]);
+
+  const [globalFilter, setGlobalFilter] = useState("");
+
+  const table = useReactTable({
+    data,
+    columns: tableCols,
+    getCoreRowModel: getCoreRowModel(),
+    state: {
+      globalFilter,
+    },
+    globalFilterFn: globalFilterFn,
+    onGlobalFilterChange: setGlobalFilter,
+    getFilteredRowModel: getFilteredRowModel(),
+    getPaginationRowModel: getPaginationRowModel(),
+    getSortedRowModel: getSortedRowModel(),
+  });
+
+  useEffect(() => {
+    if (url) {
+      loadUrlProxied(url).then((data) => {
+        const { rows, fields } = parseCsv(data);
+        setData(rows);
+        setCols(fields);
+      });
+    }
+  }, [url]);
+
+  return (
+    <div>
+      <DebouncedInput
+        value={globalFilter ?? ""}
+        onChange={(value) => setGlobalFilter(String(value))}
+        className="p-2 text-sm shadow border border-block"
+        placeholder="Search all columns..."
+      />
+      <table>
+        <thead>
+          {table.getHeaderGroups().map((hg) => (
+            <tr key={hg.id}>
+              {hg.headers.map((h) => (
+                <th key={h.id}>
+                  <div
+                    {...{
+                      className: h.column.getCanSort()
+                        ? "cursor-pointer select-none"
+                        : "",
+                      onClick: h.column.getToggleSortingHandler(),
+                    }}
+                  >
+                    {flexRender(h.column.columnDef.header, h.getContext())}
+                    {{
+                      asc: (
+                        <ArrowUpIcon className="inline-block ml-2 h-4 w-4" />
+                      ),
+                      desc: (
+                        <ArrowDownIcon className="inline-block ml-2 h-4 w-4" />
+                      ),
+                    }[h.column.getIsSorted() as string] ?? (
+                      <div className="inline-block ml-2 h-4 w-4" />
+                    )}
+                  </div>
+                </th>
+              ))}
+            </tr>
+          ))}
+        </thead>
+        <tbody>
+          {table.getRowModel().rows.map((r) => (
+            <tr key={r.id}>
+              {r.getVisibleCells().map((c) => (
+                <td key={c.id}>
+                  {flexRender(c.column.columnDef.cell, c.getContext())}
+                </td>
+              ))}
+            </tr>
+          ))}
+        </tbody>
+      </table>
+      <div className="flex gap-2 items-center justify-center">
+        <button
+          className={`w-6 h-6 ${
+            !table.getCanPreviousPage() ? "opacity-25" : "opacity-100"
+          }`}
+          onClick={() => table.setPageIndex(0)}
+          disabled={!table.getCanPreviousPage()}
+        >
+          <ChevronDoubleLeftIcon />
+        </button>
+        <button
+          className={`w-6 h-6 ${
+            !table.getCanPreviousPage() ? "opacity-25" : "opacity-100"
+          }`}
+          onClick={() => table.previousPage()}
+          disabled={!table.getCanPreviousPage()}
+        >
+          <ChevronLeftIcon />
+        </button>
+        <span className="flex items-center gap-1">
+          <div>Page</div>
+          <strong>
+            {table.getState().pagination.pageIndex + 1} of{" "}
+            {table.getPageCount()}
+          </strong>
+        </span>
+        <button
+          className={`w-6 h-6 ${
+            !table.getCanNextPage() ? "opacity-25" : "opacity-100"
+          }`}
+          onClick={() => table.nextPage()}
+          disabled={!table.getCanNextPage()}
+        >
+          <ChevronRightIcon />
+        </button>
+        <button
+          className={`w-6 h-6 ${
+            !table.getCanNextPage() ? "opacity-25" : "opacity-100"
+          }`}
+          onClick={() => table.setPageIndex(table.getPageCount() - 1)}
+          disabled={!table.getCanNextPage()}
+        >
+          <ChevronDoubleRightIcon />
+        </button>
+      </div>
+    </div>
+  );
+};
+
+const globalFilterFn: FilterFn<any> = (row, columnId, filterValue: string) => {
+  const search = filterValue.toLowerCase();
+
+  let value = row.getValue(columnId) as string;
+  if (typeof value === "number") value = String(value);
+
+  return value?.toLowerCase().includes(search);
+};
+
+export default Table;

examples/simple-example/components/drd/Vega.tsx

@@ -0,0 +1,4 @@
+import { Vega as VegaOg } from "react-vega";
+export default function Vega(props) {
+  return <VegaOg className="w-full" {...props} />;
+}

examples/simple-example/components/drd/VegaLite.tsx

@@ -0,0 +1,4 @@
+import { VegaLite as VegaOg } from "react-vega";
+export default function Vega(props) {
+  return <VegaOg  className="w-full" {...props} />;
+}

examples/simple-example/datasets.json

@@ -1,44 +1,7 @@
 [
-  {
-    "owner": "datasets",
-    "branch": "main",
-    "repo": "oil-prices",
-    "files": [
-      "data/brent-daily.csv",
-      "data/brent-monthly.csv",
-      "data/brent-weekly.csv",
-      "data/brent-year.csv",
-      "data/wti-daily.csv",
-      "data/wti-monthly.csv",
-      "data/wti-weekly.csv",
-      "data/wti-year.csv"
-    ],
-    "readme": "README.md"
-  },
-  {
-    "owner": "datasets",
-    "branch": "main",
-    "repo": "investor-flow-of-funds-us",
-    "files": [
-      "data/monthly.csv",
-      "data/weekly.csv"
-    ],
-    "readme": "README.md"
-  },
-  {
-    "owner": "fivethirtyeight",
-    "repo": "data",
-    "branch": "master",
-    "description": "Data about bad drivers",
-    "name": "Bad Drivers",
-    "files": ["bad-drivers/bad-drivers.csv"],
-    "readme": "bad-drivers/README.md"
-  },
-  {
-    "owner": "fivethirtyeight",
-    "repo": "data",
-    "branch": "master",
-    "files": ["nba-raptor/historical_RAPTOR_by_player.csv", "nba-raptor/historical_RAPTOR_by_team.csv"],
-    "readme": "nba-raptor/README.md"
-  }
+  { "owner": "datasets", "repo": "oil-prices"},
+  { "owner": "datasets", "repo": "investor-flow-of-funds-us"},
+  { "owner": "datasets", "repo": "browser-stats"},
+  { "owner": "datasets", "repo": "glacier-mass-balance"},
+  { "owner": "datasets", "repo": "bond-yields-us-10y"}
 ]

examples/simple-example/jest.config.ts

@@ -1,11 +1,11 @@
 /* eslint-disable */
 export default {
-  displayName: 'ckan-example',
+  displayName: 'simple-example',
   preset: '../../jest.preset.js',
   transform: {
     '^(?!.*\\.(js|jsx|ts|tsx|css|json)$)': '@nrwl/react/plugins/jest',
     '^.+\\.[tj]sx?$': ['babel-jest', { presets: ['@nrwl/next/babel'] }],
   },
   moduleFileExtensions: ['ts', 'tsx', 'js', 'jsx'],
-  coverageDirectory: '../../coverage/examples/ckan-example',
+  coverageDirectory: '../../coverage/examples/simple-example',
 };

examples/simple-example/lib/loadUrlProxied.tsx

@@ -0,0 +1,11 @@
+import axios from "axios";
+
+export default function loadUrlProxied(url: string) {
+  // HACK: duplicate of Excel code - maybe refactor
+  // if url is external may have CORS issue so we proxy it ...
+  if (url.startsWith("http")) {
+    const PROXY_URL = "/api/proxy";
+    url = PROXY_URL + "?url=" + encodeURIComponent(url);
+  }
+  return axios.get(url).then((res) => res.data);
+}

examples/simple-example/lib/markdown.js

@@ -0,0 +1,105 @@
+import matter from "gray-matter";
+import mdxmermaid from "mdx-mermaid";
+import { h } from "hastscript";
+import remarkCallouts from "@flowershow/remark-callouts";
+import remarkEmbed from "@flowershow/remark-embed";
+import remarkGfm from "remark-gfm";
+import remarkMath from "remark-math";
+import remarkSmartypants from "remark-smartypants";
+import remarkToc from "remark-toc";
+import remarkWikiLink from "@flowershow/remark-wiki-link";
+import rehypeAutolinkHeadings from "rehype-autolink-headings";
+import rehypeKatex from "rehype-katex";
+import rehypeSlug from "rehype-slug";
+import rehypePrismPlus from "rehype-prism-plus";
+
+import { serialize } from "next-mdx-remote/serialize";
+
+/**
+ * Parse a markdown or MDX file to an MDX source form + front matter data
+ *
+ * @source: the contents of a markdown or mdx file
+ * @format: used to indicate to next-mdx-remote which format to use (md or mdx)
+ * @returns: { mdxSource: mdxSource, frontMatter: ...}
+ */
+const parse = async function (source, format) {
+  const { content, data, excerpt } = matter(source, {
+    excerpt: (file, options) => {
+      // Generate an excerpt for the file
+      file.excerpt = file.content.split("\n\n")[0];
+    },
+  });
+
+  const mdxSource = await serialize(
+    { value: content, path: format },
+    {
+      // Optionally pass remark/rehype plugins
+      mdxOptions: {
+        remarkPlugins: [
+          remarkEmbed,
+          remarkGfm,
+          [remarkSmartypants, { quotes: false, dashes: "oldschool" }],
+          remarkMath,
+          remarkCallouts,
+          remarkWikiLink,
+          [
+            remarkToc,
+            {
+              heading: "Table of contents",
+              tight: true,
+            },
+          ],
+          [mdxmermaid, {}],
+        ],
+        rehypePlugins: [
+          rehypeSlug,
+          [
+            rehypeAutolinkHeadings,
+            {
+              properties: { className: 'heading-link' },
+              test(element) {
+                return (
+                  ["h2", "h3", "h4", "h5", "h6"].includes(element.tagName) &&
+                  element.properties?.id !== "table-of-contents" &&
+                  element.properties?.className !== "blockquote-heading"
+                );
+              },
+              content() {
+                return [
+                  h(
+                    "svg",
+                    {
+                      xmlns: "http:www.w3.org/2000/svg",
+                      fill: "#ab2b65",
+                      viewBox: "0 0 20 20",
+                      className: "w-5 h-5",
+                    },
+                    [
+                      h("path", {
+                        fillRule: "evenodd",
+                        clipRule: "evenodd",
+                        d: "M9.493 2.853a.75.75 0 00-1.486-.205L7.545 6H4.198a.75.75 0 000 1.5h3.14l-.69 5H3.302a.75.75 0 000 1.5h3.14l-.435 3.148a.75.75 0 001.486.205L7.955 14h2.986l-.434 3.148a.75.75 0 001.486.205L12.456 14h3.346a.75.75 0 000-1.5h-3.14l.69-5h3.346a.75.75 0 000-1.5h-3.14l.435-3.147a.75.75 0 00-1.486-.205L12.045 6H9.059l.434-3.147zM8.852 7.5l-.69 5h2.986l.69-5H8.852z",
+                      }),
+                    ]
+                  ),
+                ];
+              },
+            },
+          ],
+          [rehypeKatex, { output: "mathml" }],
+          [rehypePrismPlus, { ignoreMissing: true }],
+        ],
+        format,
+      },
+      scope: data,
+    }
+  );
+
+  return {
+    mdxSource: mdxSource,
+    frontMatter: data,
+    excerpt,
+  };
+};
+
+export default parse;

examples/simple-example/lib/octokit.ts

@@ -1,147 +0,0 @@
-import { Octokit } from 'octokit';
-
-export interface GithubProject {
-  owner: string;
-  repo: string;
-  branch: string;
-  files: string[];
-  readme: string;
-  description?: string;
-  name?: string;
-}
-
-export async function getProjectReadme(
-  owner: string,
-  repo: string,
-  branch: string,
-  readme: string,
-  github_pat?: string
-) {
-  const octokit = new Octokit({ auth: github_pat });
-  try {
-    const response = await octokit.rest.repos.getContent({
-      owner,
-      repo,
-      path: readme,
-      ref: branch,
-    });
-    const data = response.data as { content?: string };
-    const fileContent = data.content ? data.content : '';
-    if (fileContent === '') {
-      return null;
-    }
-    const decodedContent = Buffer.from(fileContent, 'base64').toString();
-    return decodedContent;
-  } catch (error) {
-    console.log(error);
-    return null;
-  }
-}
-
-export async function getLastUpdated(
-  owner: string,
-  repo: string,
-  branch: string,
-  readme: string,
-  github_pat?: string
-) {
-  const octokit = new Octokit({ auth: github_pat });
-  try {
-    const response = await octokit.rest.repos.listCommits({
-      owner,
-      repo,
-      path: readme,
-      ref: branch,
-    });
-    return response.data[0].commit.committer.date;
-  } catch (error) {
-    console.log(error);
-    return null;
-  }
-}
-export async function getProjectMetadata(
-  owner: string,
-  repo: string,
-  github_pat?: string
-) {
-  const octokit = new Octokit({ auth: github_pat });
-  try {
-    const response = await octokit.rest.repos.get({
-      owner,
-      repo,
-    });
-    return response.data;
-  } catch (error) {
-    console.log(error);
-    return null;
-  }
-}
-
-export async function getRepoContents(
-  owner: string,
-  repo: string,
-  branch: string,
-  files: string[],
-  github_pat?: string
-) {
-  const octokit = new Octokit({ auth: github_pat });
-  try {
-    const contents = [];
-    for (const path of files) {
-      const response = await octokit.rest.repos.getContent({
-        owner,
-        repo,
-        ref: branch,
-        path: path,
-      });
-      const data = response.data as { download_url?: string, name: string, size: number };
-      contents.push({ download_url: data.download_url, name: data.name, size: data.size});
-    }
-    return contents;
-  } catch (error) {
-    console.log(error);
-    return null;
-  }
-}
-
-export async function getProject(project: GithubProject, github_pat?: string) {
-  const projectMetadata = await getProjectMetadata(
-    project.owner,
-    project.repo,
-    github_pat
-  );
-  if (!projectMetadata) {
-    return null;
-  }
-  const projectReadme = await getProjectReadme(
-    project.owner,
-    project.repo,
-    project.branch,
-    project.readme,
-    github_pat
-  );
-  if (!projectReadme) {
-    return null;
-  }
-  const projectData = await getRepoContents(
-    project.owner,
-    project.repo,
-    project.branch,
-    project.files,
-    github_pat
-  );
-  if (!projectData) {
-    return null;
-  }
-  const projectBase = project.readme.split('/').length > 1
-      ? project.readme.split('/').slice(0, -1).join('/')
-      : '/'
-  const last_updated = await getLastUpdated(
-    project.owner,
-    project.repo,
-    project.branch,
-    projectBase,
-    github_pat
-  );
-  return { ...projectMetadata, files: projectData, readmeContent: projectReadme, last_updated, base_path: projectBase };
-}

examples/simple-example/lib/parseCsv.ts

@@ -0,0 +1,16 @@
+import papa from "papaparse";
+
+const parseCsv = (csv) => {
+  csv = csv.trim();
+  const rawdata = papa.parse(csv, { header: true });
+  const cols = rawdata.meta.fields.map((r, i) => {
+    return { key: r, name: r };
+  });
+
+  return {
+    rows: rawdata.data,
+    fields: cols,
+  };
+};
+
+export default parseCsv;

examples/simple-example/lib/project.ts

@@ -0,0 +1,60 @@
+import * as crypto from "crypto";
+import axios from "axios";
+import { Octokit } from "octokit"
+
+export default class Project {
+  id: string;
+  name: string;
+  owner: string;
+  github_repo: string;
+  readme: string;
+  metadata: any;
+  repo_metadata: any;
+
+  constructor(owner: string, name: string) {
+    this.name = name;
+    this.owner = owner;
+    this.github_repo = `https://github.com/${owner}/${name}`;
+
+    //  TODO: using the GitHub repo to set the id is not a good idea
+    //  since repos can be renamed and then we are going to end up with
+    //  a duplicate
+    const encodedGHRepo = Buffer.from(this.github_repo, "utf-8").toString();
+    this.id = crypto.createHash("sha1").update(encodedGHRepo).digest("hex");
+  }
+
+  initFromGitHub = async () => {
+    const octokit = new Octokit()
+    //  TODO: what if the repo doesn't exist?
+    await this.getFileContent("README.md")
+      .then((content) => (this.readme = content))
+      .catch((e) => (this.readme = null));
+
+    await this.getFileContent("datapackage.json")
+      .then((content) => (this.metadata = content))
+      .catch((e) => (this.metadata = {}));
+
+    const github_metadata = await octokit.rest.repos.get({ owner: this.owner, repo: this.name })
+    this.repo_metadata = github_metadata.data ? github_metadata.data : null
+  };
+
+  getFileContent = (path, branch = "main") => {
+    return axios
+      .get(
+        `https://raw.githubusercontent.com/${this.owner}/${this.name}/${branch}/${path}`
+      )
+      .then((res) => res.data);
+  };
+
+  serialize() {
+    return JSON.parse(JSON.stringify(this));
+  }
+
+  static async getFromGitHub(owner: string, name: string) {
+    const project = new Project(owner, name);
+    await project.initFromGitHub();
+
+    return project;
+  }
+}
+

examples/simple-example/lib/viewSpecConversion.ts

@@ -0,0 +1,47 @@
+export function convertSimpleToVegaLite(view, resource) {
+  const x = resource.schema.fields.find((f) => f.name === view.spec.group);
+  const y = resource.schema.fields.find((f) => f.name === view.spec.series[0]);
+
+  const xType = inferVegaType(x.type);
+  const yType = inferVegaType(y.type);
+
+  let vegaLiteSpec = {
+    $schema: "https://vega.github.io/schema/vega-lite/v5.json",
+    mark: {
+      type: view.spec.type,
+      color: "black",
+      strokeWidth: 1,
+      tooltip: true,
+    },
+    title: view.title,
+    width: 500,
+    height: 300,
+    selection: {
+      grid: {
+        type: "interval",
+        bind: "scales",
+      },
+    },
+    encoding: {
+      x: {
+        field: x.name,
+        type: xType,
+      },
+      y: {
+        field: y.name,
+        type: yType,
+      },
+    },
+  };
+
+  return vegaLiteSpec;
+}
+
+const inferVegaType = (fieldType) => {
+  switch (fieldType) {
+    case "date":
+      return "Temporal";
+    case "number":
+      return "Quantitative";
+  }
+};

examples/simple-example/next.config.js

@@ -1,7 +1,23 @@
+// eslint-disable-next-line @typescript-eslint/no-var-requires
+const { withNx } = require('@nrwl/next/plugins/with-nx');
+
+/**
+ * @type {import('@nrwl/next/plugins/with-nx').WithNxOptions}
+ **/
 const nextConfig = {
   async rewrites() {
     return {
       beforeFiles: [
+        {
+          source: "/@org/:org/:project/:file(\.\+\\\.\.\+\$)",
+          destination:
+            '/api/proxy?url=https://raw.githubusercontent.com/:org/:project/main/:file',
+        },
+        {
+          source: "/@:org/:project/:file(\.\+\\\.\.\+\$)",
+          destination:
+            '/api/proxy?url=https://raw.githubusercontent.com/:org/:project/main/:file',
+        },
         {
           source: '/@:org/:project*',
           destination: '/@org/:org/:project*',
@@ -9,9 +25,11 @@ const nextConfig = {
       ],
     };
   },
-  serverRuntimeConfig: {
-    github_pat: process.env.GITHUB_PAT ? process.env.GITHUB_PAT : null,
+  nx: {
+    // Set this to true if you would like to use SVGR
+    // See: https://github.com/gregberge/svgr
+    svgr: true,
   },
 };
 
-module.exports = nextConfig;
+module.exports = withNx(nextConfig);

examples/simple-example/package.json

@@ -1,32 +0,0 @@
-{
-  "name": "my-app",
-  "version": "0.1.0",
-  "private": true,
-  "scripts": {
-    "dev": "next dev",
-    "build": "next build",
-    "start": "next start",
-    "lint": "next lint"
-  },
-  "dependencies": {
-    "@types/node": "18.16.0",
-    "@types/react": "18.0.38",
-    "@types/react-dom": "18.0.11",
-    "eslint": "8.39.0",
-    "eslint-config-next": "13.3.1",
-    "next": "13.3.1",
-    "next-seo": "^6.0.0",
-    "octokit": "^2.0.14",
-    "react": "18.2.0",
-    "react-dom": "18.2.0",
-    "react-markdown": "^8.0.7",
-    "remark-gfm": "^3.0.1",
-    "typescript": "5.0.4"
-  },
-  "devDependencies": {
-    "@tailwindcss/typography": "^0.5.9",
-    "autoprefixer": "^10.4.14",
-    "postcss": "^8.4.23",
-    "tailwindcss": "^3.3.1"
-  }
-}

examples/simple-example/pages/@org/[org]/[...path].tsx

@@ -1,141 +0,0 @@
-import Head from 'next/head';
-import { useRouter } from 'next/router';
-
-import { NextSeo } from 'next-seo';
-import { promises as fs } from 'fs';
-import path from 'path';
-import getConfig from 'next/config';
-import { getProject, GithubProject } from '../../../lib/octokit';
-import ReactMarkdown from 'react-markdown';
-import remarkGfm from 'remark-gfm';
-import Link from 'next/link';
-import Footer from '../../../components/Footer';
-import NavBar from '../../../components/NavBar';
-
-export default function ProjectPage({ project }) {
-  return (
-    <>
-      <NextSeo
-        title={`PortalJS - @${project.repo_config.owner}/${
-          project.repo_config.repo
-        }${project.base_path !== '/' ? '/' + project.base_path : ''}`}
-      />
-      <NavBar />
-      <main className="mx-auto my-8 max-w-7xl sm:px-6 lg:px-8 px-4">
-        <div className="prose">
-          <h1 className="mb-0">Data</h1>
-        </div>
-        <div className="inline-block min-w-full py-4 align-middle">
-          <div className="overflow-hidden shadow ring-1 ring-black ring-opacity-5 sm:rounded-lg">
-            <table className="min-w-full divide-y divide-gray-300">
-              <thead className="bg-gray-50">
-                <tr>
-                  <th
-                    scope="col"
-                    className="py-3.5 pl-4 pr-3 text-left text-sm font-semibold text-gray-900 sm:pl-6"
-                  >
-                    Name
-                  </th>
-                  <th
-                    scope="col"
-                    className="px-3 py-3.5 text-left text-sm font-semibold text-gray-900"
-                  >
-                    Size
-                  </th>
-                  <th
-                    scope="col"
-                    className="px-3 py-3.5 text-left text-sm font-semibold text-gray-900"
-                  >
-                    Download
-                  </th>
-                </tr>
-              </thead>
-              <tbody className="divide-y divide-gray-200 bg-white">
-                {project.files.map((file) => (
-                  <tr key={file.download_url}>
-                    <td className="py-4 pl-4 pr-3 text-sm font-medium text-gray-900 sm:pl-6">
-                      {file.name}
-                    </td>
-                    <td className="whitespace-nowrap px-3 py-4 text-sm text-gray-500">
-                      {file.size} Bytes
-                    </td>
-                    <td className="px-3 py-4 text-sm text-gray-500">
-                      <a
-                        className="rounded-md bg-indigo-600 no-underline px-2.5 py-1.5 text-sm font-semibold text-white shadow-sm hover:bg-indigo-500 focus-visible:outline focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-indigo-600"
-                        href={file.download_url}
-                      >
-                        Download file
-                      </a>
-                    </td>
-                  </tr>
-                ))}
-              </tbody>
-            </table>
-          </div>
-        </div>
-
-        <div className="prose py-4 max-w-7xl">
-          <h1>Readme</h1>
-          <ReactMarkdown remarkPlugins={[remarkGfm]}>
-            {project.readmeContent}
-          </ReactMarkdown>
-        </div>
-      </main>
-      <Footer />
-    </>
-  );
-}
-
-// Generates `/posts/1` and `/posts/2`
-export async function getStaticPaths() {
-  const jsonDirectory = path.join(process.cwd(), 'datasets.json');
-  const repos = await fs.readFile(jsonDirectory, 'utf8');
-
-  return {
-    paths: JSON.parse(repos).map((repo) => {
-      const projectPath =
-        repo.readme.split('/').length > 1
-          ? repo.readme.split('/').slice(0, -1)
-          : null;
-      let path = [repo.repo];
-      if (projectPath) {
-        projectPath.forEach((element) => {
-          path.push(element);
-        });
-      }
-      return {
-        params: { org: repo.owner, path },
-      };
-    }),
-    fallback: false, // can also be true or 'blocking'
-  };
-}
-
-export async function getStaticProps({ params }) {
-  const jsonDirectory = path.join(process.cwd(), 'datasets.json');
-  const reposFile = await fs.readFile(jsonDirectory, 'utf8');
-  const repos: GithubProject[] = JSON.parse(reposFile);
-  const repo = repos.find((_repo) => {
-    const projectPath =
-      _repo.readme.split('/').length > 1
-        ? _repo.readme.split('/').slice(0, -1)
-        : null;
-    let path = [_repo.repo];
-    if (projectPath) {
-      projectPath.forEach((element) => {
-        path.push(element);
-      });
-    }
-    return (
-      _repo.owner == params.org &&
-      JSON.stringify(path) === JSON.stringify(params.path)
-    );
-  });
-  const github_pat = getConfig().serverRuntimeConfig.github_pat;
-  const project = await getProject(repo, github_pat);
-  return {
-    props: {
-      project: { ...project, repo_config: repo },
-    },
-  };
-}

examples/simple-example/pages/@org/[org]/[project]/index.tsx

@@ -0,0 +1,110 @@
+import Head from 'next/head';
+import { useRouter } from 'next/router';
+
+import DRD from '../../../../components/drd/DRD';
+import parse from '../../../../lib/markdown';
+import Project from '../../../../lib/project';
+import { NextSeo } from 'next-seo';
+import MDLayout from 'examples/simple-example/components/MDLayout';
+import { promises as fs } from 'fs';
+import path from 'path';
+
+function CollectionsLayout({ children, ...frontMatter }) {
+  const { title, date, description } = frontMatter;
+
+  return (
+    <article className="docs prose text-primary dark:text-primary-dark dark:prose-invert prose-headings:font-headings prose-a:break-words mx-auto p-6">
+      <header>
+        <div className="mb-6">
+          {date && (
+            <p className="text-sm text-zinc-400 dark:text-zinc-500">
+              <time dateTime={date}>{date}</time>
+            </p>
+          )}
+          {title && <h1 className="mb-2">{title}</h1>}
+          {description && <p className="text-xl mt-0">{description}</p>}
+        </div>
+      </header>
+      <section>{children}</section>
+    </article>
+  );
+}
+
+export default function ProjectPage({
+  mdxSource,
+  frontMatter,
+  excerpt,
+  project,
+}) {
+  const router = useRouter();
+
+  return (
+    <>
+      <NextSeo title={`PortalJS - @${project.owner}/${project.name}`} />
+      <Head>
+        {/* 
+          On index files, add trailling slash to the base path 
+          see notes: https://github.com/datopian/datahub-next/issues/69
+        */}
+        <base href={router.asPath.split('#')[0] + '/'} />
+      </Head>
+      <main>
+        <MDLayout
+          layout={frontMatter.layout}
+          excerpt={excerpt}
+          project={project}
+          {...frontMatter}
+        >
+          <DRD
+            source={mdxSource}
+            frictionless={{
+              views: project.metadata?.views,
+              resources: project.metadata?.resources,
+            }}
+          />
+        </MDLayout>
+      </main>
+    </>
+  );
+}
+
+// Generates `/posts/1` and `/posts/2`
+export async function getStaticPaths() {
+  const jsonDirectory = path.join(process.cwd(), '/examples/simple-example/datasets.json');
+  const repos = await fs.readFile(jsonDirectory, 'utf8');
+
+  return {
+    paths: JSON.parse(repos).map(repo => ({ params: { org: repo.owner, project: repo.repo}})),
+    fallback: false, // can also be true or 'blocking'
+  }
+}
+
+export async function getStaticProps({ params }) {
+  const { org: orgName, project: projectName } = params;
+
+  const project = await Project.getFromGitHub(orgName, projectName);
+
+  //  Defaults to README
+  let content = project.readme;
+
+  if (content === null) {
+    return {
+      notFound: true,
+    };
+  }
+
+  let { mdxSource, frontMatter, excerpt } = await parse(content, '.mdx');
+
+  if (project.metadata?.resources) {
+    frontMatter.layout = 'datapackage';
+  }
+
+  return {
+    props: {
+      mdxSource,
+      frontMatter,
+      excerpt,
+      project: project.serialize(),
+    },
+  };
+}

examples/simple-example/pages/_app.tsx

@@ -1,6 +1,7 @@
 import { AppProps } from 'next/app';
 import Head from 'next/head';
 import './styles.css';
+import "../styles/global.css";
 
 function CustomApp({ Component, pageProps }: AppProps) {
   return (

examples/simple-example/pages/api/proxy.ts

@@ -0,0 +1,26 @@
+import axios from "axios";
+
+export default function handler(req, res) {
+  if (!req.query.url) {
+    res.status(200).send({
+      error: true,
+      info: "No url to proxy in query string i.e. ?url=...",
+    });
+    return;
+  }
+  axios({
+    method: "get",
+    url: req.query.url,
+    responseType: "stream",
+  })
+    .then((resp) => {
+      resp.data.pipe(res);
+    })
+    .catch((err) => {
+      res.status(400).send({
+        error: true,
+        info: err.message,
+        detailed: err,
+      });
+    });
+}

examples/simple-example/pages/index.tsx

@@ -1,19 +1,35 @@
+import parse from '../lib/markdown';
+import Project from '../lib/project';
 import { promises as fs } from 'fs';
 import path from 'path';
-import { getProject } from '../lib/octokit';
-import getConfig from 'next/config';
-import NavBar from '../components/NavBar';
-import Footer from '../components/Footer';
+import Link from 'next/link';
 
 export async function getStaticProps() {
-  const jsonDirectory = path.join(process.cwd(), '/datasets.json');
+  const jsonDirectory = path.join(
+    process.cwd(),
+    '/examples/simple-example/datasets.json'
+  );
   const repos = await fs.readFile(jsonDirectory, 'utf8');
-  const github_pat = getConfig().serverRuntimeConfig.github_pat;
 
   const projects = await Promise.all(
     JSON.parse(repos).map(async (repo) => {
-      const project = await getProject(repo, github_pat);
-      return { ...project, repo_config: repo };
+      const project = await Project.getFromGitHub(repo.owner, repo.repo);
+
+      //  Defaults to README
+      const content = project.readme ? project.readme : '';
+
+      let { mdxSource, frontMatter, excerpt } = await parse(content, '.mdx');
+
+      if (project.metadata?.resources) {
+        frontMatter.layout = 'datapackage';
+      }
+
+      return {
+        mdxSource,
+        frontMatter,
+        excerpt,
+        project: project.serialize(),
+      };
     })
   );
   return {
@@ -28,118 +44,109 @@ const formatter = new Intl.DateTimeFormat('en-US', {
   month: 'long',
   day: 'numeric',
   hour: 'numeric',
+  minute: 'numeric',
+  second: 'numeric',
   timeZone: 'UTC',
 });
 
-export default function Datasets({ projects }) {
+export function Datasets({ projects }) {
   return (
-    <>
-      <NavBar />
-      <div className="px-4 sm:px-6 lg:px-8 py-16 max-w-7xl mx-auto">
-        <div className="sm:flex sm:items-center">
-          <div className="sm:flex-auto">
-            <h1 className="text-xl font-semibold leading-6 text-indigo-600">
-              Datasets
-            </h1>
-            <p className="mt-2 text-sm text-gray-700 py-8">
-              Here is a list of all my datasets for easy access and sharing all
-              stored on multiple github accounts and repos and joined together
-              here
-            </p>
-          </div>
-        </div>
-        <div className="mt-8 flow-root">
+    <div className="bg-white">
+      <div className="mx-auto max-w-7xl px-6 py-16 sm:py-24 lg:px-8">
+        <h2 className="text-2xl font-bold leading-10 tracking-tight text-indigo-500">
+          My Datasets
+        </h2>
+        <p className="mt-6 max-w-2xl text-base leading-7 text-gray-600">
+          Here is a list of all my datasets for easy access and sharing
+        </p>
+        <div className="mt-20">
+          {/*
+          <dl className="space-y-16 sm:grid sm:grid-cols-2 sm:gap-x-6 sm:gap-y-16 sm:space-y-0 lg:grid-cols-3 lg:gap-x-10">
+            {projects.map((project) => (
+              <div>
+                <dt className="text-base font-semibold leading-7 text-gray-900">
+                  <Link
+                    href={`@${project.project.owner}/${project.project.name}`}
+                  >
+                    {project.project.owner}/{project.project.name}
+                  </Link>
+                </dt>
+                <dt className="text-base font-semibold leading-7 text-indigo-600">
+                  <a
+                    href={`https://github.com/${project.project.owner}/${project.project.name}`}
+                  >
+                    Github repo
+                  </a>
+                </dt>
+                <dd className="mt-2 text-base leading-7 text-gray-600">
+                  {project.excerpt !== '' ? project.excerpt : 'No description'}
+                </dd>
+              </div>
+            ))}
+          </dl> */}
           <div className="-mx-4 -my-2 overflow-x-auto sm:-mx-6 lg:-mx-8">
             <div className="inline-block min-w-full py-2 align-middle sm:px-6 lg:px-8">
-              <div className="overflow-hidden shadow ring-1 ring-black ring-opacity-5 sm:rounded-lg">
-                <table className="min-w-full divide-y divide-gray-300">
-                  <thead className="bg-gray-50">
+              <table className="min-w-full divide-y divide-gray-300">
+                <thead>
+                  <tr>
+                    <th
+                      scope="col"
+                      className="px-3 py-3.5 text-left text-sm font-semibold text-gray-900"
+                    >
+                      Dataset name
+                    </th>
+                    <th
+                      scope="col"
+                      className="px-3 py-3.5 text-left text-sm font-semibold text-gray-900"
+                    >
+                      Description
+                    </th>
+                    <th
+                      scope="col"
+                      className="px-3 py-3.5 text-left text-sm font-semibold text-gray-900"
+                    >
+                      Last updated
+                    </th>
+                    <th
+                      scope="col"
+                      className="relative py-3.5 pl-3 pr-4 sm:pr-0"
+                    ></th>
+                  </tr>
+                </thead>
+                <tbody className="divide-y divide-gray-200">
+                  {projects.map((project) => (
                     <tr>
-                      <th
-                        scope="col"
-                        className="py-3.5 pl-4 pr-3 text-left text-sm font-semibold text-gray-900 sm:pl-6"
-                      >
-                        Name
-                      </th>
-                      <th
-                        scope="col"
-                        className="px-3 py-3.5 text-left text-sm font-semibold text-gray-900"
-                      >
-                        Repo
-                      </th>
-                      <th
-                        scope="col"
-                        className="px-3 py-3.5 text-left text-sm font-semibold text-gray-900"
-                      >
-                        Description
-                      </th>
-                      <th
-                        scope="col"
-                        className="px-3 py-3.5 text-left text-sm font-semibold text-gray-900"
-                      >
-                        Last updated
-                      </th>
-                      <th
-                        scope="col"
-                        className="relative py-3.5 pl-3 pr-4 sm:pr-6"
-                      >
-                        <span className="sr-only">More info</span>
-                      </th>
+                      <td className="whitespace-nowrap px-3 py-4 text-sm text-gray-500">
+                        <a href={project.project.repo_metadata.html_url}>
+                          {project.project.owner}/{project.project.name}
+                        </a>
+                      </td>
+                      <td className="px-3 py-4 text-sm text-gray-500">
+                        {project.project.repo_metadata.description}
+                      </td>
+                      <td className="whitespace-nowrap px-3 py-4 text-sm text-gray-500">
+                        {formatter.format(
+                          new Date(project.project.repo_metadata.updated_at)
+                        )}
+                      </td>
+                      <td className="relative whitespace-nowrap py-4 pl-3 pr-4 text-right text-sm font-medium sm:pr-0">
+                        <a
+                          href={`/@${project.project.owner}/${project.project.name}`}
+                          className="text-indigo-600 hover:text-indigo-900"
+                        >
+                          More info
+                        </a>
+                      </td>
                     </tr>
-                  </thead>
-                  <tbody className="divide-y divide-gray-200 bg-white">
-                    {projects.map((project) => (
-                      <tr key={project.id}>
-                        <td className="py-4 pl-4 pr-3 text-sm font-medium text-gray-900 sm:pl-6">
-                          {project.repo_config.name
-                            ? project.repo_config.name
-                            : project.full_name +
-                              (project.base_path === '/'
-                                ? ''
-                                : '/' + project.base_path)}
-                        </td>
-                        <td className="whitespace-nowrap px-3 py-4 text-sm text-gray-500">
-                          <a href={project.html_url}>{project.full_name}</a>
-                        </td>
-                        <td className="px-3 py-4 text-sm text-gray-500">
-                          {project.repo_config.description
-                            ? project.repo_config.description
-                            : project.description}
-                        </td>
-                        <td className="whitespace-nowrap px-3 py-4 text-sm text-gray-500">
-                          {formatter.format(new Date(project.last_updated))}
-                        </td>
-                        <td className="relative whitespace-nowrap py-4 pl-3 pr-4 text-right text-sm font-medium sm:pr-6">
-                          <a
-                            href={`/@${project.repo_config.owner}/${
-                              project.repo_config.repo
-                            }/${
-                              project.base_path === '/' ? '' : project.base_path
-                            }`}
-                            className="text-indigo-600 hover:text-indigo-900"
-                          >
-                            More info
-                            <span className="sr-only">
-                              on,
-                              {project.repo_config.name
-                                ? project.repo_config.name
-                                : project.full_name +
-                                  (project.base_path === '/'
-                                    ? ''
-                                    : '/' + project.base_path)}
-                            </span>
-                          </a>
-                        </td>
-                      </tr>
-                    ))}
-                  </tbody>
-                </table>
-              </div>
+                  ))}
+                </tbody>
+              </table>
             </div>
           </div>
         </div>
       </div>
-      <Footer />
-    </>
+    </div>
   );
 }
+
+export default Datasets;

examples/simple-example/pages/styles.css

@@ -1,11 +1,6 @@
 @tailwind base;
 @tailwind components;
 @tailwind utilities;
-
-.prose {
-  --tw-prose-headings: #4F46E5 !important;
-}
-
 html {
   -webkit-text-size-adjust: 100%;
   font-family: ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont,
@@ -67,6 +62,9 @@ pre {
   box-shadow: 0 0 #0000, 0 0 #0000, 0 10px 15px -3px rgba(0, 0, 0, 0.1),
     0 4px 6px -2px rgba(0, 0, 0, 0.05);
 }
+.rounded {
+  border-radius: 1.5rem;
+}
 .wrapper {
   width: 100%;
 }

examples/simple-example/postcss.config.js

@@ -1,6 +1,15 @@
+const { join } = require('path');
+
+// Note: If you use library-specific PostCSS/Tailwind configuration then you should remove the `postcssConfig` build
+// option from your application's configuration (i.e. project.json).
+//
+// See: https://nx.dev/guides/using-tailwind-css-in-react#step-4:-applying-configuration-to-libraries
+
 module.exports = {
   plugins: {
-    tailwindcss: {},
+    tailwindcss: {
+      config: join(__dirname, 'tailwind.config.js'),
+    },
     autoprefixer: {},
   },
-}
+};

examples/simple-example/project.json

@@ -1,7 +1,7 @@
 {
-  "name": "ckan-example",
+  "name": "simple-example",
   "$schema": "../../node_modules/nx/schemas/project-schema.json",
-  "sourceRoot": "examples/ckan-example",
+  "sourceRoot": "examples/simple-example",
   "projectType": "application",
   "targets": {
     "build": {
@@ -9,12 +9,12 @@
       "outputs": ["{options.outputPath}"],
       "defaultConfiguration": "production",
       "options": {
-        "root": "examples/ckan-example",
-        "outputPath": "dist/examples/ckan-example"
+        "root": "examples/simple-example",
+        "outputPath": "dist/examples/simple-example"
       },
       "configurations": {
         "development": {
-          "outputPath": "examples/ckan-example"
+          "outputPath": "examples/simple-example"
         },
         "production": {}
       }
@@ -23,16 +23,16 @@
       "executor": "@nrwl/next:server",
       "defaultConfiguration": "development",
       "options": {
-        "buildTarget": "ckan-example:build",
+        "buildTarget": "simple-example:build",
         "dev": true
       },
       "configurations": {
         "development": {
-          "buildTarget": "ckan-example:build:development",
+          "buildTarget": "simple-example:build:development",
           "dev": true
         },
         "production": {
-          "buildTarget": "ckan-example:build:production",
+          "buildTarget": "simple-example:build:production",
           "dev": false
         }
       }
@@ -40,14 +40,14 @@
     "export": {
       "executor": "@nrwl/next:export",
       "options": {
-        "buildTarget": "ckan-example:build:production"
+        "buildTarget": "simple-example:build:production"
       }
     },
     "test": {
       "executor": "@nrwl/jest:jest",
       "outputs": ["{workspaceRoot}/coverage/{projectRoot}"],
       "options": {
-        "jestConfig": "examples/ckan-example/jest.config.ts",
+        "jestConfig": "examples/simple-example/jest.config.ts",
         "passWithNoTests": true
       },
       "configurations": {
@@ -61,7 +61,7 @@
       "executor": "@nrwl/linter:eslint",
       "outputs": ["{options.outputFile}"],
       "options": {
-        "lintFilePatterns": ["examples/ckan-example/**/*.{ts,tsx,js,jsx}"]
+        "lintFilePatterns": ["examples/simple-example/**/*.{ts,tsx,js,jsx}"]
       }
     }
   },

examples/simple-example/styles/global.css

@@ -0,0 +1,67 @@
+@import "@flowershow/remark-callouts/styles.css";
+
+/* mathjax */
+.math-inline > mjx-container > svg {
+  display: inline;
+  align-items: center;
+}
+
+/* smooth scrolling in modern browsers */
+html {
+  scroll-behavior: smooth !important;
+}
+
+/* tooltip fade-out clip */
+.tooltip-body::after {
+  content: "";
+  position: absolute;
+  right: 0;
+  top: 3.6rem; /* multiple of $line-height used on the tooltip body (defined in tooltipBodyStyle) */
+  height: 1.2rem; /* ($top + $height)/$line-height is the number of lines we want to clip tooltip text at*/
+  width: 10rem;
+  background: linear-gradient(
+    to right,
+    rgba(255, 255, 255, 0),
+    rgba(255, 255, 255, 1) 100%
+  );
+}
+
+:is(h2, h3, h4, h5, h6):not(.blogitem-title) {
+  margin-left: -2rem !important;
+  padding-left: 2rem !important;
+  scroll-margin-top: 4.5rem;
+  position: relative;
+}
+
+.heading-link {
+  padding: 1px;
+  position: absolute;
+  left: 0;
+  top: 50%;
+  transform: translateY(-50%);
+  margin: auto 0;
+  border-radius: 5px;
+  background: #1e293b;
+  opacity: 0;
+  transition: opacity 0.2s;
+}
+
+.light .heading-link {
+  /* border: 1px solid #ab2b65; */
+  /* background: none; */
+  background: #e2e8f0;
+}
+
+:is(h2, h3, h4, h5, h6):not(.blogitem-title):hover .heading-link {
+  opacity: 100;
+}
+
+.heading-link svg {
+  transform: scale(0.75);
+}
+
+@media screen and (max-width: 640px) {
+  .heading-link {
+    visibility: hidden;
+  }
+}

examples/simple-example/tailwind.config.js

@@ -1,15 +1,21 @@
+const { createGlobPatternsForDependencies } = require('@nrwl/react/tailwind');
+const { join } = require('path');
+
 /** @type {import('tailwindcss').Config} */
 module.exports = {
   content: [
-    "./app/**/*.{js,ts,jsx,tsx,mdx}",
-    "./pages/**/*.{js,ts,jsx,tsx,mdx}",
-    "./components/**/*.{js,ts,jsx,tsx,mdx}",
+    "node_modules/@flowershow/core/dist/*.js",
+    "node_modules/@flowershow/core/*.js",
+    join(
+      __dirname,
+      '{src,pages,components}/**/*!(*.stories|*.spec).{ts,tsx,html}'
+    ),
+    ...createGlobPatternsForDependencies(__dirname),
   ],
   theme: {
     extend: {},
   },
   plugins: [
-    require('@tailwindcss/typography')
+    require('@tailwindcss/typography'),
   ],
-}
-
+};

examples/simple-example/tsconfig.json

@@ -1,20 +1,50 @@
 {
+  "extends": "../../tsconfig.base.json",
   "compilerOptions": {
-    "target": "es5",
-    "lib": ["dom", "dom.iterable", "esnext"],
+    "jsx": "preserve",
     "allowJs": true,
-    "skipLibCheck": true,
+    "esModuleInterop": true,
+    "allowSyntheticDefaultImports": true,
     "strict": false,
     "forceConsistentCasingInFileNames": true,
     "noEmit": true,
-    "esModuleInterop": true,
-    "module": "esnext",
-    "moduleResolution": "node",
     "resolveJsonModule": true,
     "isolatedModules": true,
-    "jsx": "preserve",
-    "incremental": true
+    "incremental": true,
+    "types": [
+      "jest",
+      "node"
+    ]
   },
-  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"],
-  "exclude": ["node_modules"]
+  "target": "es2020",
+  "lib": [
+    "dom",
+    "dom.iterable",
+    "esnext"
+  ],
+  "allowJs": true,
+  "skipLibCheck": true,
+  "strict": false,
+  "forceConsistentCasingInFileNames": true,
+  "noEmit": true,
+  "incremental": true,
+  "esModuleInterop": true,
+  "module": "esnext",
+  "moduleResolution": "node",
+  "resolveJsonModule": true,
+  "isolatedModules": true,
+  "jsx": "preserve",
+  "include": [
+    "**/*.ts",
+    "**/*.tsx",
+    "**/*.js",
+    "**/*.jsx",
+    "next-env.d.ts"
+  ],
+  "exclude": [
+    "node_modules",
+    "jest.config.ts",
+    "src/**/*.spec.ts",
+    "src/**/*.test.ts"
+  ]
 }

examples/simple-example/tsconfig.spec.json

@@ -6,6 +6,9 @@
     "types": ["jest", "node"],
     "jsx": "react"
   },
+  "paths": {
+      "@/*": ["./*"]
+  },
   "include": [
     "jest.config.ts",
     "src/**/*.test.ts",

package-lock.json

@@ -44,7 +44,6 @@
         "prop-types": "^15.8.1",
         "react": "18.2.0",
         "react-dom": "18.2.0",
-        "react-markdown": "^8.0.7",
         "react-next-github-btn": "^1.2.1",
         "react-plotly.js": "^2.6.0",
         "react-plotlyjs": "^0.4.4",
@@ -29696,41 +29695,6 @@
       "integrity": "sha512-w2GsyukL62IJnlaff/nRegPQR94C/XXamvMWmSHRJ4y7Ts/4ocGRmTHvOs8PSE6pB3dWOrD/nueuU5sduBsQ4w==",
       "dev": true
     },
-    "node_modules/react-markdown": {
-      "version": "8.0.7",
-      "resolved": "https://registry.npmjs.org/react-markdown/-/react-markdown-8.0.7.tgz",
-      "integrity": "sha512-bvWbzG4MtOU62XqBx3Xx+zB2raaFFsq4mYiAzfjXJMEz2sixgeAfraA3tvzULF02ZdOMUOKTBFFaZJDDrq+BJQ==",
-      "dependencies": {
-        "@types/hast": "^2.0.0",
-        "@types/prop-types": "^15.0.0",
-        "@types/unist": "^2.0.0",
-        "comma-separated-tokens": "^2.0.0",
-        "hast-util-whitespace": "^2.0.0",
-        "prop-types": "^15.0.0",
-        "property-information": "^6.0.0",
-        "react-is": "^18.0.0",
-        "remark-parse": "^10.0.0",
-        "remark-rehype": "^10.0.0",
-        "space-separated-tokens": "^2.0.0",
-        "style-to-object": "^0.4.0",
-        "unified": "^10.0.0",
-        "unist-util-visit": "^4.0.0",
-        "vfile": "^5.0.0"
-      },
-      "funding": {
-        "type": "opencollective",
-        "url": "https://opencollective.com/unified"
-      },
-      "peerDependencies": {
-        "@types/react": ">=16",
-        "react": ">=16"
-      }
-    },
-    "node_modules/react-markdown/node_modules/react-is": {
-      "version": "18.2.0",
-      "resolved": "https://registry.npmjs.org/react-is/-/react-is-18.2.0.tgz",
-      "integrity": "sha512-xWGDIW6x921xtzPkhiULtthJHoJvBbF3q26fzloPCK0hsvxtPVelvftw3zjbHWSkR2km9Z+4uxbDDK/6Zw9B8w=="
-    },
     "node_modules/react-next-github-btn": {
       "version": "1.2.1",
       "resolved": "https://registry.npmjs.org/react-next-github-btn/-/react-next-github-btn-1.2.1.tgz",
@@ -57255,35 +57219,6 @@
       "integrity": "sha512-w2GsyukL62IJnlaff/nRegPQR94C/XXamvMWmSHRJ4y7Ts/4ocGRmTHvOs8PSE6pB3dWOrD/nueuU5sduBsQ4w==",
       "dev": true
     },
-    "react-markdown": {
-      "version": "8.0.7",
-      "resolved": "https://registry.npmjs.org/react-markdown/-/react-markdown-8.0.7.tgz",
-      "integrity": "sha512-bvWbzG4MtOU62XqBx3Xx+zB2raaFFsq4mYiAzfjXJMEz2sixgeAfraA3tvzULF02ZdOMUOKTBFFaZJDDrq+BJQ==",
-      "requires": {
-        "@types/hast": "^2.0.0",
-        "@types/prop-types": "^15.0.0",
-        "@types/unist": "^2.0.0",
-        "comma-separated-tokens": "^2.0.0",
-        "hast-util-whitespace": "^2.0.0",
-        "prop-types": "^15.0.0",
-        "property-information": "^6.0.0",
-        "react-is": "^18.0.0",
-        "remark-parse": "^10.0.0",
-        "remark-rehype": "^10.0.0",
-        "space-separated-tokens": "^2.0.0",
-        "style-to-object": "^0.4.0",
-        "unified": "^10.0.0",
-        "unist-util-visit": "^4.0.0",
-        "vfile": "^5.0.0"
-      },
-      "dependencies": {
-        "react-is": {
-          "version": "18.2.0",
-          "resolved": "https://registry.npmjs.org/react-is/-/react-is-18.2.0.tgz",
-          "integrity": "sha512-xWGDIW6x921xtzPkhiULtthJHoJvBbF3q26fzloPCK0hsvxtPVelvftw3zjbHWSkR2km9Z+4uxbDDK/6Zw9B8w=="
-        }
-      }
-    },
     "react-next-github-btn": {
       "version": "1.2.1",
       "resolved": "https://registry.npmjs.org/react-next-github-btn/-/react-next-github-btn-1.2.1.tgz",

package.json

@@ -4,7 +4,62 @@
   "license": "MIT",
   "scripts": {},
   "private": true,
-  "dependencies": {},
+  "dependencies": {
+    "@apollo/client": "^3.7.11",
+    "@apollo/react-hooks": "^4.0.0",
+    "@emotion/react": "^11.10.6",
+    "@emotion/styled": "^11.10.6",
+    "@flowershow/core": "^0.4.9",
+    "@flowershow/markdowndb": "^0.1.0",
+    "@flowershow/remark-callouts": "^1.0.0",
+    "@flowershow/remark-embed": "^1.0.0",
+    "@flowershow/remark-wiki-link": "^1.0.1",
+    "@headlessui/react": "^1.7.13",
+    "@heroicons/react": "^2.0.17",
+    "@mui/icons-material": "^5.11.16",
+    "@mui/material": "^5.11.16",
+    "@mui/x-data-grid": "^6.1.0",
+    "@opentelemetry/api": "^1.4.0",
+    "@tailwindcss/typography": "^0.5.9",
+    "@tanstack/react-table": "^8.8.5",
+    "apollo-cache-inmemory": "^1.6.6",
+    "apollo-link": "^1.2.14",
+    "apollo-link-rest": "^0.9.0",
+    "filesize": "^10.0.7",
+    "gray-matter": "^4.0.3",
+    "html-react-parser": "^3.0.15",
+    "markdown-it": "^13.0.1",
+    "next": "^13.2.1",
+    "next-mdx-remote": "^4.4.1",
+    "next-seo": "^6.0.0",
+    "next-translate": "^2.0.5",
+    "nock": "^13.3.0",
+    "octokit": "^2.0.14",
+    "papaparse": "^5.4.1",
+    "plotly.js-basic-dist": "^2.20.0",
+    "prop-types": "^15.8.1",
+    "react": "18.2.0",
+    "react-dom": "18.2.0",
+    "react-next-github-btn": "^1.2.1",
+    "react-plotly.js": "^2.6.0",
+    "react-plotlyjs": "^0.4.4",
+    "react-vega": "^7.6.0",
+    "rehype-autolink-headings": "^6.1.1",
+    "rehype-katex": "^6.0.2",
+    "rehype-prism-plus": "^1.5.1",
+    "rehype-slug": "^5.1.0",
+    "remark-footnotes": "^4.0.1",
+    "remark-gfm": "^3.0.1",
+    "remark-math": "^5.1.1",
+    "remark-slug": "^7.0.1",
+    "remark-smartypants": "^2.0.0",
+    "remark-toc": "^8.0.1",
+    "slugify": "^1.6.6",
+    "timeago.js": "^4.0.2",
+    "tslib": "^2.3.0",
+    "vega": "^5.24.0",
+    "xlsx": "^0.18.5"
+  },
   "devDependencies": {
     "@babel/preset-react": "^7.14.5",
     "@nrwl/cypress": "15.9.2",
@@ -28,6 +83,7 @@
     "@types/react-dom": "18.0.11",
     "@typescript-eslint/eslint-plugin": "^5.36.1",
     "@typescript-eslint/parser": "^5.36.1",
+    "autoprefixer": "10.4.13",
     "babel-jest": "^29.4.1",
     "cypress": "^12.2.0",
     "eslint": "~8.15.0",
@@ -41,9 +97,11 @@
     "jest": "^29.4.1",
     "jest-environment-jsdom": "^29.4.1",
     "nx": "15.9.2",
+    "postcss": "8.4.21",
     "prettier": "^2.6.2",
     "react-test-renderer": "18.2.0",
     "swc-loader": "0.1.15",
+    "tailwindcss": "3.2.7",
     "ts-jest": "^29.0.5",
     "ts-node": "10.9.1",
     "typescript": "~4.9.5"

site/README.md

@@ -1,4 +1,4 @@
-This the PortalJS website.
+This the Portal.JS website.
 
 It is built on [Next.js](https://nextjs.org/).
 

site/components/ButtonLink.tsx

@@ -1,26 +0,0 @@
-import Link from 'next/link';
-
-export default function ButtonLink({
-  style = 'primary',
-  className = '',
-  href = '',
-  children,
-}) {
-  let styleClassName = '';
-
-  if (style == 'primary') {
-    styleClassName = 'text-primary bg-blue-400 hover:bg-blue-300';
-  } else if (style == 'secondary') {
-    styleClassName =
-      'text-secondary border !border-secondary hover:text-primary hover:bg-blue-300';
-  }
-
-  return (
-    <Link
-      href={href}
-      className={`inline-block h-12 px-6 py-3 border border-transparent text-base font-medium rounded-md focus:outline-none focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-sky-300/50 active:bg-sky-500 ${styleClassName} ${className}`}
-    >
-      {children}
-    </Link>
-  );
-}

site/components/Community.tsx

@@ -1,99 +0,0 @@
-import Container from './Container';
-import DiscordIcon from './icons/DiscordIcon';
-import EmailIcon from './icons/EmailIcon';
-import GitHubIcon from './icons/GitHubIcon';
-
-import { siteConfig } from '@/config/siteConfig';
-import { getContributorsCount, getRepoInfo } from '@/lib/getGitHubData';
-import { useEffect, useState } from 'react';
-
-const Stat = ({ title, value, ...props }) => {
-  return (
-    <div {...props}>
-      <span className="text-6xl font-bold text-secondary">{value}</span>
-      <p className="text-lg font-medium">{title}</p>
-    </div>
-  );
-};
-
-const IconButton = ({ Icon, text, href, ...props }) => {
-  return (
-    <div {...props}>
-      <a
-        className="rounded border border-secondary px-5 py-3 text-primary dark:text-primary-dark flex items-center hover:bg-secondary hover:text-primary dark:hover:text-primary transition-all duration-200"
-        href={href}
-      >
-        <Icon className="w-6 h-6 mr-2" />
-        {text}
-      </a>
-    </div>
-  );
-};
-
-export default function Community() {
-  const [repoInfo, setRepoInfo] = useState<any>();
-  const [contributorsCount, setContributorsCount] = useState('');
-
-  useEffect(() => {
-    //  This runs on client side and it's unlikely that users
-    //  will exceed the GitHub API  usage limit,  but added a
-    //  handling for that just in case.
-
-    getRepoInfo().then((res) => {
-      if (res.success) {
-        res.info.then((data) => setRepoInfo(data));
-      } else {
-        //  If the request fail e.g API usage limit, use
-        //  a placeholder
-        setRepoInfo({ stargazers_count: '+2k' });
-      }
-    });
-
-    getContributorsCount().then((res) => {
-      if (res.success) {
-        setContributorsCount(res.count);
-      } else {
-        setContributorsCount('+70');
-      }
-    });
-  }, []);
-
-  return (
-    <Container>
-      <h2 className="text-3xl font-bold text-primary dark:text-primary-dark ">
-        Community
-      </h2>
-      <p className="text-lg mt-8 ">
-        We are growing. Get in touch or become a contributor!
-      </p>
-      <div className="flex justify-center mt-12">
-        <Stat
-          title="Stars on GitHub"
-          value={repoInfo?.stargazers_count}
-          className="mr-10"
-        />
-        <Stat title="Contributors" value={contributorsCount} />
-      </div>
-      <div className="flex flex-wrap justify-center mt-12">
-        <IconButton
-          Icon={GitHubIcon}
-          text="Star PortalJS on GitHub"
-          className="sm:mr-4 mb-4 w-full sm:w-auto"
-          href={siteConfig.github}
-        />
-        <IconButton
-          Icon={DiscordIcon}
-          text="Join the Discord server"
-          className="sm:mr-4 mb-4 w-full sm:w-auto"
-          href={siteConfig.discord}
-        />
-        <IconButton
-          Icon={EmailIcon}
-          text="Subscribe to the PortalJS newsletter"
-          className="w-full sm:w-auto"
-          href="#hero"
-        />
-      </div>
-    </Container>
-  );
-}

site/components/Container.tsx

@@ -1,7 +0,0 @@
-export default function Container({ children }) {
-  return (
-    <div className="lg:max-w-8xl mx-auto px-4 lg:px-8 xl:px-12 mb-32">
-      {children}
-    </div>
-  );
-}

site/components/Features.tsx

@@ -1,5 +1,3 @@
-import Container from './Container';
-
 const features: { title: string; description: string; icon: string }[] = [
   {
     title: 'Unified sites',
@@ -39,12 +37,10 @@ const features: { title: string; description: string; icon: string }[] = [
 
 export default function Features() {
   return (
-    <Container>
-      <h2 className="text-3xl font-bold text-primary dark:text-primary-dark">
-        How PortalJS works?
-      </h2>
+    <div className="lg:max-w-8xl mx-auto px-4 lg:px-8 xl:px-12">
+      <h2 className="text-3xl font-bold">How Portal.JS works?</h2>
       <p className="text-lg mt-8">
-        PortalJS is built in JavaScript and React on top of the popular Next.js
+        Portal.JS is built in JavaScript and React on top of the popular Next.js
         framework, assuming a "decoupled" approach where the frontend is a
         separate service from the backend and interacts with backend(s) via an
         API. It can be used with any backend and has out of the box support for
@@ -59,7 +55,7 @@ export default function Features() {
             <div className="absolute -inset-px rounded-xl border-2 border-transparent opacity-0 [background:linear-gradient(var(--quick-links-hover-bg,theme(colors.sky.50)),var(--quick-links-hover-bg,theme(colors.sky.50)))_padding-box,linear-gradient(to_top,theme(colors.blue.300),theme(colors.blue.400),theme(colors.blue.500))_border-box] group-hover:opacity-100 dark:[--quick-links-hover-bg:theme(colors.slate.800)]" />
             <div className="relative overflow-hidden rounded-xl p-6">
               <img src={feature.icon} alt="" className="h-24 w-auto" />
-              <h2 className="mt-4 font-display text-base text-primary dark:text-primary-dark">
+              <h2 className="mt-4 font-display text-base text-slate-900 dark:text-white">
                 <span className="absolute -inset-px rounded-xl" />
                 {feature.title}
               </h2>
@@ -70,6 +66,6 @@ export default function Features() {
           </div>
         ))}
       </div>
-    </Container>
+    </div>
   );
 }

site/components/Gallery.tsx

@@ -1,73 +0,0 @@
-import Container from './Container';
-import GalleryItem from './GalleryItem';
-
-const items = [
-  {
-    title: 'Open Data Northern Ireland',
-    href: 'https://www.opendatani.gov.uk/',
-    image: '/images/showcases/odni.png',
-    description: 'Government Open Data Portal',
-  },
-  {
-    title: 'Birmingham City Observatory',
-    href: 'https://www.cityobservatory.birmingham.gov.uk/',
-    image: '/images/showcases/birmingham.png',
-    description: 'Government Open Data Portal',
-  },
-  {
-    title: 'UAE Open Data',
-    href: 'https://opendata.fcsc.gov.ae/',
-    image: '/images/showcases/uae.png',
-    description: 'Government Open Data Portal',
-    sourceUrl: 'https://github.com/FCSCOpendata/frontend',
-  },
-  {
-    title: 'Brazil Open Data',
-    href: 'https://dados.gov.br/',
-    image: '/images/showcases/brazil.png',
-    description: 'Government Open Data Portal',
-  },
-  {
-    title: 'Datahub Open Data',
-    href: 'https://opendata.datahub.io/',
-    image: '/images/showcases/datahub.png',
-    description: 'Demo Data Portal by DataHub',
-  },
-  {
-    title: 'Example: Simple Data Catalog',
-    href: 'https://example.portaljs.org/',
-    image: '/images/showcases/example-simple-catalog.png',
-    description: 'Simple data catalog',
-    sourceUrl:
-      'https://github.com/datopian/portaljs/tree/main/examples/simple-example',
-    docsUrl: '/docs/example-data-catalog',
-  },
-  {
-    title: 'Example: Portal with CKAN',
-    href: 'https://ckan-example.portaljs.org/',
-    image: '/images/showcases/example-ckan.png',
-    description: 'Simple portal with data coming from CKAN',
-    sourceUrl:
-      'https://github.com/datopian/portaljs/tree/main/examples/ckan-example',
-    docsUrl: '/docs/example-ckan',
-  },
-];
-
-export default function Gallery() {
-  return (
-    <Container>
-      <h2
-        className="text-3xl font-bold text-primary dark:text-primary-dark"
-        id="gallery"
-      >
-        Gallery
-      </h2>
-      <p className="text-lg mt-8">Discover what's being powered by PortalJS</p>
-      <div className="not-prose my-12 grid grid-cols-1 gap-6 md:grid-cols-2 lg:grid-cols-3">
-        {items.map((item) => {
-          return <GalleryItem item={item} />;
-        })}
-      </div>
-    </Container>
-  );
-}

site/components/GalleryItem.tsx

@@ -1,106 +0,0 @@
-const IconBeaker = () => (
-  <svg
-    xmlns="http://www.w3.org/2000/svg"
-    fill="none"
-    viewBox="0 0 24 24"
-    stroke-width="1.5"
-    stroke="currentColor"
-    className="w-6 h-6"
-  >
-    <path
-      stroke-linecap="round"
-      stroke-linejoin="round"
-      d="M9.75 3.104v5.714a2.25 2.25 0 01-.659 1.591L5 14.5M9.75 3.104c-.251.023-.501.05-.75.082m.75-.082a24.301 24.301 0 014.5 0m0 0v5.714c0 .597.237 1.17.659 1.591L19.8 15.3M14.25 3.104c.251.023.501.05.75.082M19.8 15.3l-1.57.393A9.065 9.065 0 0112 15a9.065 9.065 0 00-6.23-.693L5 14.5m14.8.8l1.402 1.402c1.232 1.232.65 3.318-1.067 3.611A48.309 48.309 0 0112 21c-2.773 0-5.491-.235-8.135-.687-1.718-.293-2.3-2.379-1.067-3.61L5 14.5"
-    />
-  </svg>
-);
-
-const IconDocs = () => (
-  <svg
-    xmlns="http://www.w3.org/2000/svg"
-    fill="none"
-    viewBox="0 0 24 24"
-    strokeWidth={1.5}
-    stroke="currentColor"
-    className="w-6 h-6"
-  >
-    <path
-      strokeLinecap="round"
-      strokeLinejoin="round"
-      d="M12 6.042A8.967 8.967 0 006 3.75c-1.052 0-2.062.18-3 .512v14.25A8.987 8.987 0 016 18c2.305 0 4.408.867 6 2.292m0-14.25a8.966 8.966 0 016-2.292c1.052 0 2.062.18 3 .512v14.25A8.987 8.987 0 0018 18a8.967 8.967 0 00-6 2.292m0-14.25v14.25"
-    />
-  </svg>
-);
-
-const IconCode = () => (
-  <svg
-    xmlns="http://www.w3.org/2000/svg"
-    fill="none"
-    viewBox="0 0 24 24"
-    strokeWidth={1.5}
-    stroke="currentColor"
-    className="w-6 h-6"
-  >
-    <path
-      strokeLinecap="round"
-      strokeLinejoin="round"
-      d="M17.25 6.75L22.5 12l-5.25 5.25m-10.5 0L1.5 12l5.25-5.25m7.5-3l-4.5 16.5"
-    />
-  </svg>
-);
-
-const ActionButton = ({ title, Icon, href, className = '' }) => (
-  <a
-    title={title}
-    target="_blank"
-    href={href}
-    className={`rounded-full p-2 hover:bg-secondary transition-all duration-250 ${className}`}
-  >
-    <Icon />
-  </a>
-);
-
-export default function GalleryItem({ item }) {
-  return (
-    <a
-      className="rounded overflow-hidden group relative border-1 shadow-lg"
-      target="_blank"
-      href={item.href}
-    >
-      <div
-        className="bg-cover bg-no-repeat bg-top aspect-video w-full group-hover:blur-sm group-hover:scale-105 transition-all duration-200"
-        style={{ backgroundImage: `url(${item.image})` }}
-      >
-        <div className="w-full h-full bg-black opacity-0 group-hover:opacity-50 transition-all duration-200"></div>
-      </div>
-      <div>
-        <div className="opacity-0 group-hover:opacity-100 absolute top-0 bottom-0 right-0 left-0 transition-all duration-200 px-2 flex items-center justify-center">
-          <div className="text-center text-primary-dark">
-            <span className="text-xl font-semibold">{item.title}</span>
-            <p className="text-base font-medium">{item.description}</p>
-            <div className="flex justify-center mt-2">
-              <ActionButton Icon={IconBeaker} title="Demo" href={item.href} />
-              {item.docsUrl && (
-                <ActionButton
-                  Icon={IconDocs}
-                  title="Documentation"
-                  href={item.docsUrl}
-                  className="mx-5"
-                />
-              )}
-              {item.sourceUrl && (
-                <ActionButton
-                  Icon={IconCode}
-                  title="Source code"
-                  href={item.sourceUrl}
-                />
-              )}
-
-              {/* Maybe: Blog post */}
-            </div>
-          </div>
-        </div>
-      </div>
-    </a>
-  );
-}

site/components/Hero.tsx

@@ -1,8 +1,6 @@
 import clsx from 'clsx';
 import Highlight, { defaultProps } from 'prism-react-renderer';
 import { Fragment, useRef } from 'react';
-import ButtonLink from './ButtonLink';
-import NewsletterForm from './NewsletterForm';
 
 const codeLanguage = 'javascript';
 const code = `export default {
@@ -33,10 +31,7 @@ export function Hero() {
   const el = useRef(null);
 
   return (
-    <div
-      className="overflow-hidden -mb-32 mt-[-4.5rem] pb-32 pt-[4.5rem] lg:mt-[-4.75rem] lg:pt-[4.75rem]"
-      id="hero"
-    >
+    <div className="overflow-hidden -mb-32 mt-[-4.5rem] pb-32 pt-[4.5rem] lg:mt-[-4.75rem] lg:pt-[4.75rem]">
       <div className="py-16 sm:px-2 lg:relative lg:py-20 lg:px-0">
         {/* Commented code on line 37, 39 and 113 will reenable the two columns hero */}
         {/* <div className="mx-auto grid max-w-2xl grid-cols-1 items-center gap-y-16 gap-x-8 px-4 lg:max-w-8xl lg:grid-cols-2 lg:px-8 xl:gap-x-16 xl:px-12"> */}
@@ -49,19 +44,55 @@ export function Hero() {
               </h1>
             </div>
             <p className="mt-4 text-xl tracking-tight text-slate-400">
-              Rapidly build rich data portals using a modern frontend framework.
+              Portal.JS is a framework for rapidly building rich data portal
+              frontends using a modern frontend approach. It can be used to
+              present a single dataset or build a full-scale data
+              catalog/portal.
             </p>
-
-            <ButtonLink className="mt-8" href="/docs">
-              Get started
-            </ButtonLink>
-
-            <ButtonLink className="ml-3" href="#gallery" style="secondary">
-              Gallery
-            </ButtonLink>
-
-            <div className="md:max-w-md mx-auto">
-              <NewsletterForm />
+            <div className="mt-8 sm:mx-auto sm:text-center lg:text-left lg:mx-0">
+              <p className="text-base font-medium text-slate-400 dark:text-slate-400">
+                Sign up to get notified about updates
+              </p>
+              <form
+                method="POST"
+                name="get-updates"
+                data-netlify="true"
+                action="/subscribed"
+                className="mt-3 sm:flex"
+              >
+                <label htmlFor="name" className="sr-only">
+                  Name
+                </label>
+                <input
+                  name="name"
+                  type="text"
+                  required
+                  placeholder="Your name"
+                  className="block w-full sm:flex-auto sm:w-32 px-2 py-3 text-base rounded-md bg-slate-200 dark:bg-slate-800 placeholder-gray-500 focus:outline-none focus:ring-2 focus:ring-offset-2 focus:ring-blue-400 focus:ring-offset-gray-900"
+                />
+                <label htmlFor="email" className="sr-only">
+                  Email address
+                </label>
+                <input
+                  name="email"
+                  type="email"
+                  required
+                  placeholder="Your email"
+                  className="block w-full mt-3 sm:flex-auto sm:w-64 sm:mt-0 sm:ml-3 px-2 py-3 text-base rounded-md bg-slate-200 dark:bg-slate-800 placeholder-gray-500 focus:outline-none focus:ring-2 focus:ring-offset-2 focus:ring-blue-400 focus:ring-offset-gray-900"
+                />
+                <input type="hidden" name="form-name" value="get-updates" />
+                <button
+                  type="submit"
+                  className="flex-none mt-3 px-6 py-3 border border-transparent text-base font-medium rounded-md text-slate-900 bg-blue-400 hover:bg-blue-300 focus:outline-none focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-sky-300/50 active:bg-sky-500 sm:mt-0 sm:ml-3"
+                >
+                  Notify me
+                </button>
+              </form>
+              {/* <p className="mt-3 text-sm text-slate-400 dark:text-slate-300 sm:mt-4">
+                We are actively trialling and developing Flowershow. If you'd
+                like to get notified about our progress and important updates,
+                please sign up.
+              </p> */}
             </div>
             <p className="my-10 text-l tracking-wide">
               <span>A project of</span>

site/components/Layout.tsx

@@ -1,6 +1,5 @@
 import { siteConfig } from '@/config/siteConfig';
 import { NextSeo } from 'next-seo';
-import { useTheme } from 'next-themes';
 import Link from 'next/link';
 import { useCallback, useEffect, useState } from 'react';
 
@@ -59,7 +58,6 @@ export default function Layout({
   tableOfContents?;
 }) {
   // const { toc } = children.props;
-  const { theme, setTheme } = useTheme();
 
   const currentSection = useTableOfContents(tableOfContents);
 
@@ -89,21 +87,17 @@ export default function Layout({
         >
           Built by{' '}
           <img
-            src={
-              theme === 'dark'
-                ? '/images/datopian-light-logotype.svg'
-                : '/images/datopian-dark-logotype.svg'
-            }
+            src="/datopian-logo.png"
             alt="Datopian Logo"
             className="h-6 ml-2"
           />
         </a>
       </footer>
       {/** TABLE OF CONTENTS */}
-      {tableOfContents.length > 0 && siteConfig.tableOfContents && (
+      {tableOfContents.length > 0 && (siteConfig.tableOfContents) && (
         <div className="hidden xl:fixed xl:right-0 xl:top-[4.5rem] xl:block xl:w-1/5 xl:h-[calc(100vh-4.5rem)] xl:flex-none xl:overflow-y-auto xl:py-16 xl:pr-6 xl:mb-16">
           <nav aria-labelledby="on-this-page-title" className="w-56">
-            <h2 className="font-display text-md font-medium text-primary dark:text-primary-dark">
+            <h2 className="font-display text-md font-medium text-slate-900 dark:text-white">
               On this page
             </h2>
             <ol className="mt-4 space-y-3 text-sm">
@@ -114,7 +108,7 @@ export default function Layout({
                       href={`#${section.id}`}
                       className={
                         isActive(section)
-                          ? 'text-secondary'
+                          ? 'text-sky-500'
                           : 'font-normal text-slate-500 hover:text-slate-700 dark:text-slate-400 dark:hover:text-slate-300'
                       }
                     >

site/components/MDXPage.tsx

@@ -11,7 +11,7 @@ export default function MDXPage({ source, frontMatter }) {
   };
 
   return (
-    <div className="prose mx-auto prose-a:text-primary dark:prose-a:text-primary-dark prose-strong:text-primary dark:prose-strong:text-primary-dark prose-headings:text-primary dark:prose-headings:text-primary-dark text-primary dark:text-primary-dark prose-headings:font-headings dark:prose-invert prose-a:break-words">
+    <div className="prose mx-auto prose-a:text-primary dark:prose-a:text-primary-dark prose-strong:text-primary dark:prose-strong:text-primary-dark prose-code:text-primary dark:prose-code:text-primary-dark prose-headings:text-primary dark:prose-headings:text-primary-dark prose text-primary dark:text-primary-dark prose-headings:font-headings dark:prose-invert prose-a:break-words">
       <header>
         <div className="mb-6">
           {/* Default layout */}

site/components/NavItem.tsx

@@ -29,12 +29,12 @@ export default function NavItem({ item }) {
         {Object.prototype.hasOwnProperty.call(item, "href") ? (
           <Link
             href={item.href}
-            className="text-slate-600 dark:text-slate-400 inline-flex items-center mr-2 px-1 pt-1 text-sm font-medium hover:text-slate-500"
+            className="text-slate-500 inline-flex items-center mr-2 px-1 pt-1 text-sm font-medium hover:text-slate-600"
           >
             {item.name}
           </Link>
         ) : (
-          <div className="text-slate-600 dark:text-slate-400 inline-flex items-center mr-2 px-1 pt-1 text-sm font-medium hover:text-slate-500 fill-slate-500 hover:fill-slate-600">
+          <div className="text-slate-500 inline-flex items-center mr-2 px-1 pt-1 text-sm font-medium hover:text-slate-600 fill-slate-500 hover:fill-slate-600">
             {item.name}
           </div>
         )}

site/components/NewsletterForm.tsx

@@ -1,127 +0,0 @@
-import Script from 'next/script';
-
-export default function NewsletterForm() {
-  return (
-    <div>
-      <link
-        rel="stylesheet"
-        href="https://sibforms.com/forms/end-form/build/sib-styles.css"
-      />
-      <div
-        id="sib-form-container"
-        className="mt-8 sm:mx-auto sm:text-center lg:text-left lg:mx-0"
-      >
-        <p className="text-base font-medium text-slate-400 dark:text-slate-400">
-          Sign up to get notified about updates
-        </p>
-        <div id="sib-container" className="!bg-transparent !p-0 !pb-5">
-          <form
-            id="sib-form"
-            method="POST"
-            action="https://0613d040.sibforms.com/serve/MUIEAGd31Nknuf7_fodoNJ3t0B71KWpbFfnzgk_VewvONuLQG8JO3qOotew23kQT3HpoJQUG_vzcjOTjn29B6GpXxPbSml_XWwHgG2mWq-jhrjfqpHCcPoOY_ge-rN2vDFWYZ80l242DTYGDRRWtTusdAYIk2oyf-nhJyOqQrUzTnXlAlKc7SxWgynSQ1GHr3jU5s57h6986IoK4"
-            data-type="subscription"
-            className="mt-3 sm:flex"
-          >
-            <div className="sib-input sib-form-block !p-0 block w-full sm:flex-auto sm:w-64 mt-3 sm:mt-0">
-              <div className="form__entry entry_block w-full">
-                <label htmlFor="email" className="sr-only entry__label">
-                  Email address
-                </label>
-                <input
-                  id="EMAIL"
-                  name="EMAIL"
-                  type="email"
-                  required
-                  placeholder="Your email"
-                  className="input entry__field !w-full px-2 py-3 text-base rounded-md bg-slate-200 dark:bg-slate-800 placeholder-gray-500 focus:outline-none focus:ring-2 focus:ring-offset-2 focus:ring-blue-400 focus:ring-offset-gray-900"
-                />
-
-                <label className="entry__error entry__error--primary px-2 text-red-400 text-sm"></label>
-              </div>
-            </div>
-
-            <input type="hidden" name="form-name" value="get-updates" />
-            <button
-              type="submit"
-              className="sib-form-block__button sib-form-block__button-with-loader h-12 flex-none mt-3 px-6 py-3 border border-transparent text-base font-medium rounded-md text-slate-900 bg-blue-400 hover:bg-blue-300 focus:outline-none focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-sky-300/50 active:bg-sky-500 sm:mt-0 sm:ml-3"
-            >
-              <svg
-                className="icon clickable__icon progress-indicator__icon sib-hide-loader-icon hidden"
-                viewBox="0 0 512 512"
-              >
-                <path d="M460.116 373.846l-20.823-12.022c-5.541-3.199-7.54-10.159-4.663-15.874 30.137-59.886 28.343-131.652-5.386-189.946-33.641-58.394-94.896-95.833-161.827-99.676C261.028 55.961 256 50.751 256 44.352V20.309c0-6.904 5.808-12.337 12.703-11.982 83.556 4.306 160.163 50.864 202.11 123.677 42.063 72.696 44.079 162.316 6.031 236.832-3.14 6.148-10.75 8.461-16.728 5.01z" />
-              </svg>
-              Notify Me
-            </button>
-            <input
-              type="text"
-              name="email_address_check"
-              value=""
-              className="input--hidden"
-            />
-            <input type="hidden" name="locale" value="en" />
-          </form>
-        </div>
-        <div id="error-message" className="sib-form-message-panel !border-none">
-          <div className="sib-form-message-panel__text sib-form-message-panel__text--center !text-red-400 justify-center">
-            <svg
-              viewBox="0 0 512 512"
-              className="sib-icon sib-notification__icon"
-            >
-              <path d="M256 40c118.621 0 216 96.075 216 216 0 119.291-96.61 216-216 216-119.244 0-216-96.562-216-216 0-119.203 96.602-216 216-216m0-32C119.043 8 8 119.083 8 256c0 136.997 111.043 248 248 248s248-111.003 248-248C504 119.083 392.957 8 256 8zm-11.49 120h22.979c6.823 0 12.274 5.682 11.99 12.5l-7 168c-.268 6.428-5.556 11.5-11.99 11.5h-8.979c-6.433 0-11.722-5.073-11.99-11.5l-7-168c-.283-6.818 5.167-12.5 11.99-12.5zM256 340c-15.464 0-28 12.536-28 28s12.536 28 28 28 28-12.536 28-28-12.536-28-28-28z" />
-            </svg>
-            <span className="sib-form-message-panel__inner-text !text-md">
-              Your subscription could not be saved. Please try again.
-            </span>
-          </div>
-        </div>
-        <div
-          id="success-message"
-          className="sib-form-message-panel !border-none"
-        >
-          <div className="sib-form-message-panel__text sib-form-message-panel__text--center text-green-400 justify-center">
-            <svg
-              viewBox="0 0 512 512"
-              className="sib-icon sib-notification__icon"
-            >
-              <path d="M256 8C119.033 8 8 119.033 8 256s111.033 248 248 248 248-111.033 248-248S392.967 8 256 8zm0 464c-118.664 0-216-96.055-216-216 0-118.663 96.055-216 216-216 118.664 0 216 96.055 216 216 0 118.663-96.055 216-216 216zm141.63-274.961L217.15 376.071c-4.705 4.667-12.303 4.637-16.97-.068l-85.878-86.572c-4.667-4.705-4.637-12.303.068-16.97l8.52-8.451c4.705-4.667 12.303-4.637 16.97.068l68.976 69.533 163.441-162.13c4.705-4.667 12.303-4.637 16.97.068l8.451 8.52c4.668 4.705 4.637 12.303-.068 16.97z" />
-            </svg>
-            <span className="sib-form-message-panel__inner-text !text-md !text-green-500">
-              Your subscription has been successful.
-            </span>
-          </div>
-        </div>
-      </div>
-      <Script
-        id="newsletter-form-validation-message"
-        dangerouslySetInnerHTML={{
-          __html: `  
-          window.REQUIRED_CODE_ERROR_MESSAGE = 'Please choose a country code';
-          window.LOCALE = 'en';
-          window.EMAIL_INVALID_MESSAGE = window.SMS_INVALID_MESSAGE = "The information provided is invalid. Please review the field format and try again.";
-        
-          window.REQUIRED_ERROR_MESSAGE = "This field cannot be left blank. ";
-        
-          window.GENERIC_INVALID_MESSAGE = "The information provided is invalid. Please review the field format and try again.";
-        
-        
-        
-        
-          window.translation = {
-            common: {
-              selectedList: '{quantity} list selected',
-              selectedLists: '{quantity} lists selected'
-            }
-          };
-        
-          var AUTOHIDE = Boolean(0);
-        `,
-        }}
-      />
-      <Script
-        id="newsletter-submit-form"
-        src="https://sibforms.com/forms/end-form/build/main.js"
-      />
-    </div>
-  );
-}

site/components/icons/DiscordIcon.tsx

@@ -1,14 +0,0 @@
-export default function DiscordIcon(props) {
-  return (
-    <svg
-      xmlns="http://www.w3.org/2000/svg"
-      width="16"
-      height="16"
-      fill="currentColor"
-      viewBox="0 0 16 16"
-      {...props}
-    >
-      <path d="M13.545 2.907a13.227 13.227 0 0 0-3.257-1.011.05.05 0 0 0-.052.025c-.141.25-.297.577-.406.833a12.19 12.19 0 0 0-3.658 0 8.258 8.258 0 0 0-.412-.833.051.051 0 0 0-.052-.025c-1.125.194-2.22.534-3.257 1.011a.041.041 0 0 0-.021.018C.356 6.024-.213 9.047.066 12.032c.001.014.01.028.021.037a13.276 13.276 0 0 0 3.995 2.02.05.05 0 0 0 .056-.019c.308-.42.582-.863.818-1.329a.05.05 0 0 0-.01-.059.051.051 0 0 0-.018-.011 8.875 8.875 0 0 1-1.248-.595.05.05 0 0 1-.02-.066.051.051 0 0 1 .015-.019c.084-.063.168-.129.248-.195a.05.05 0 0 1 .051-.007c2.619 1.196 5.454 1.196 8.041 0a.052.052 0 0 1 .053.007c.08.066.164.132.248.195a.051.051 0 0 1-.004.085 8.254 8.254 0 0 1-1.249.594.05.05 0 0 0-.03.03.052.052 0 0 0 .003.041c.24.465.515.909.817 1.329a.05.05 0 0 0 .056.019 13.235 13.235 0 0 0 4.001-2.02.049.049 0 0 0 .021-.037c.334-3.451-.559-6.449-2.366-9.106a.034.034 0 0 0-.02-.019Zm-8.198 7.307c-.789 0-1.438-.724-1.438-1.612 0-.889.637-1.613 1.438-1.613.807 0 1.45.73 1.438 1.613 0 .888-.637 1.612-1.438 1.612Zm5.316 0c-.788 0-1.438-.724-1.438-1.612 0-.889.637-1.613 1.438-1.613.807 0 1.451.73 1.438 1.613 0 .888-.631 1.612-1.438 1.612Z" />
-    </svg>
-  );
-}

site/components/icons/EmailIcon.tsx

@@ -1,14 +0,0 @@
-export default function EmailIcon(props) {
-  return (
-    <svg
-      fill="currentColor"
-      viewBox="0 0 2150 2150"
-      xmlns="http://www.w3.org/2000/svg"
-      {...props}
-    >
-      <path
-        d="M1920 428.266v1189.54l-464.16-580.146-88.203 70.585 468.679 585.904H83.684l468.679-585.904-88.202-70.585L0 1617.805V428.265l959.944 832.441L1920 428.266ZM1919.932 226v52.627l-959.943 832.44L.045 278.628V226h1919.887Z"
-      />
-    </svg>
-  );
-}

site/components/icons/GitHubIcon.tsx

@@ -1,7 +0,0 @@
-export default function GitHubIcon(props) {
-  return (
-    <svg aria-hidden="true" viewBox="0 0 16 16" fill="currentColor" {...props}>
-      <path d="M8 0C3.58 0 0 3.58 0 8C0 11.54 2.29 14.53 5.47 15.59C5.87 15.66 6.02 15.42 6.02 15.21C6.02 15.02 6.01 14.39 6.01 13.72C4 14.09 3.48 13.23 3.32 12.78C3.23 12.55 2.84 11.84 2.5 11.65C2.22 11.5 1.82 11.13 2.49 11.12C3.12 11.11 3.57 11.7 3.72 11.94C4.44 13.15 5.59 12.81 6.05 12.6C6.12 12.08 6.33 11.73 6.56 11.53C4.78 11.33 2.92 10.64 2.92 7.58C2.92 6.71 3.23 5.99 3.74 5.43C3.66 5.23 3.38 4.41 3.82 3.31C3.82 3.31 4.49 3.1 6.02 4.13C6.66 3.95 7.34 3.86 8.02 3.86C8.7 3.86 9.38 3.95 10.02 4.13C11.55 3.09 12.22 3.31 12.22 3.31C12.66 4.41 12.38 5.23 12.3 5.43C12.81 5.99 13.12 6.7 13.12 7.58C13.12 10.65 11.25 11.33 9.47 11.53C9.76 11.78 10.01 12.26 10.01 13.01C10.01 14.08 10 14.94 10 15.21C10 15.42 10.15 15.67 10.55 15.59C13.71 14.53 16 11.53 16 8C16 3.58 12.42 0 8 0Z" />
-    </svg>
-  );
-}

site/content/config.js

@@ -1,8 +1,8 @@
 const config = {
   title:
-    "PortalJS",
+    "Portal.JS",
   description:
-    "PortalJS is a framework for rapidly building rich data portal frontends using a modern frontend approach. PortalJS can be used to present a single dataset or build a full-scale data catalog/portal.",
+    "Portal.JS is a framework for rapidly building rich data portal frontends using a modern frontend approach. portal.js can be used to present a single dataset or build a full-scale data catalog/portal.",
   theme: {
     default: "dark",
     toggleIcon: "/images/theme-button.svg",
@@ -12,33 +12,34 @@ const config = {
   authorUrl: "https://datopian.com/",
   navbarTitle: {
     // logo: "/images/logo.svg",
-    text: "🌀 PortalJS",
+    text: "🌀 Portal.JS",
     // version: "Alpha",
   },
   navLinks: [
     { name: "Docs", href: "/docs" },
-    // { name: "Components", href: "/docs/components" },
-    { name: "Blog", href: "/blog" },
-    // { name: "Gallery", href: "/gallery" },
-    // { name: "Data Literate", href: "/data-literate" },
-    // { name: "DL Demo", href: "/data-literate/demo" },
-    // { name: "Excel Viewer", href: "/excel-viewer" },
+    { name: "Components", href: "/docs/components" },
+    { name: "Learn", href: "/learn" },
+    { name: "Gallery", href: "/gallery" },
+    { name: "Data Literate", href: "/data-literate" },
+    { name: "DL Demo", href: "/data-literate/demo" },
+    { name: "Excel Viewer", href: "/excel-viewer" },
+    { name: "GitHub", href: "https://github.com/datopian/portal.js" },
   ],
   footerLinks: [],
   nextSeo: {
     openGraph: {
       type: "website",
       title:
-        "PortalJS - rapidly build rich data portals using a modern frontend framework.",
+        "Portal.JS - Rapidly build rich data portals using a modern frontend framework",
       description:
-        "PortalJS is a framework for rapidly building rich data portal frontends using a modern frontend approach. PortalJS can be used to present a single dataset or build a full-scale data catalog and portal.",
+        "Portal.JS is a framework for rapidly building rich data portal frontends using a modern frontend approach. portal.js can be used to present a single dataset or build a full-scale data catalog/portal.",
       locale: "en_US",
       images: [
         {
-          url: "/homepage-screenshot.png",  //  TODO
-          alt: "PortalJS - rapidly build rich data portals using a modern frontend framework.",
-          width: 1280,
-          height: 720,
+          url: "https://datahub.io/static/img/opendata/product.png",  //  TODO
+          alt: "Portal.JS - Rapidly build rich data portals using a modern frontend framework",
+          width: 1200,
+          height: 627,
           type: "image/jpg",
         },
       ],
@@ -50,7 +51,7 @@ const config = {
     },
   },
   github: "https://github.com/datopian/portaljs",
-  discord: "https://discord.gg/EeyfGrGu4U",
+  discord: "https://discord.gg/An7Bu5x8",
   tableOfContents: true,
   // analytics: "xxxxxx",
   // editLinkShow: true,

site/content/data-literate/demo.mdx

@@ -13,7 +13,7 @@ You can see the raw source of this page here: https://raw.githubusercontent.com/
 We can have github-flavored markdown including markdown tables, auto-linked links and checklists:
 
 ```
-https://github.com/datopian/portaljs
+https://github.com/datopian/portal.js
 
 | a | b |
 |---|---|
@@ -23,7 +23,7 @@ https://github.com/datopian/portaljs
 * [ ] a second thing to do
 ```
 
-https://github.com/datopian/portaljs
+https://github.com/datopian/portal.js
 
 | a | b |
 |---|---|

site/content/docs.md

@@ -0,0 +1,132 @@
+# 🌀 Portal.JS: The JavaScript framework for data portals
+
+🌀 `portal.js` is a framework for rapidly building rich data portal frontends using a modern frontend approach. `portal.js` can be used to present a single dataset or build a full-scale data catalog/portal.
+
+`portal.js` is built in Javascript and React on top of the popular [Next.js](https://nextjs.com/) framework. `portal` assumes a "decoupled" approach where the frontend is a separate service from the backend and interacts with backend(s) via an API. It can be used with any backend and has out of the box support for [CKAN](https://ckan.org/).
+
+## Features
+
+- 🗺️ Unified sites: present data and content in one seamless site, pulling datasets from a DMS (e.g. CKAN) and content from a CMS (e.g. wordpress) with a common internal API.
+- 👩‍💻 Developer friendly: built with familiar frontend tech Javascript, React etc
+- 🔋 Batteries included: Full set of portal components out of the box e.g. catalog search, dataset showcase, blog etc.
+- 🎨 Easy to theme and customize: installable themes, use standard CSS and React+CSS tooling. Add new routes quickly.
+- 🧱 Extensible: quickly extend and develop/import your own React components
+- 📝 Well documented: full set of documentation plus the documentation of NextJS and Apollo.
+
+### For developers
+
+- 🏗 Build with modern, familiar frontend tech such as Javascript and React.
+- 🚀 NextJS framework: so everything in NextJS for free React, SSR, static site generation, huge number of examples and integrations etc.
+  - SSR => unlimited number of pages, SEO etc whilst still using React.
+  - Static Site Generation (SSG) (good for small sites) => ultra-simple deployment, great performance and lighthouse scores etc
+
+## Installation and setup
+
+Before installation, ensure your system satisfies the following requirements:
+
+- Node.js 10.13 or later
+- Nextjs 10.0.3
+- MacOS, Windows (including WSL), and Linux are supported
+
+> Note: We also recommend instead of npm using `yarn` instead of `npm`.
+> 
+Portal.js is built with React on top of Nextjs framework, so for a quick setup, you can bootstrap a  Nextjs app and install portal.js as demonstrated in the code below:
+
+```bash=
+## Create a react app
+npx create-next-app
+# or
+yarn create next-app
+```
+After the installation is complete, follow the instructions to start the development server. Try editing pages/index.js and see the result on your browser.
+
+> For more information on how to use create-next-app, you can review the [create-next-app](https://nextjs.org/docs/api-reference/create-next-app) documentation.
+
+Once you have Nextjs created, you can install portal.js:
+
+```bash=
+yarn add https://github.com/datopian/portal.js.git
+```
+
+You're now ready to use portal.js in your next app. To test portal.js, open your `index.js` file in the pages folder. By default you should have some autogenerated code in the `index.js` file:
+
+
+Which outputs a page with the following content:
+
+![](https://i.imgur.com/GVh0P6p.png)
+
+Now, we are going to do some clean up and add a table component. In the `index.js` file, import a [Table]() component from portal as shown below:
+
+```javascript
+import Head from 'next/head'
+import { Table } from 'portal' //import Table component
+import styles from '../styles/Home.module.css'
+
+export default function Home() {
+
+  const columns = [
+    { field: 'id', headerName: 'ID' },
+    { field: 'firstName', headerName: 'First name' },
+    { field: 'lastName', headerName: 'Last name' },
+    { field: 'age', headerName: 'Age' }
+  ];
+
+  const rows = [
+    { id: 1, lastName: 'Snow', firstName: 'Jon', age: 35 },
+    { id: 2, lastName: 'Lannister', firstName: 'Cersei', age: 42 },
+    { id: 3, lastName: 'Lannister', firstName: 'Jaime', age: 45 },
+    { id: 4, lastName: 'Stark', firstName: 'Arya', age: 16 },
+    { id: 7, lastName: 'Clifford', firstName: 'Ferrara', age: 44 },
+    { id: 8, lastName: 'Frances', firstName: 'Rossini', age: 36 },
+    { id: 9, lastName: 'Roxie', firstName: 'Harvey', age: 65 },
+  ];
+
+  return (
+    <div className={styles.container}>
+      <Head>
+        <title>Create Portal App</title>
+        <link rel="icon" href="/favicon.ico" />
+      </Head>
+
+      <h1 className={styles.title}>
+        Welcome to <a href="https://nextjs.org">Portal.JS</a>
+      </h1>
+
+      {/* Use table component */}
+      <Table data={rows} columns={columns} />
+
+    </div>
+  )
+}
+```
+
+Now, your page should look like the following:
+
+![](https://i.imgur.com/n0vSjY4.png)
+
+> **Note**: You can learn more about individual portal components, as well as their prop types in the [components reference](/docs/components).
+
+
+## Next Steps
+
+You can check out the following examples built with Portal.js.
+
+* [A portal for a single Frictionless dataset](/learn/ckan)
+* [A portal with a CKAN backend](/learn/single-frictionless-dataset)
+
+> The [`examples` directory](https://github.com/datopian/portal.js/tree/main/examples) is regularly updated with different portal examples. 
+
+You can also look at the full list of the available components that are provided by Portal.JS in [Components](/docs/components).
+
+
+## Reference Information
+
+* [Full list of the available components that are provided by Portal.JS](/docs/components)
+* [Reference](/docs/references)
+
+
+## Getting Help
+
+If you have questions about anything related to Portal.js, you're always welcome to ask our community on [GitHub Discussions](https://github.com/datopian/portal.js/discussions).
+
+

site/content/docs/components.md

@@ -0,0 +1,589 @@
+# Components Reference
+
+Portal.js supports many components that can help you build amazing data portals similar to [this](https://catalog-portal-js.vercel.app/) and [this](https://portal-js.vercel.app/). 
+
+In this section, we'll cover all supported components in depth, and help you understand their use as well as the expected properties. 
+
+Components are grouped under the following sections:
+* [UI](https://github.com/datopian/portal.js/tree/main/src/components/ui): Components like Nav bar, Footer, e.t.c 
+* [Dataset](https://github.com/datopian/portal.js/tree/main/src/components/dataset): Components used for displaying a Frictionless dataset and resources
+* [Search](https://github.com/datopian/portal.js/tree/main/src/components/search): Components used for building a search interface for datasets
+* [Blog](https://github.com/datopian/portal.js/tree/main/src/components/blog): Components for building a simple blog for datasets
+* [Views](https://github.com/datopian/portal.js/tree/main/src/components/views): Components like charts, tables, maps for generating data views
+* [Misc](https://github.com/datopian/portal.js/tree/main/src/components/misc): Miscellaneos components like errors, custom links, etc used for extra design. 
+
+### UI Components
+
+In the UI we group all components that can be used for building generic page sections. These are components for building sections like the Navigation bar, Footer, Side pane, Recent datasets, e.t.c.  
+
+#### [Nav Component](https://github.com/datopian/portal.js/blob/main/src/components/ui/Nav.js)
+
+To build a navigation bar, you can use the `Nav` component as demonstrated below:
+
+```javascript
+import { Nav } from 'portal'
+
+export default function Home(){
+
+ const navMenu = [{ title: 'Blog', path: '/blog' },
+                 { title: 'Search', path: '/search' }]
+ 
+ return (
+   <>
+    <Nav logo="/images/logo.png" navMenu={navMenu}/>
+    ...
+   </>
+ 
+ )
+}
+```
+
+#### Nav Component Prop Types
+
+Nav component accepts two properties:
+* **logo**: A string to an image path. Can be relative or absolute.
+* **navMenu**: An array of objects with title and path. E.g : {"[{ title: 'Blog', path: '/blog' },{ title: 'Search', path: '/search' }]"}
+
+
+#### [Recent Component](https://github.com/datopian/portal.js/blob/main/src/components/ui/Recent.js)
+
+The `Recent` component is used to display a list of recent [datasets](#Dataset) in the home page. This useful if you want to display the most recent dataset users have interacted with in your home page. 
+To build a recent dataset section, you can use the `Recent` component as demonstrated below:
+
+```javascript
+import { Recent } from 'portal'
+
+export default function Home() {
+
+  const datasets = [
+    {
+      organization: {
+        name: "Org1",
+        title: "This is the first org",
+        description: "A description of the organization 1"
+      },
+      title: "Data package title",
+      name: "dataset1",
+      description: "description of data package",
+      resources: [],
+    },
+    {
+      organization: {
+        name: "Org2",
+        title: "This is the second org",
+        description: "A description of the organization 2"
+      },
+      title: "Data package title",
+      name: "dataset2",
+      description: "description of data package",
+      resources: [],
+    },
+  ]
+
+  return (
+    <div>
+      {/* Use Recent component */}
+      <Recent datasets={datasets} />
+    </div>
+  )
+}
+
+```
+
+Note: The `Recent` component is hyperlinked with the dataset name of the organization and the dataset name in the following format: 
+
+> `/@<org name>/<dataset name>`
+
+For instance, using the example dataset above, the first component will be link to page:
+
+> `/@org1/dataset1`
+
+and the second will be linked to:
+
+> `/@org2/dataset2` 
+
+This is useful to know when generating dynamic pages for each dataset. 
+
+#### Recent Component Prop Types
+
+The `Recent` component accepts the following properties:
+* **datasets**: An array of [datasets](#Dataset)
+
+### Dataset Components
+
+The dataset component groups together components that can be used for building a dataset UI. These includes components for displaying info about a dataset, resources in a dataset as well as dataset ReadMe.
+
+#### [KeyInfo Component](https://github.com/datopian/portal.js/blob/main/src/components/dataset/KeyInfo.js)
+
+The `KeyInfo` components displays key properties like the number of resources, size, format, licences of in a dataset in tabular form. See example in the `Key Info` section [here](https://portal-js.vercel.app/). To use it, you can import the `KeyInfo` component as demonstrated below:
+```javascript
+import { KeyInfo } from 'portal'
+
+export default function Home() {
+
+  const datapackage = {
+    "name": "finance-vix",
+    "title": "VIX - CBOE Volatility Index",
+    "homepage": "http://www.cboe.com/micro/VIX/",
+    "version": "0.1.0",
+    "license": "PDDL-1.0",
+    "sources": [
+      {
+        "title": "CBOE VIX Page",
+        "name": "CBOE VIX Page",
+        "web": "http://www.cboe.com/micro/vix/historical.aspx"
+      }
+    ],
+    "resources": [
+      {
+        "name": "vix-daily",
+        "path": "vix-daily.csv",
+        "format": "csv",
+        "size": 20982,
+        "mediatype": "text/csv",
+      }
+    ]
+  }
+
+  return (
+    <div>
+      {/* Use KeyInfo component */}
+      <KeyInfo descriptor={datapackage} resources={datapackage.resources} />
+    </div>
+  )
+}
+
+```
+
+#### KeyInfo Component Prop Types
+
+KeyInfo component accepts two properties:
+* **descriptor**: A [Frictionless data package descriptor](https://specs.frictionlessdata.io/data-package/#descriptor)
+* **resources**: An [Frictionless data package resource](https://specs.frictionlessdata.io/data-resource/#introduction)
+
+
+#### [ResourceInfo Component](https://github.com/datopian/portal.js/blob/main/src/components/dataset/ResourceInfo.js)
+
+The `ResourceInfo` components displays key properties like the name, size, format, modification dates, as well as a download link in a resource object. See an example of a `ResourceInfo` component in the `Data Files` section [here](https://portal-js.vercel.app/).
+
+You can import and use the`ResourceInfo` component as demonstrated below:
+```javascript
+import { ResourceInfo } from 'portal'
+
+export default function Home() {
+
+  const resources = [
+    {
+      "name": "vix-daily",
+      "path": "vix-daily.csv",
+      "format": "csv",
+      "size": 20982,
+      "mediatype": "text/csv",
+    },
+    {
+      "name": "vix-daily 2",
+      "path": "vix-daily2.csv",
+      "format": "csv",
+      "size": 2082,
+      "mediatype": "text/csv",
+    }
+  ]
+
+  return (
+    <div>
+      {/* Use Recent component */}
+      <ResourceInfo resources={resources} />
+    </div>
+  )
+}
+```
+
+#### ResourceInfo Component Prop Types
+
+ResourceInfo component accepts a single property:
+* **resources**: An [Frictionless data package resource](https://specs.frictionlessdata.io/data-resource/#introduction)
+
+
+#### [ReadMe Component](https://github.com/datopian/portal.js/blob/main/src/components/dataset/Readme.js)
+
+The `ReadMe` component is used for displaying a compiled dataset Readme in a readable format. See example in the `README` section [here](https://portal-js.vercel.app/).
+
+> Note: By compiled ReadMe, we mean ReadMe that has been converted to plain string using a package like [remark](https://www.npmjs.com/package/remark).
+
+You can import and use the`ReadMe` component as demonstrated below:
+```javascript
+import { ReadMe } from 'portal'
+import remark from 'remark'
+import html from 'remark-html'
+import { useEffect, useState } from 'react'
+
+
+const readMeMarkdown = `
+    CBOE Volatility Index (VIX) time-series dataset including daily open, close,
+    high and low. The CBOE Volatility Index (VIX) is a key measure of market
+    expectations of near-term volatility conveyed by S&P 500 stock index option
+    prices introduced in 1993.
+
+    ## Data
+
+    From the [VIX FAQ][faq]:
+
+    > In 1993, the Chicago Board Options Exchange® (CBOE®) introduced the CBOE
+    > Volatility Index®, VIX®, and it quickly became the benchmark for stock market
+    > volatility. It is widely followed and has been cited in hundreds of news
+    > articles in the Wall Street Journal, Barron's and other leading financial
+    > publications. Since volatility often signifies financial turmoil, VIX is
+    > often referred to as the "investor fear gauge".
+
+    [faq]: http://www.cboe.com/micro/vix/faq.aspx
+
+    ## License
+
+    No obvious statement on [historical data page][historical]. Given size and
+    factual nature of the data and its source from a US company would imagine this
+    was public domain and as such have licensed the Data Package under the Public
+    Domain Dedication and License (PDDL).
+
+    [historical]: http://www.cboe.com/micro/vix/historical.aspx
+`
+
+export default function Home() {
+  const [readMe, setreadMe] = useState("")
+
+  useEffect(() => {
+    async function processReadMe() {
+      const processed = await remark()
+        .use(html)
+        .process(readMeMarkdown)
+      setreadMe(processed.toString())
+    }
+    processReadMe()
+  }, [])
+
+  return (
+    <div>
+      <ReadMe readme={readMe} />
+    </div>
+  )
+}
+
+```
+
+#### ReadMe Component Prop Types
+
+The `ReadMe` component accepts a single property:
+* **readme**: A string of a compiled ReadMe in html format. 
+
+### [View Components](https://github.com/datopian/portal.js/tree/main/src/components/views)
+
+View components is a set of components that can be used for displaying dataset views like charts, tables, maps, e.t.c. 
+
+#### [Chart Component](https://github.com/datopian/portal.js/blob/main/src/components/views/Chart.js)
+
+The `Chart` components exposes different chart components like Plotly Chart, Vega charts, which can be used for showing graphs. See example in the `Graph` section [here](https://portal-js.vercel.app/). 
+To use a chart component, you need to compile and pass a view spec as props to the chart component. 
+Each Chart type have their specific spec, as explained in this [doc](https://specs.frictionlessdata.io/views/#graph-spec).
+
+In the example below, we assume there's a compiled Plotly spec:
+
+```javascript
+import { PlotlyChart } from 'portal'
+
+export default function Home({plotlySpec}) {
+
+  return (
+    < div >
+      <PlotlyChart spec={plotlySpec} />
+    </div>
+  )
+}
+
+```
+> Note: You can compile views using the [datapackage-render](https://github.com/datopian/datapackage-views-js) library, as demonstrated in [this example](https://github.com/datopian/portal.js/blob/main/examples/dataset-frictionless/lib/utils.js).
+
+
+#### Chart Component Prop Types
+
+KeyInfo component accepts two properties:
+* **spec**: A compiled view spec depending on the chart type. 
+
+#### [Table Component](https://github.com/datopian/portal.js/blob/main/examples/dataset-frictionless/components/Table.js)
+
+The `Table` component is used for displaying dataset resources as a tabular grid. See example in the `Data Preview` section [here](https://portal-js.vercel.app/). 
+To use a Table component, you have to pass an array of data and columns as demonstrated below:
+
+```javascript
+import { Table } from 'portal' //import Table component
+
+export default function Home() {
+
+  const columns = [
+    { field: 'id', headerName: 'ID' },
+    { field: 'firstName', headerName: 'First name' },
+    { field: 'lastName', headerName: 'Last name' },
+    { field: 'age', headerName: 'Age' }
+  ];
+
+  const data = [
+    { id: 1, lastName: 'Snow', firstName: 'Jon', age: 35 },
+    { id: 2, lastName: 'Lannister', firstName: 'Cersei', age: 42 },
+    { id: 3, lastName: 'Lannister', firstName: 'Jaime', age: 45 },
+    { id: 4, lastName: 'Stark', firstName: 'Arya', age: 16 },
+    { id: 7, lastName: 'Clifford', firstName: 'Ferrara', age: 44 },
+    { id: 8, lastName: 'Frances', firstName: 'Rossini', age: 36 },
+    { id: 9, lastName: 'Roxie', firstName: 'Harvey', age: 65 },
+  ];
+
+  return (
+    <Table data={data} columns={columns} />
+  )
+}
+
+```
+> Note: Under the hood, Table component uses the [DataGrid Material UI table](https://material-ui.com/components/data-grid/), and as such all supported params in data and columns are supported. 
+
+
+#### Table Component Prop Types
+
+Table component accepts two properties:
+* **data**: An array of column names with properties: e.g {'[{field: "col1", headerName: "col1"}, {field: "col2", headerName: "col2"}]'}
+* **columns**: An array of data objects e.g. {'[ {col1: 1, col2: 2}, {col1: 5, col2: 7} ]'}
+
+
+### [Search Components](https://github.com/datopian/portal.js/tree/main/src/components/search)
+
+Search components groups together components that can be used for creating a search interface. This includes search forms, search item as well as search result list. 
+
+#### [Form Component](https://github.com/datopian/portal.js/blob/main/src/components/search/Form.js)
+
+The search`Form` component is a simple search input and submit button. See example of a search form [here](https://catalog-portal-js.vercel.app/search). 
+
+The search `form` requires a submit handler (`handleSubmit`). This handler function receives the search term, and handles actual search. 
+
+In the example below, we demonstrate how to use the `Form` component.
+
+```javascript
+import { Form } from 'portal'
+
+export default function Home() {
+
+  const handleSearchSubmit = (searchQuery) => {
+    // Write your custom code to perform search in db
+    console.log(searchQuery);
+  }
+
+  return (
+    <Form
+      handleSubmit={handleSearchSubmit} />
+  )
+}
+```
+
+#### Form Component Prop Types
+
+The `Form` component accepts a single property:
+* **handleSubmit**: A function that receives the search text, and can be customize to perform the actual search. 
+
+#### [Item Component](https://github.com/datopian/portal.js/blob/main/src/components/search/Item.js)
+
+The search`Item` component can be used to display a single search result. 
+
+In the example below, we demonstrate how to use the `Item` component.
+
+```javascript
+import { Item } from 'portal'
+
+export default function Home() {
+  const datapackage = {
+    "name": "finance-vix",
+    "title": "VIX - CBOE Volatility Index",
+    "homepage": "http://www.cboe.com/micro/VIX/",
+    "version": "0.1.0",
+    "description": "This is a test organization description",
+    "resources": [
+      {
+        "name": "vix-daily",
+        "path": "vix-daily.csv",
+        "format": "csv",
+        "size": 20982,
+        "mediatype": "text/csv",
+      }
+    ]
+  }
+
+  return (
+    <Item dataset={datapackage} />
+  )
+}
+```
+
+#### Item Component Prop Types
+
+The `Item` component accepts a single property:
+* **dataset**: A [Frictionless data package descriptor](https://specs.frictionlessdata.io/data-package/#descriptor)
+
+
+#### [ItemTotal Component](https://github.com/datopian/portal.js/blob/main/src/components/search/Item.js)
+
+The search`ItemTotal` is a simple component for displaying the total search result 
+
+In the example below, we demonstrate how to use the `ItemTotal` component.
+
+```javascript
+import { ItemTotal } from 'portal'
+
+export default function Home() {
+  //do some custom search to get results
+  const search = (text) => {
+    return [{ name: "data1" }, { name: "data2" }]
+  }
+  //get the total result count
+  const searchTotal = search("some text").length
+
+  return (
+    <ItemTotal count={searchTotal} />
+  )
+}
+```
+
+#### ItemTotal Component Prop Types
+
+The `ItemTotal` component accepts a single property:
+* **count**: An integer of the total number of results. 
+
+
+### [Blog Components](https://github.com/datopian/portal.js/tree/main/src/components/blog)
+
+These are group of components for building a portal blog. See example of portal blog [here](https://catalog-portal-js.vercel.app/blog)
+
+#### [PostList Components](https://github.com/datopian/portal.js/tree/main/src/components/misc)
+
+The `PostList` component is used to display a list of blog posts with the title and a short excerpts from the content.
+
+In the example below, we demonstrate how to use the `PostList` component.
+
+```javascript
+import { PostList } from 'portal'
+
+export default function Home() {
+
+  const posts = [
+    { title: "Blog post 1", excerpt: "This is the first blog excerpts in this list." },
+    { title: "Blog post 2", excerpt: "This is the second blog excerpts in this list." },
+    { title: "Blog post 3", excerpt: "This is the third blog excerpts in this list." },
+  ]
+  return (
+    <PostList posts={posts} />
+  )
+}
+```
+
+#### PostList Component Prop Types
+
+The `PostList` component accepts a single property:
+* **posts**: An array of post list objects with the following properties:
+    ```javascript
+    [
+        { 
+          title: "The title of the blog post",
+          excerpt: "A short excerpt from the post content",
+        },
+    ]
+    ```
+
+#### [Post Components](https://github.com/datopian/portal.js/tree/main/src/components/misc)
+
+The `Post` component is used to display a blog post. See an example of a blog post [here](https://catalog-portal-js.vercel.app/blog/nyt-pa-platformen-opdateringsfrekvens-og-andres-data)
+
+In the example below, we demonstrate how to use the `Post` component.
+
+```javascript
+import { Post } from 'portal'
+import * as dayjs from 'dayjs' //For converting UTC time to relative format
+import relativeTime from 'dayjs/plugin/relativeTime'
+
+dayjs.extend(relativeTime)
+
+export default function Home() {
+
+  const post = {
+    title: "This is a sample blog post",
+    content: `<h1>A simple header</h1>
+    The PostList component is used to display a list of blog posts
+              with the title and a short excerpts from the content.
+              In the example below, we demonstrate how to use the PostList component.`,
+    createdAt: dayjs().to(dayjs(1620649596902)),
+    featuredImage: "https://pixabay.com/get/ge9a766d1f7b5fe0eccbf0f439501a2cf2b191997290e7ab15e6a402574acc2fdba48a82d278dca3547030e0202b7906d_640.jpg"
+  }
+
+  return (
+    <Post post={post} />
+  )
+}
+```
+
+#### Post Component Prop Types
+
+The `Post` component accepts a single property:
+* **post**: An object with the following properties:
+```javascript
+  {
+    title: <The title of the blog post>
+    content: <The body of the blog post. Can be plain text or html>
+    createdAt: <The utc date when the post was last modified>
+    featuredImage: < Url/relative url to post cover image>
+  }
+```
+
+
+### [Misc Components](https://github.com/datopian/portal.js/tree/main/src/components/misc)
+
+These are group of miscellaneous/extra components for extending your portal. They include components like Errors, custom links, etc.
+
+#### [Error Component](https://github.com/datopian/portal.js/blob/main/src/components/misc/Error.js)
+
+The `Error` component is used to display a custom error message.
+
+In the example below, we demonstrate how to use the `Error` component.
+
+```javascript
+import { Error } from 'portal'
+
+export default function Home() {
+
+  return (
+    <Error message="An error occured when loading the file!" />
+  )
+}
+```
+
+#### Error Component Prop Types
+
+The `Error` component accepts a single property:
+* **message**: A string with the error message to display. 
+    
+    
+#### [Custom Component](https://github.com/datopian/portal.js/blob/main/src/components/misc/Error.js)
+
+The `CustomLink` component is used to create a link with a consistent style to other portal components. 
+
+In the example below, we demonstrate how to use the `CustomLink` component.
+
+```javascript
+import { CustomLink } from 'portal'
+
+export default function Home() {
+
+  return (
+    <CustomLink url="/blog" title="Goto Blog" />
+  )
+}
+```
+
+#### CustomLink Component Prop Types
+
+The `CustomLink` component accepts the following properties:
+
+* **url**: A string. The relative or absolute url of the link. 
+* **title**: A string. The title of the link
+

site/content/docs/dms/authentication.md

@@ -1,249 +0,0 @@
-# Authentication
-
-## Introduction
-
-The core function of authentication is to **Identify** Users of the Portal (in a federated way) so we can base access on their identity.
-
-There are 3 major conceptual components: Identity, Accounts and Sessions which come together in the following stages:
-
-* **Root Identity Determination:** Determine Identity often via Delegation
-* **Sessions:** Persistence of the identity in the web application in a secure way (without new identity determination on each request! I don't want to have to login via third party service every time)
-* **Account (aka profile):** Storing Related Account/Profile Information in our application (not in third party identity) eg. email, name (other preferences)
-  * This will get auto-created usually at first Identification
-  * In limited case this can be seen as a cache of info from Identity system (e.g. your email)
-  * However often richer info that is app specific that is generated (relevant for personalization)
-
-### Root Identity Determination options :key:
-
-The identity determination can be done in multiple ways. In this article we're considering following 3 options that we believe are widely used:
-
-- Password authentication - traditional username and password pair
-- Single Sign-on (SSO) via protocols such as OAuth, SAML, OpenID Connect
-- One-time password (OTP) via email or SMS (aka passwordless connection)
-
-#### Password authentication
-
-Traditional way of authentication of users. When signing up user provides at least username and password pair which is then stored in a database for future authentication processes. Normally, additional information such as email address, full name etc. is also requested when registering.
-
-Examples of password authentication in popular services:
-
-- GitHub - https://github.com/join
-- GitLab - https://gitlab.com/users/sign_up
-- NPM - https://www.npmjs.com/signup
-
-#### Single Sign-on (SSO)
-
-The way of delegating identity determination process to some third-party service. Normally, popular social network services are used, e.g., Google, Facebook, Twitter etc. SSO implementations can be done using OAuth or SAML protocols. In addition, there is OpenID Connect protocol which is an extension of OAuth2.0.
-
-- OAuth
-  - JWT based
-  - JSON based
-  - 'webby'
-- SAML
-  - XML based
-  - SOAP based
-  - 'enterprisey'
-
-List of OAuth providers:
-
-https://en.wikipedia.org/wiki/List_of_OAuth_providers
-
-Examples of SSO in popular projects:
-
-- https://datahub.io/login
-- https://vercel.com/signup
-
-#### One-time password (OTP)
-
-Also known as dynamic password, OTP also solves limitations of traditional password authentication method. Usually, the one time passwords are received via email or SMS.
-
-### Account (aka profile) 
-
-- Storage of user profile information (email, fullname, gravatar etc.)
-- Retrieving user profile information via API
-- Updating profile
-- Deleting profile
-
-### Sessions
-
-- Log out: DePersisting the Session
-- Invalidating all Sessions: e.g. if a security issue
-- Sessions outside of browsers
-
-## Key Job Stories
-
-When a user signs in, I want to know her/his identity so that I can limit access and editing based on who she/he is.
-
-When a user visits the data portal for the first time, I want to provide him/her a way to register easily/quickly so that more people uses the data portal.
-
-When I visit the data portal for the first time, I want to sign up using my existing social network account so that I don't need to remember yet another credentials.
-
-When I'm using the CLI app (or anything else outside browser), I want to be able to login so that I can work from the terminal (e.g., have write access: editing datasets etc.).
-
-[More job stories](#more-job-stories).
-
-## CKAN 2 (CKAN Classic)
-
-### Basic CKAN authentication
-
-In classic system, we have basic CKAN authentication. Below is how registration page looks like:
-
-![CKAN Classic register page](/static/img/docs/dms/ckan-register.png)
-
-Registration flow in CKAN Classic:
-
-```mermaid
-sequenceDiagram
-
-  user->>ckan: fill in the form and submit
-  ckan->>ckan: check access (if user can create user)
-  ckan->>ckan: parse params
-  ckan->>ckan: check recaptcha
-  ckan->>ckan: call 'user_create' action
-  ckan->>ckan.model: add a new user into db
-  ckan->>ckan: create an activity
-  ckan->>ckan: log the user
-  ckan->>user: redirect to dashboard
-```
-
-We can extend basic CKAN authentication with:
-
-- LDAP
-  - https://extensions.ckan.org/extension/ldap/
-  - https://github.com/NaturalHistoryMuseum/ckanext-ldap
-- OAuth - see below
-- SAML - https://extensions.ckan.org/extension/saml2/
-
-### CKAN Classic as OAuth client
-
-CKAN Classic can also be used as OAuth client:
-
-- https://github.com/conwetlab/ckanext-oauth2 - this is the only one that's maintained.
-- https://github.com/etalab/ckanext-oauth2 - outdated, the one above is based on this.
-- https://github.com/okfn/ckanext-oauth - last commit 9 years ago.
-- https://github.com/ckan/ckanext-oauth2waad - Windows Azure Active Directory specific and outdated.
-
-How it works:
-
-```mermaid
-sequenceDiagram
-
-  user->>ckan: request for login via OAuth provider
-  ckan->>ckan.oauth: raise 401 and call `challenge` function
-  ckan.oauth->>user: redirect the user to the 3rd party log in page
-  user->>3rdparty: perform login
-  3rdparty->>ckan.oauth: redirect to /oauth2/callback with token
-  ckan.oauth->>3rdparty: call `authenticate` with token
-  3rdparty->>ckan.oauth: return user info
-  ckan.oauth->>ckan: if doesn't exist save that info in db or update it
-  ckan.oauth->>ckan.oauth: add cookies
-  ckan.oauth->>user: redirect to dashboard
-```
-
-## CKAN 3 (Next Gen)
-
-We have considered some of popular and/or modern solutions for identity management that we can implement in CKAN 3:
-
-https://docs.google.com/spreadsheets/d/1qXZyzAbA2NtpnoSZRJ2K_EbaWJnvxkrKVzQ_2rD5eQw/edit#gid=0
-
-Shortlist based on scores from the spreadsheet above:
-
-- Auth0
-- AuthN
-- Ory/Kratos
-
-Recommendation:
-
-All projects from the shortlist can be considered for a project. It worth to give a try for each of them and find out what works best for your project's needs. Testing out Auth0 should be straightforward and take less than an hour. AuthN and Ory/Kratos would require to build docker images and to run it locally but overall it should not be time consuming.
-
-### Existing work
-
-In datahub.io we have implemented SSO via Google/Github. Below is sequence diagram showing the auth flow with datopian/auth + frontend express app (similar to CKAN 3 frontend):
-
-```mermaid
-sequenceDiagram
-
-  frontend.login->>auth.authenticate: authenticate(jwt=None,next=/success/...)
-  auth.authenticate->>frontend.login: failed + here are urls for logging on 3rd party including success
-  frontend.login->>user: login form with login urls to 3rd party including next url in state
-  user->>3rdparty: login
-  3rdparty->>auth.oauth_response: success
-  auth.oauth_response->>frontend.success: redirect to next url
-  frontend.success->>auth.authenticate: with valid jwt
-  auth.authenticate->>frontend.success: valid + here is profile
-  frontend.success->>frontend.success: decode jwt, check it, then see localstorage
-  frontend.success->>frontend.dashboard: redirect to dashboard
-```
-
-## CKAN 2 to CKAN 3 (aka Next Gen)
-
-How does this conceptual framework map to an evolution of CKAN 2 to CKAN 3?
-
-```mermaid
-graph TD
-
-subgraph "CKAN Classic"
-  Signup["Classic signup, e.g., self-service or by sysadmin"]
-  Login["Classic login if you're using the classic UI"]
-  OAuth["OAuth2(ORY/Hydra)"]
-end
-
-subgraph "Authentication service (ORY/Kratos)"
-  SSO["Social Sign-On: Github, Google, Facebook"]
-  CC["CKAN Classic"]
-  Admins["Sysadmin users"]
-  Curators["Data curators"]
-  Users["Regular users"]
-end
-
-subgraph "Frontend v3"
-  SignupFront["Signup via Kratos"]
-  LoginFront["Login via Kratos"]
-end
-
-SignupFront --"Regular user"--> SSO
-LoginFront --"Regular user"--> SSO
-
-LoginFront --"Data curator"--> CC
-
-CC --> Admins
-CC --> Curators
-SSO --> Users
-
-CC --"Redirect"--> OAuth
-OAuth --> Login
-```
-
-Sequence diagram of login process:
-
-[![](https://mermaid.ink/img/eyJjb2RlIjoic2VxdWVuY2VEaWFncmFtXG5cdEJyb3dzZXItPj5Gcm9udGVuZDogUmVxdWVzdCB0byBgL2F1dGgvbG9naW5gXG4gIEZyb250ZW5kLT4-S3JhdG9zOiBBdXRoIHJlcXVlc3RcbiAgS3JhdG9zLT4-QnJvd3NlcjogUmVkaXJlY3QgdG8gYC9hdXRoL2xvZ2luP3JlcXVlc3Q9e2lkfWAgcGFyYW1cbiAgQnJvd3Nlci0-PkZyb250ZW5kOiBHZXQgYC9hdXRoL2xvZ2luP3JlcXVlc3Q9e2lkfWBcbiAgRnJvbnRlbmQtPj5LcmF0b3M6IEZldGNoIGRhdGEgZm9yIHJlbmRlcmluZyB0aGUgZm9ybVxuICBLcmF0b3MtPj5Gcm9udGVuZDogTG9naW4gb3B0aW9uc1xuICBGcm9udGVuZC0-PkJyb3dzZXI6IFJlbmRlciB0aGUgbG9naW4gZm9ybSB3aXRoIGF2YWlsYWJsZSBvcHRpb25zXG4gIEJyb3dzZXItPj5Gcm9udGVuZDogU3VwcGx5IGZvcm0gZGF0YVxuICBGcm9udGVuZC0-PktyYXRvczogVmFsaWRhdGUgYW5kIGxvZ2luXG4gIEtyYXRvcy0-PkZyb250ZW5kOiBTZXQgc2Vzc2lvblxuICBGcm9udGVuZC0-PkJyb3dzZXI6IFJlZGlyZWN0IHRvIC9kYXNoYm9hcmRcblxuXG5cdFx0XHRcdFx0IiwibWVybWFpZCI6eyJ0aGVtZSI6ImRlZmF1bHQifSwidXBkYXRlRWRpdG9yIjpmYWxzZX0)](https://mermaid-js.github.io/mermaid-live-editor/#/edit/eyJjb2RlIjoic2VxdWVuY2VEaWFncmFtXG5cdEJyb3dzZXItPj5Gcm9udGVuZDogUmVxdWVzdCB0byBgL2F1dGgvbG9naW5gXG4gIEZyb250ZW5kLT4-S3JhdG9zOiBBdXRoIHJlcXVlc3RcbiAgS3JhdG9zLT4-QnJvd3NlcjogUmVkaXJlY3QgdG8gYC9hdXRoL2xvZ2luP3JlcXVlc3Q9e2lkfWAgcGFyYW1cbiAgQnJvd3Nlci0-PkZyb250ZW5kOiBHZXQgYC9hdXRoL2xvZ2luP3JlcXVlc3Q9e2lkfWBcbiAgRnJvbnRlbmQtPj5LcmF0b3M6IEZldGNoIGRhdGEgZm9yIHJlbmRlcmluZyB0aGUgZm9ybVxuICBLcmF0b3MtPj5Gcm9udGVuZDogTG9naW4gb3B0aW9uc1xuICBGcm9udGVuZC0-PkJyb3dzZXI6IFJlbmRlciB0aGUgbG9naW4gZm9ybSB3aXRoIGF2YWlsYWJsZSBvcHRpb25zXG4gIEJyb3dzZXItPj5Gcm9udGVuZDogU3VwcGx5IGZvcm0gZGF0YVxuICBGcm9udGVuZC0-PktyYXRvczogVmFsaWRhdGUgYW5kIGxvZ2luXG4gIEtyYXRvcy0-PkZyb250ZW5kOiBTZXQgc2Vzc2lvblxuICBGcm9udGVuZC0-PkJyb3dzZXI6IFJlZGlyZWN0IHRvIC9kYXNoYm9hcmRcblxuXG5cdFx0XHRcdFx0IiwibWVybWFpZCI6eyJ0aGVtZSI6ImRlZmF1bHQifSwidXBkYXRlRWRpdG9yIjpmYWxzZX0)
-
-From ORY/Kratos:
-
-[![](https://mermaid.ink/img/eyJjb2RlIjoic2VxdWVuY2VEaWFncmFtXG4gIHBhcnRpY2lwYW50IEIgYXMgQnJvd3NlclxuICBwYXJ0aWNpcGFudCBLIGFzIE9SWSBLcmF0b3NcbiAgcGFydGljaXBhbnQgQSBhcyBZb3VyIEFwcGxpY2F0aW9uXG5cblxuICBCLT4-SzogSW5pdGlhdGUgTG9naW5cbiAgSy0-PkI6IFJlZGlyZWN0cyB0byB5b3VyIEFwcGxpY2F0aW9uJ3MgL2xvZ2luIGVuZHBvaW50XG4gIEItPj5BOiBDYWxscyAvbG9naW5cbiAgQS0tPj5LOiBGZXRjaGVzIGRhdGEgdG8gcmVuZGVyIGZvcm1zIGV0Y1xuICBCLS0-PkE6IEZpbGxzIG91dCBmb3JtcywgY2xpY2tzIGUuZy4gXCJTdWJtaXQgTG9naW5cIlxuICBCLT4-SzogUE9TVHMgZGF0YSB0b1xuICBLLS0-Pks6IFByb2Nlc3NlcyBMb2dpbiBJbmZvXG5cbiAgYWx0IExvZ2luIGRhdGEgdmFsaWRcbiAgICBLLS0-PkI6IFNldHMgc2Vzc2lvbiBjb29raWVcbiAgICBLLT4-QjogUmVkaXJlY3RzIHRvIGUuZy4gRGFzaGJvYXJkXG4gIGVsc2UgTG9naW4gZGF0YSBpbnZhbGlkXG4gICAgSy0tPj5COiBSZWRpcmVjdHMgdG8geW91ciBBcHBsaWNhaXRvbidzIC9sb2dpbiBlbmRwb2ludFxuICAgIEItPj5BOiBDYWxscyAvbG9naW5cbiAgICBBLS0-Pks6IEZldGNoZXMgZGF0YSB0byByZW5kZXIgZm9ybSBmaWVsZHMgYW5kIGVycm9yc1xuICAgIEItLT4-QTogRmlsbHMgb3V0IGZvcm1zIGFnYWluLCBjb3JyZWN0cyBlcnJvcnNcbiAgICBCLT4-SzogUE9TVHMgZGF0YSBhZ2FpbiAtIGFuZCBzbyBvbi4uLlxuICBlbmRcbiIsIm1lcm1haWQiOnsidGhlbWUiOiJuZXV0cmFsIiwic2VxdWVuY2VEaWFncmFtIjp7ImRpYWdyYW1NYXJnaW5YIjoxNSwiZGlhZ3JhbU1hcmdpblkiOjE1LCJib3hUZXh0TWFyZ2luIjowLCJub3RlTWFyZ2luIjoxNSwibWVzc2FnZU1hcmdpbiI6NDUsIm1pcnJvckFjdG9ycyI6dHJ1ZX19fQ)](https://mermaid-js.github.io/mermaid-live-editor/#/edit/eyJjb2RlIjoic2VxdWVuY2VEaWFncmFtXG4gIHBhcnRpY2lwYW50IEIgYXMgQnJvd3NlclxuICBwYXJ0aWNpcGFudCBLIGFzIE9SWSBLcmF0b3NcbiAgcGFydGljaXBhbnQgQSBhcyBZb3VyIEFwcGxpY2F0aW9uXG5cblxuICBCLT4-SzogSW5pdGlhdGUgTG9naW5cbiAgSy0-PkI6IFJlZGlyZWN0cyB0byB5b3VyIEFwcGxpY2F0aW9uJ3MgL2xvZ2luIGVuZHBvaW50XG4gIEItPj5BOiBDYWxscyAvbG9naW5cbiAgQS0tPj5LOiBGZXRjaGVzIGRhdGEgdG8gcmVuZGVyIGZvcm1zIGV0Y1xuICBCLS0-PkE6IEZpbGxzIG91dCBmb3JtcywgY2xpY2tzIGUuZy4gXCJTdWJtaXQgTG9naW5cIlxuICBCLT4-SzogUE9TVHMgZGF0YSB0b1xuICBLLS0-Pks6IFByb2Nlc3NlcyBMb2dpbiBJbmZvXG5cbiAgYWx0IExvZ2luIGRhdGEgdmFsaWRcbiAgICBLLS0-PkI6IFNldHMgc2Vzc2lvbiBjb29raWVcbiAgICBLLT4-QjogUmVkaXJlY3RzIHRvIGUuZy4gRGFzaGJvYXJkXG4gIGVsc2UgTG9naW4gZGF0YSBpbnZhbGlkXG4gICAgSy0tPj5COiBSZWRpcmVjdHMgdG8geW91ciBBcHBsaWNhaXRvbidzIC9sb2dpbiBlbmRwb2ludFxuICAgIEItPj5BOiBDYWxscyAvbG9naW5cbiAgICBBLS0-Pks6IEZldGNoZXMgZGF0YSB0byByZW5kZXIgZm9ybSBmaWVsZHMgYW5kIGVycm9yc1xuICAgIEItLT4-QTogRmlsbHMgb3V0IGZvcm1zIGFnYWluLCBjb3JyZWN0cyBlcnJvcnNcbiAgICBCLT4-SzogUE9TVHMgZGF0YSBhZ2FpbiAtIGFuZCBzbyBvbi4uLlxuICBlbmRcbiIsIm1lcm1haWQiOnsidGhlbWUiOiJuZXV0cmFsIiwic2VxdWVuY2VEaWFncmFtIjp7ImRpYWdyYW1NYXJnaW5YIjoxNSwiZGlhZ3JhbU1hcmdpblkiOjE1LCJib3hUZXh0TWFyZ2luIjowLCJub3RlTWFyZ2luIjoxNSwibWVzc2FnZU1hcmdpbiI6NDUsIm1pcnJvckFjdG9ycyI6dHJ1ZX19fQ)
-
-
-Kratos to Hydra in CKAN Classic:
-
-WIP
-
-Questions
-
-* Does CKAN Classic allow us to store arbitrary account information (are there "extras")
-* How would we avoid having to support identity persistence, delegation etc in both NG frontend and Classic Admin UI?
-  * Can we share cookies (e.g. via using subdomains)
-* How is login, identity determination etc done at least for frontend in DataHub.io
-* Should account UI really be in NG frontend vs Classic Admin UI?
-* how can we handle "invite a user" to my org set up ... (it's basically post processing after sign up ...)
-
-## Appendix
-
-### More job stories
-
-When a user visits the data portal, I want to provide multiple options for him/her to sign up so that I have more users registered and using the data portal.
-
-When a user needs to change his/her profile info, I want to make sure it is possible, so that I have the up-to-date information about users.
-
-When my personal info (email etc.) is changed, I want to edit it in my profile so that I provide up-to-date information about me and I receive messages (eg, notifications) properly.
-
-When I decide to stop using the data portal, I want to be able to delete my account, so that my personal details aren't stored in the service that I don't need anymore.

site/content/docs/dms/blob-storage.md

@@ -1,215 +0,0 @@
-# Blob Storage
-
-## Introduction
-
-DMS and data portals often need to *store* data as well as metadata. As such, they require a system for doing this. This page focuses on Blob Storage aka Bulk or Raw storage (see [storage](/docs/dms/storage) page for an overview of all types of storage).
-
-Blob storage is for storing "blobs" of data, that is a raw stream of bytes like files on a filesystem. For blob storage think local filesystem or cloud storage like S3, GCS, etc.
-
-Blob Storage in a DMS can be provided via:
-
-* Local file system: storing on disk or storage directly connected to the instance
-* Cloud storage like S3, Google Cloud Storage, Azure storage etc
-
-Today, cloud storage would be the default in most cases.
-
-### Features
-
-* Storage: Persistent, cost-efficient storage
-* Download: Fast, reliable download (possibly even with support for edge distribution)
-* Upload: reliable and rapid upload 
-  * Direct upload to (cloud) storage by clients i.e. without going via the DMS. Why? Because cloud storage has many features that it would be costly replicate (e.g. multipart, resumable etc), excellent performance and reliability for upload. It also cuts out the middleman of the DMS backend thereby saving bandwidth, reducing load on the DMS backend and improving performance
-  * Upload UI: having an excellent UI for doing upload. NB: this UI is considered part of the [publish feature](/docs/dms/publish)
-* Cloud: integrate with cloud storage
-* Permissions: restricting access to data stored in blob storage based on the permissions of the DMS. For example, if Joe does not have access to a dataset on the DMS he should not be able to access associated blob data in the storage system
-
-## Flows
-
-### Direct to Cloud Upload
-
-Want: Direct upload to cloud storage ... But you need to authorize that ... So give them a token from your app
-
-A sequence diagram illustrating the process for a direct to cloud upload:
-
-```mermaid
-sequenceDiagram
-
-participant Browser as Client (Browser / Code)
-participant Authz as Authz Server
-participant BitStore as Storage Access Token Service
-participant Storage as Cloud Storage
-
-  Browser->>Authz: Give me a BitStore access token
-  Authz->>Browser: Token
-  Browser->>BitStore: Get a signed upload URL (access token, file metdata)
-  BitStore->>Browser: Signed URL
-  Browser->>Storage: Upload file (signed URL)
-  Storage->>Browser: OK (storage metadata)
-```
-
-Here's a more elaborate version showing storage of metadata into the MetaStore afterwards (and skipping the Authz service):
-
-```mermaid
-sequenceDiagram
-
-  participant browser as Client (Browser / Code)
-  participant vfts as MetaStore
-  participant bitstore as Storage Access Token Service
-  participant storage as Cloud Storage
-  
-  browser->>browser: Select files to upload
-  browser->>browser: calculate file hashes (if doing content addressable)
-  browser->bitstore: get signed URLs(file1.csv URL, file2.csv URL, auth info)
-  bitstore->>browser: signed URLs
-  browser->>storage: upload file1.csv
-  storage->>browser: OK
-  browser->>storage: upload file2.csv
-  storage->>browser: OK
-  browser->>browser: Compose datapackage.json
-  browser->>vfts: create dataset(datapackage.json, file1.csv pointer, file2.csv pointer, jwt token, ...)
-  vfts->>browser: OK
-```
-
-## CKAN 2 (Classic)
-
-Blob Storage is known as the FileStore in CKAN v2 and below. The default is local disk storage.
-
-There is support for cloud storage via a variety of extensions the most prominent of which is `ckanext-cloudstorage`: https://github.com/TkTech/ckanext-cloudstorage
-
-There are a variety of issues:
-
-* Cloud storage is not a first class citizen in CKAN: CKAN defaults to local file storage but cloud storage is the default in the world and has much better scalability, performance as well as integratability with cloud deployment
-* The FileStore interface definition has a poor separation of concerns (for example, blob storage file paths is set in the FileStore component not in core CKAN) which makes it hard / hacky to extend and use for key use cases e.g. versioning.
-* `ckanext-cloudstorage` (the default cloud storage extension) is ok but has many issues e.g.
-  * No direct to cloud upload: it uses CKAN backend as a middleman so all data must go via ckan backend
-  * Implements its own (sometimes unreliable) version of multipart upload (which means additional code which isn't as reliable as cloud storage providers interface)
-  * No access to advanced features such as resumability etc
-
-Generally, we at Datopian have seen a lot of issues around multipart / large file upload stability with clients and are still seeing issues when a lot of large files are uploaded via scripts. Fixing and refactoring code related to storage is very costly, and tends to result in client specific "hacks".
-
-## CKAN v3
-
-An approach to blob storage that leverages cloud blob storage directly (i.e. without having to upload and serve all files via the CKAN web server), unlocking the performance characteristics of the storage backend directly. It is designed with a microservice approach and supports direct to cloud uploads and downloads. The key components are listed in the next section. You can read more about the overall design approach in the [design section below](#Design).
-
-It is backwards compatible with CKAN v2 and has been successfully deployed with CKAN v2.8 and v2.9.
-
-**Status: Production.**
-
-### Components
-
-* [ckanext-blob-storage](https://github.com/datopian/ckanext-blob-storage) (formerly known as ckanext-external-storage)
-  * Hooking CKAN to Giftless replacing resource storage
-  * Depends on giftless-client and ckanext-authz-service
-  * Doesn't implement IUploader - completely overrides upload / download routes for resources
-* [Giftless](https://github.com/datopian/giftless) - Git LFS compatible implementation for storage with some extras on top. This hands out access tokens to store data in cloud storage.
-  * Docs at https://giftless.datopian.com
-  * Backends for Azure, Google Cloud Storage and local
-  * Multipart support (on top of standard LFS protocol)
-  * Accepts JWT tokens for authentication and authorization
-* [ckanext-authz-service](https://github.com/datopian/ckanext-authz-service/) - This extension uses CKAN’s built-in authentication and authorization capabilities to: a) Generate JWT tokens and provide them via CKAN’s Web API to clients and b) Validate JWT tokens.
-  * Allows hooking CKAN's authentication and authorization capabilities to generate signed JWT tokens, to integrate with external systems
-  * Not specific for Giftless, but this is what it was built for
-* [ckanext-asset-storage](https://github.com/datopian/ckanext-asset-storage) - this takes care of storing non-data assets e.g. organization images etc.
-  * CKAN IUploader for assets (not resources!)
-  * Pluggable backends - currently local and Azure
-  * Much cleaner than older implementations (ckanext-cloudstorage etc.)
-
-Clients:
-
-* [giftless-client-py](https://github.com/datopian/giftless-client) - Python client for Git LFS and Giftless-specific features
-  * Used by ckanext-blob-storage and other tools
-* [giftless-client-js](https://github.com/datopian/giftless-client-js) - Javascript client for Git LFS and Giftless-specific features
-  * Used by ckanext-blob-storage and other tools for creating uploaders in the UI
-
-## Design
-
-### Purpose
-
-The goal of this project is to create a more **_flexible_** system for storing **_data files_** (AKA “resources”) for **_CKAN_ and _other implementations_** of a data portal so that CKAN can support versioning, large file upload (and great file upload UX), plug easily into cloud and local file storage backends and, in general, is easy to customize both for storage layer and for CKAN client code of that layer
-
-### Features
-
-* Do one thing and do it well: provide an API to store and retrieve files from storage, in a way that is pluggable into a micro-services based application and to existing CKAN (2.8 / 2.9)
-* Does not force, and in fact is not aware of, a specific file naming logic (i.e. resource file names could be based on a user given name, a content hash, a revision ID or any mixture of these - it is up to the using system to decide)
-* Does not force a specific storage backend; Should support Amazon S3, Azure Storage and local file storage in some way initially but in general backend should be pluggable
-* Does not force a specific authentication scheme; Expects a signed JWT token, does not care who signed it and how the user got authenticated
-* Does not force complex authorization scheme; Leave it to external system to do complex authorization if needed;
-  * By default, the system can work in an “admin party” mode where all authenticated users have full access to all files. This will be “good enough” for many DMS implementations including CKAN.
-  * Potentially, allow plugging in a more complex authorization logic that relies on JWT claims to perform granular authorization checks
-
-### For Data Files (i.e. Blobs)
-
-This system is about storing and providing access to blobs, or streams of bytes; It is not about providing access to the data stored within (i.e. it is not meant to replace CKAN’s datastore).
-
-### For CKAN – whilst not necessarily CKAN Specific
-
-While the system’s design should not be CKAN specific in any way, our current client needs require us to provide a CKAN extension that integrates with this system.
-
-CKAN’s current IUploader interface has been identified to be too narrow to provide the functionality required by complex projects (resource versioning, direct cloud uploads and downloads, large file support and multipart support). While some of these needs could be and have been “hacked” through the IUploader interface, the implementations have been over complex and hard to debug.
-
-Our goal should be to provide a CKAN extension that provides the following functionality directly:
-
-* Uploading and downloading resource files directly from the client if supported by the storage backend
-  *   Multipart upload support if supported by storage backend
-  *   Handling of signed URLs for uploads and private downloads
-  *   Client side code for handling multipart uploads
-  *   TBD: If storage backend does not support direct uploads / downloads, fall back to …
-
-In addition, this extension should provide an API for other extensions to do things like:
-
-*   Set the file naming scheme (We need this for ckanext-versions)
-*   Lower level file access, e.g. move and delete files. We may need this in the future to optimize storage and deduplicate files as proposed for ckanext-versions
-
-In addition, this extension must “play nice” with common CKAN features such as the datastore extension and related datapusher / xloader extensions.
-
-### Usable For other DMS implementations
-
-There should be nothing in this system, except for the CKAN extension described above, that is specific to CKAN. That will allow to re-use and re-integrate this system as a micro-service in other DMS implementations such as ckan-ng and others.
-In fact, the core part of this system should be a generic, abstract storage service with a light authorization layer. This could make it useful in a host of situations where storage micro-service is needed.
-
-### High Level Principles
-
-Common Principles
-
-* Uploads and downloads directly from cloud provides to browser
-* Signed uploads / downloads - for private / authorized only data access
-* Support for AWS, Azure and potentially GCP storage
-* Support for local (non cloud) storage, potentially through a system like [https://min.io/](https://min.io/)
-* Multipart / large file upload support (a few GB in size should be supported for Gates)
-* Not opinionated about file naming / paths; Allow users to set file locations under some pre-defined patchs / buckets
-* Client side support - browser widgets / code for uploading and downloading files / multipart uploads directly to different backends
-* Well-documented flow for using from API (not browser)
-* Provided API for deleting and moving files
-* Provided API for accessing storage-level metadata (e.g. file MD5) (do we need this could be useful for processes that do things like deduplicate storage)
-* Provided API for managing storage-level object level settings (e.g. “Content-disposition” / “Content-type” headers, etc.)
-* Authorization based on some kind of portable scheme (JWT)
-
-CKAN integration specific (implemented as a CKAN extension)
-
-* JWT generation based on current CKAN user permissions
-* Client widgets integration (or CKAN specific widgets) in right places in CKAN templates
-* Hook into resource upload / download / deletion controllers in CKAN
-* API to allow other extensions to control storage level object metadata (headers, path)
-* API to allow other extensions to hook into lifecycle events - upload completion, download request, deletion etc.
-
-
-### Components
-
-The Decoupled Storage solution should be split into several parts, with some parts being independent of others:
-
-* [External] Cloud Storage service (or API similar if local file system) e.g. S3, GCS, Azure Storage, Min.io (for local file system)
-* Cloud Storage Access Service
-* [External] Permissions Service for granting general permission tokens that give access to Cloud Storage Access Service
-  * JWT tokens can be generated by any party that has the right signing key. Thus, we can initially do without this if JWT signing is implemented as part of the CKAN extension
-* Browser based Client for Cloud Storage (compatible with #1 and with different cloud vendors)
-* CKAN extension that wraps the two parts above to provide a storage solution for CKAN
-
-### Questions
-
-* What is file structure in cloud ... i.e. What is the file path for uploaded files? Options:
-  * Client chooses a name/path
-  * Content addressable i.e. the name is given by the content? How? Use a hash.]
-    * Beauty of that: standard way to name things. The same thing has the same name (modulo collisions)
-    * Goes with versioning => same file = same name, diff file = diff name
-* And do you enforce that from your app
-  * Request for token needs to include the destination file path

site/content/docs/dms/ckan-client-guide/index.md

@@ -1,503 +0,0 @@
-# CKAN Client Guide
-
-Guide to interacting with [CKAN](/docs/dms/ckan) for power users such as data scientists, data engineers and data wranglers.
-
-This guide is about adding and managing data in CKAN programmatically and it assumes:
-
-* You are familiar with key concepts like metadata, data, etc.
-* You are working programmatically with a programming language such as Python, JavaScript or R (_coming soon_).
-
-## Frictionless Formats
-
-Clients use [Frictionless formats](https://specs.frictionlessdata.io/) by default for describing dataset and resource objects passed to client methods. Internally, we then use the a *CKAN {'<=>'} Frictionless Mapper* (both [in JavaScript]( https://github.com/datopian/frictionless-ckan-mapper-js ) and [in Python](https://github.com/frictionlessdata/frictionless-ckan-mapper)) to convert objects to CKAN formats before calling the API. **Thus, you can use _Frictionless Formats_ by default with the client**.
-
->[!tip]As CKAN moves to Frictionless to default this will gradually become unnecessary.
-
-## Quick start
-
-Most of this guide has Python programming language in mind, including its [convention regading using _snake case_ for instances and methods names](https://www.python.org/dev/peps/pep-0008/#descriptive-naming-styles).
-
-If needed, you can adapt the instructions to JavaScript and R (coming soon) by using _camel case_ instead — for example, if in the Python code we have  `client.push_blob(…)`, in JavaScript it would be `client.pushBlob(…)`.
-
-### Prerequisites
-
-Install the client for your language of choice:
-
-* Python: https://github.com/datopian/ckan-client-py#install
-* JavaScript: https://github.com/datopian/ckan-client-js#install
-* R: _coming soon_
-
-### Create a client
-
-#### Python
-
-```python
-from ckanclient import Client
-
-
-api_key = '771a05ad-af90-4a70-beea-cbb050059e14'
-api_url = 'http://localhost:5000'
-organization = 'datopian'
-dataset = 'dailyprices'
-lfs_url = 'http://localhost:9419'
-
-client = Client(api_url, organization, dataset, lfs_url)
-```
-
-#### JavaScript
-
-```javascript
-const { Client } = require('ckanClient')
-
-apiKey = '771a05ad-af90-4a70-beea-cbb050059e14'
-apiUrl = 'http://localhost:5000'
-organization = 'datopian'
-dataset = 'dailyprices'
-
-const client = Client(apiKey, organization, dataset, apiUrl)
-```
-
-### Upload a resource
-
-That is to say, upload a file, implicitly creating a new dataset.
-
-#### Python
-
-```python
-from frictionless import describe
-
-
-resource = describe('my-data.csv')
-client.push_blob(resource)
-```
-
-### Create a new empty Dataset with metadata
-
-#### Python
-
-```python
-client.create('my-data')
-client.push(resource)
-```
-
-### Adding a resource to an existing Dataset
-
->[!note]Not implemented yet.
-
-
-```python
-client.create('my-data')
-client.push_resource(resource)
-```
-
-### Edit a Dataset's metadata
-
->[!note]Not implemented yet.
-
-
-```python
-dataset = client.retrieve('sample-dataset')
-client.update_metadata(
-    dataset,
-    metadata: {'maintainer_email': 'sample@datopian.com'}
-)
-```
-
-For details of metadata see the [metadata reference below](#metadata-reference).
-
-## API - Porcelain
-
-### `Client.create`
-
-Expects as a single argument: a _string_, or a _dict_ (in Python), or an _object_ (in JavaScript). This argument is either a valid dataset name or dictionary with metadata for the dataset in Frictionless format.
-
-### `Client.push`
-
-Expects a single argument: a _dict_ (in Python) or an _object_ (in JavaScript) with a dataset metadata in Frictionless format.
-
-### `Client.retrieve`
-
-Expects a single argument: a string with a dataset name or uniquer ID. Returns a Frictionless resource as a _dict_ (in Python) or as an _Promisse .&lt;object&gt;_ (in JavaScript).
-
-### `Client.push_blob`
-
-Expects a single argument: a _dict_ (in Python) or an _object_ (in JavaScript) with a Frictionless resource.
-
-## API - Plumbing
-
-### `Client.action`
-
-This method bridges access to the CKAN API _action endpoint_.
-
-#### In Python
-
-Arguments:
-
-| Name                 | Type       | Default    | Description                                                  |
-| -------------------- | ---------- | ---------- | ------------------------------------------------------------ |
-| `name`               | `str`      | (required) | The action name, for example, `site_read`, `package_show`…   |
-| `payload`            | `dict`     | (required) | The payload being sent to CKAN. When a payload is provided to a GET request, it will be converted to URL parameters and each key will be converted to snake case. |
-| `http_get`           | `bool`     | `False`    | Optional, if `True` will make `GET` request, otherwise `POST`. |
-| `transform_payload`  | `function` | `None`     | Function to mutate the `payload` before making the request (useful to convert to and from CKAN and Frictionless formats). |
-| `transform_response` | `function` | `None`     | function to mutate the response data before returning it (useful to convert to and from CKAN and Frictionless formats). |
-
->[!note]The CKAN API uses the CKAN dataset and resource formats (rather than Frictionless formats).
-In other words, to stick to Frictionless formats, you can pass `frictionless_ckan_mapper.frictionless_to_ckan` as `transform_payload`, and `frictionless_ckan_mapper.ckan_to_frictionless` as `transform_response`.
-
-
-#### In JavaScript
-
-Arguments:
-
-| Name         | Type                | Default            | Description                                                  |
-| ------------ | ------------------- | ------------------ | ------------------------------------------------------------ |
-| `actionName` | <code>string</code> | (required)         | The action name, for example, `site_read`, `package_show`…   |
-| `payload`    | <code>object</code> | (required)         | The payload being sent to CKAN. When a payload is provided to a GET request, it will be converted to URL parameters and each key will be converted to snake case. |
-| `useHttpGet` | <code>object</code> | <code>false</code> | Optional, if `True` will make `GET` request, otherwise `POST`. |
-
->[!note]The JavaScript implementation uses the CKAN dataset and resource formats (rather than Frictionless formats).
-In other words, to stick to Frictionless formats, you need to convert from Frictionless to CKAN before calling `action` , and from CKAN to Frictionless after calling `action`.
-
-## Metadata reference
-
->[!info]Your site may have custom metadata that differs from the example set below.
-
-
-### Profile
-
-**(`string`)** Defaults to _data-resource_.
-
-The profile of this descriptor.
-
-Every Package and Resource descriptor has a profile. The default profile, if none is declared, is `data-package` for Package and `data-resource` for Resource.
-
-#### Examples
-
-- `{"profile":"tabular-data-package"}`
-
-- `{"profile":"http://example.com/my-profiles-json-schema.json"}`
-
-### Name
-
-**(`string`)**
-
-An identifier string. Lower case characters with `.`, `_`, `-` and `/` are allowed.
-
-This is ideally a url-usable and human-readable name. Name `SHOULD` be invariant, meaning it `SHOULD NOT` change when its parent descriptor is updated.
-
-#### Example
-
-- `{"name":"my-nice-name"}`
-
-### Path
-
-A reference to the data for this resource, as either a path as a string, or an array of paths as strings. of valid URIs.
-
-The dereferenced value of each referenced data source in `path` `MUST` be commensurate with a native, dereferenced representation of the data the resource describes. For example, in a *Tabular* Data Resource, this means that the dereferenced value of `path` `MUST` be an array.
-
-#### Validation
-
-##### It must satisfy one of these conditions
-
-###### Path
-
-**(`string`)**
-
-A fully qualified URL, or a POSIX file path..
-
-Implementations need to negotiate the type of path provided, and dereference the data accordingly.
-
-**Examples**
-
-- `{"path":"file.csv"}`
-
-- `{"path":"http://example.com/file.csv"}`
-
-**(`array`)**
-
-**Examples**
-
-- `["file.csv"]`
-
-- `["http://example.com/file.csv"]`
-
-#### Examples
-
-- `{"path":["file.csv","file2.csv"]}`
-
-- `{"path":["http://example.com/file.csv","http://example.com/file2.csv"]}`
-
-- `{"path":"http://example.com/file.csv"}`
-
-### Data
-
-Inline data for this resource.
-
-### Schema
-
-**(`object`)**
-
-A schema for this resource.
-
-### Title
-
-**(`string`)**
-
-A human-readable title.
-
-#### Example
-
-- `{"title":"My Package Title"}`
-
-### Description
-
-**(`string`)**
-
-A text description. Markdown is encouraged.
-
-#### Example
-
-- `{"description":"# My Package description\nAll about my package."}`
-
-### Home Page
-
-**(`string`)**
-
-The home on the web that is related to this data package.
-
-#### Example
-
-- `{"homepage":"http://example.com/"}`
-
-### Sources
-
-**(`array`)**
-
-The raw sources for this resource.
-
-#### Example
-
-- `{"sources":[{"title":"World Bank and OECD","path":"http://data.worldbank.org/indicator/NY.GDP.MKTP.CD"}]}`
-
-### Licenses
-
-**(`array`)**
-
-The license(s) under which the resource is published.
-
-This property is not legally binding and does not guarantee that the package is licensed under the terms defined herein.
-
-#### Example
-
-- `{"licenses":[{"name":"odc-pddl-1.0","path":"http://opendatacommons.org/licenses/pddl/","title":"Open Data Commons Public Domain Dedication and License v1.0"}]}`
-
-### Format
-
-**(`string`)**
-
-The file format of this resource.
-
-`csv`, `xls`, `json` are examples of common formats.
-
-#### Example
-
-- `{"format":"xls"}`
-
-### Media Type
-
-**(`string`)**
-
-The media type of this resource. Can be any valid media type listed with [IANA](https://www.iana.org/assignments/media-types/media-types.xhtml).
-
-#### Example
-
-- `{"mediatype":"text/csv"}`
-
-### Encoding
-
-**(`string`)** Defaults to _utf-8_.
-
-The file encoding of this resource.
-
-#### Example
-
-- `{"encoding":"utf-8"}`
-
-### Bytes
-
-**(`integer`)**
-
-The size of this resource in bytes.
-
-#### Example
-
-- `{"bytes":2082}`
-
-### Hash
-
-**(`string`)**
-
-The MD5 hash of this resource. Indicate other hashing algorithms with the {'{algorithm}'}:{'{hash}'} format.
-
-#### Examples
-
-- `{"hash":"d25c9c77f588f5dc32059d2da1136c02"}`
-
-- `{"hash":"SHA256:5262f12512590031bbcc9a430452bfd75c2791ad6771320bb4b5728bfb78c4d0"}`
-
-## Generating templates
-
-You can use [`jsv`](https://github.com/datopian/jsv) to generate a template  script in Python, JavaScript, and R.
-
-To install it:
-
-```
-$ npm install -g git+https://github.com/datopian/jsv.git
-```
-
-### Python
-
-```
-$ jsv data-resource.json --output py
-```
-
-**Output**
-```python
-dataset_metadata = {
-    "profile": "data-resource",  # The profile of this descriptor.
-    # [example] "profile": "tabular-data-package"
-    # [example] "profile": "http://example.com/my-profiles-json-schema.json"
-    "name": "my-nice-name",  # An identifier string. Lower case characters with `.`, `_`, `-` and `/` are allowed.
-    "path": ["file.csv","file2.csv"],  # A reference to the data for this resource, as either a path as a string, or an array of paths as strings. of valid URIs.
-    # [example] "path": ["http://example.com/file.csv","http://example.com/file2.csv"]
-    # [example] "path": "http://example.com/file.csv"
-    "data": None,  # Inline data for this resource.
-    "schema": None,  # A schema for this resource.
-    "title": "My Package Title",  # A human-readable title.
-    "description": "# My Package description\nAll about my package.",  # A text description. Markdown is encouraged.
-    "homepage": "http://example.com/",  # The home on the web that is related to this data package.
-    "sources": [{"title":"World Bank and OECD","path":"http://data.worldbank.org/indicator/NY.GDP.MKTP.CD"}],  # The raw sources for this resource.
-    "licenses": [{"name":"odc-pddl-1.0","path":"http://opendatacommons.org/licenses/pddl/","title":"Open Data Commons Public Domain Dedication and License v1.0"}],  # The license(s) under which the resource is published.
-    "format": "xls",  # The file format of this resource.
-    "mediatype": "text/csv",  # The media type of this resource. Can be any valid media type listed with [IANA](https://www.iana.org/assignments/media-types/media-types.xhtml).
-    "encoding": "utf-8",  # The file encoding of this resource.
-    # [example] "encoding": "utf-8"
-    "bytes": 2082,  # The size of this resource in bytes.
-    "hash": "d25c9c77f588f5dc32059d2da1136c02",  # The MD5 hash of this resource. Indicate other hashing algorithms with the {algorithm}:{hash} format.
-    # [example] "hash": "SHA256:5262f12512590031bbcc9a430452bfd75c2791ad6771320bb4b5728bfb78c4d0"
-}
-```
-
-
-### JavaScript
-
-```
-$ jsv data-resource.json --output js
-```
-
-**Output**
-```javascript
-const datasetMetadata = {
-  // The profile of this descriptor.
-  profile: "data-resource",
-  // [example] profile: "tabular-data-package"
-  // [example] profile: "http://example.com/my-profiles-json-schema.json"
-  // An identifier string. Lower case characters with `.`, `_`, `-` and `/` are allowed.
-  name: "my-nice-name",
-  // A reference to the data for this resource, as either a path as a string, or an array of paths as strings. of valid URIs.
-  path: ["file.csv", "file2.csv"],
-  // [example] path: ["http://example.com/file.csv","http://example.com/file2.csv"]
-  // [example] path: "http://example.com/file.csv"
-  // Inline data for this resource.
-  data: null,
-  // A schema for this resource.
-  schema: null,
-  // A human-readable title.
-  title: "My Package Title",
-  // A text description. Markdown is encouraged.
-  description: "# My Package description\nAll about my package.",
-  // The home on the web that is related to this data package.
-  homepage: "http://example.com/",
-  // The raw sources for this resource.
-  sources: [
-    {
-      title: "World Bank and OECD",
-      path: "http://data.worldbank.org/indicator/NY.GDP.MKTP.CD",
-    },
-  ],
-  // The license(s) under which the resource is published.
-  licenses: [
-    {
-      name: "odc-pddl-1.0",
-      path: "http://opendatacommons.org/licenses/pddl/",
-      title: "Open Data Commons Public Domain Dedication and License v1.0",
-    },
-  ],
-  // The file format of this resource.
-  format: "xls",
-  // The media type of this resource. Can be any valid media type listed with [IANA](https://www.iana.org/assignments/media-types/media-types.xhtml).
-  mediatype: "text/csv",
-  // The file encoding of this resource.
-  encoding: "utf-8",
-  // [example] encoding: "utf-8"
-  // The size of this resource in bytes.
-  bytes: 2082,
-  // The MD5 hash of this resource. Indicate other hashing algorithms with the {algorithm}:{hash} format.
-  hash: "d25c9c77f588f5dc32059d2da1136c02",
-  // [example] hash: "SHA256:5262f12512590031bbcc9a430452bfd75c2791ad6771320bb4b5728bfb78c4d0"
-};
-```
-
-### R
-
-```
-$ jsv data-resource.json --output r
-```
-
-**Output** 
-```r
-# The profile of this descriptor.
-profile <- "data-resource"
-# [example] profile <- "tabular-data-package"
-# [example] profile <- "http://example.com/my-profiles-json-schema.json"
-# An identifier string. Lower case characters with `.`, `_`, `-` and `/` are allowed.
-name <- "my-nice-name"
-# A reference to the data for this resource, as either a path as a string, or an array of paths as strings. of valid URIs.
-path <- ["file.csv","file2.csv"]
-# [example] path <- ["http://example.com/file.csv","http://example.com/file2.csv"]
-# [example] path <- "http://example.com/file.csv"
-# Inline data for this resource.
-data <- NA
-# A schema for this resource.
-schema <- NA
-# A human-readable title.
-title <- "My Package Title"
-# A text description. Markdown is encouraged.
-description <- "# My Package description\nAll about my package."
-# The home on the web that is related to this data package.
-homepage <- "http://example.com/"
-# The raw sources for this resource.
-sources <- [{"title":"World Bank and OECD","path":"http://data.worldbank.org/indicator/NY.GDP.MKTP.CD"}]
-# The license(s) under which the resource is published.
-licenses <- [{"name":"odc-pddl-1.0","path":"http://opendatacommons.org/licenses/pddl/","title":"Open Data Commons Public Domain Dedication and License v1.0"}]
-# The file format of this resource.
-format <- "xls"
-# The media type of this resource. Can be any valid media type listed with [IANA](https://www.iana.org/assignments/media-types/media-types.xhtml).
-mediatype <- "text/csv"
-# The file encoding of this resource.
-encoding <- "utf-8"
-# [example] encoding <- "utf-8"
-# The size of this resource in bytes.
-bytes <- 2082L
-# The MD5 hash of this resource. Indicate other hashing algorithms with the {algorithm}:{hash} format.
-hash <- "d25c9c77f588f5dc32059d2da1136c02"
-# [example] hash <- "SHA256:5262f12512590031bbcc9a430452bfd75c2791ad6771320bb4b5728bfb78c4d0"
-
-```
-
-
-## Design Principles
-
-The client **should** use Frictionless formats by default for describing dataset and resource objects passed to client methods.
-
-In addition, where more than metadata is needed (e.g., we need to access the data stream, or get the schema) we expect the _Dataset_ and _Resource_ objects to follow the [Frictionless Data Lib pattern](https://github.com/frictionlessdata/project/blob/master/rfcs/0004-frictionless-data-lib-pattern.md).

site/content/docs/dms/ckan-enterprise/index.md

@@ -1,108 +0,0 @@
-# CKAN Enterprise
-
-## Introduction
-
-CKAN Enterprise is our name for what we plan would become our standard "base" distribution for CKAN going forward:
-
-* It is a CKAN standard code base with micro-services.
-* Enterprise grade data catalog and portal targeted at Gov (open data portals) and Enterprise (Data Catalogs +).
-* It is also known as [Datopian DMS](https://www.datopian.com/datopian-dms/).
-
-## Roadmap 2021 and beyond
-
-|                   | Current                                                                                    | CKAN Enterprise                                                 |
-|-------------------|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------|
-| Raw storage       | Filestore                                                                                  | Giftless                                                        |
-| Data Loader (db)  | DataPusher extension                                                                       | Aircan                                                          |
-| Data Storage (db) | Postgres                                                                                   | Any database engine. By default, Postgres                       |
-| Data API (read)   | Built-in DataStore extension's API including SQL endpoint                                  | GraphQL based standalone micro-service                          |
-| Frontend (public) | Build-in frontend into CKAN Classic python app (some projects are using nodejs app)        | PortalJS or nodejs app                                          |
-| Data Explorer     | ReclineJS (some projects that uses nodejs app for frontend have React based Data Explorer) | GraphQL based Data Explorer                                     |
-| Auth              | Traditional login/password + extendable with CKAN Classic extensions                       | SSO with default Google, Github, Facebook and Microsoft options |
-| Permissions       | CKAN Classic based permissions                                                             | Existing permissions exposed via JWT based authz API            |
-
-## Timeline 2021
-
-To develop a base distribution of CKAN Enterprise, we want to build a demo project with the features from the roadmap. This way we can:
-
-* understand its advantages/limitations;
-* compare against other instances of CKAN;
-* demonstrate for the potential clients.
-
-High level overview of the planned features with ETA:
-
-| Name                          | Description                          | Effort | ETA |
-| ----------------------------- | ------------------------------------ | ------ | --- |
-| [Init](#Init)                 | Select CKAN version and deploy to DX | xs     | Q2  |
-| [Blobstore](#Blobstore)       | Integrate Giftless for raw storage   | s      | Q2  |
-| [Versioning](#Versioning)     | Develop/integrate new versioning sys | l      | Q3  |
-| [DataLoader](#DataLoader)     | Develop/integrate Aircan             | xl     | Q3  |
-| [Data API](#Data-API)         | Integrate new Data API (read)        | m      | Q2  |
-| [Frontend](#Frontend)         | Build a theme using PortalJS         | s      | Q2  |
-| [DataExplorer](#DataExplorer) | Integrate into PortalJS              | s      | Q2  |
-| [Permissions](#Permissions)   | Develop permissions in read frontend | m      | Q4  |
-| [Auth](#Auth)                 | Integrate                            | s      | Q4  |
-
-### Init
-
-Initialize a new project for development of CKAN Enterprise.
-
-Tasks:
-
-* Boot project in Datopian-DX cluster
-* Use CKAN v2.8.x (latest patch) or 2.9.x
-* Don't setup DataPusher
-* Namespace: `ckan-enterprise`
-* Domain: `enterprise.ckan.datopian.com`
-
-### Blobstore
-
-See [blob storage](/docs/dms/blob-storage#ckan-v3)
-
-### Versioning
-
-See [versioning](/docs/dms/versioning#ckan-v3)
-
-### DataLoader
-
-See [DataLoader](/docs/dms/load)
-
-### Data API
-
-* Install new [Data API service](https://github.com/datopian/data-api) in the project
-* Install Hasura service in the project
-* Set it up to work with DB of CKAN Enterprise
-* Read more about Data API [here](/docs/dms/data-api#read-api-3)
-
-Notes:
-
-* We could experiment and use various features of Hasura, eg:
-  * Setting up row/column limits per user role (permissions)
-  * Subscriptions to auto load new data rows
-
-### Frontend
-
-PortalJS for the read frontend of CKAN Enterprise. [Read more](/docs/dms/frontend/#frontend).
-
-### DataExplorer
-
-A new Data Explorer based on GraphQL API: https://github.com/datopian/data-explorer-graphql
-
-### Permissions
-
-See [permissions](/docs/dms/permissions#permissions-authorization).
-
-### Auth
-
-Next generation, Kratos based, authentication (mostly SSO with no Traditional login by default) with following options out of the box:
-
-* GitHub
-* Google
-* Facebook
-* Microsoft
-
-Easy to add:
-
-* Discord
-* GitLab
-* Slack

site/content/docs/dms/ckan-v3/index.md

@@ -1,365 +0,0 @@
-# CKAN v3
-
-## Introduction
-
-This document describes the architectures of CKAN v2 ("CKAN Classic"), CKAN v3 (also known as "CKAN Next Gen" for Next Generation), and CKAN v3 hybrid. The latter is an intermediate approach towards v3, where we still use CKAN v2 and common extensions, and only create microservices for new features.
-
-You will also find out how to do common tasks such as theming or testing, in each of the architectures.
-
-*Note: this blog post has an overview of the more decoupled, microservices approach at the core of v3: https://www.datopian.com/2021/05/17/a-more-decoupled-ckan/*
-
-## CKAN v2, CKAN v3 and Why v3
-
-In yellow, you see one single Python process:
-
-```mermaid
-graph TB
-  subgraph ckanclassic["CKAN Classic"]
-    ckancore["Core"]
-  end
-```
-
-When you want to extend core functionality of CKAN v2 (Classic), you write a Python package that must be installed in CKAN. This way, the extension will also run in the same process as the core functionality. This is known as a monolithic architecture.
-
-```mermaid
-graph TB
-  subgraph ckanclassic["CKAN Classic"]
-    ckancore["Core"] --> ckanext["CKAN Extension 1"]
-  end
-```
-
-When you start to add multiple features, through extensions, what you get is one single Python process running many non-related functionalities.
-
-```mermaid
-graph TB
-  subgraph ckanclassic["CKAN Classic"]
-    ckancore["Core"] --> ckanext["CKAN Extension 1"]
-    ckancore --> ckanext2["CKAN Extension 2"]
-    ckancore --> ckanext3["CKAN Extension 3"]
-    ckancore --> ckanext4["CKAN Extension 4"]
-    ckancore --> ckanext5["CKAN Extension 5"]
-  end
-```
-
-This monolithic approach has advantages in terms of simplicity of development and deployment, especially when the system is small. However, as it grows in scale and scope, there are an increasing number of issues.
-
-In this approach, an optional extension has the ability to crash the whole CKAN instance. Every new feature must be written in the same language and framework (e.g. Python, leveraging Flask or Django). And, perhaps most fundamentally, the overall system is highly coupled, making it complex and hard to understand, debug, extend, and evolve.
-
-### Microservices and CKAN v3
-
-The main way to address these problems while gaining extra benefits is to move to a microservices-based architecture.
-
-Thus, we recommend building the next version of CKAN – CKAN v3 – on a microservices approach.
-
-[!tip]CKAN v3 is sometimes also referred to as CKAN Next Gen(eration).
-
-With microservices, each piece of functionality runs in its own service and process. 
-
-```mermaid
-graph TB
-  subgraph ckanapi3["CKAN API 3"]
-    ckanapi31["API 3"]
-  end
-
-  subgraph ckanapi2["CKAN API 2"]
-    ckanapi21["API 2"]
-  end
-  
-  subgraph ckanapi1["CKAN API 1"]
-    ckanapi11["API 1"]
-  end
-
-  subgraph ckanfrontend["CKAN frontend"]
-    ckanfrontend1["Frontend"]
-  end
-  
-  ckanfrontend1 --> ckanapi11
-  ckanfrontend1 --> ckanapi21
-  ckanfrontend1 --> ckanapi31
-```
-
-### Incremental Evolution – Hybrid v3
-
-One of the other advantages of the microservices approach is that it can also be used to extend and evolve current CKAN v2 solutions in an incremental way. We term these kinds of solutions "Hybrid v3," as they are a mix of v2 and v3 together. 
-
-For example, a Hybrid v3 data portal could use a new microservice written in Node for the frontend, and combine that with CKAN v2 (with v2 extensions).
-
-```mermaid
-graph TB
-  subgraph ckanapi3["CKAN API 3"]
-    ckanapi31["API 3"]
-  end
-
-  subgraph ckanapi2["CKAN API 2"]
-    ckanapi21["API 2"]
-  end
-  
-  subgraph ckanapi1["CKAN API 1"]
-    ckanapi11["API 1"]
-  end
-
-  subgraph ckanfrontend["CKAN frontend"]
-    ckanfrontend1["Frontend"]
-  end
-  
-  subgraph ckanclassic["CKAN Classic"]
-    ckancore["Core"] --> ckanext["CKAN Extension 1"]
-    ckancore --> ckanext2["CKAN Extension 2"]
-  end
-  
-  ckanfrontend1 --> ckancore
-  ckanfrontend1 --> ckanapi11
-  ckanfrontend1 --> ckanapi21
-  ckanfrontend1 --> ckanapi31
-```
-
-The hybrid approach means we can evolve CKAN v2 "Classic" to CKAN v3 "Next Gen" incrementally. In particular, it allows people to keep using their existing v2 extensions, and upgrade them to new microservices gradually.
-
-### Comparison of Approaches
-
-|              | CKAN v2 (Classic) | CKAN v3 (Next Gen) | CKAN v3 Hybrid |
-| ------------ | ------------------| -------------------| ---------------|
-| Architecture | Monolithic        | Microservice       | Microservice with v2 core |
-| Language     | Python            | You can write services in any language you like.<br/><br/>Frontend default: JS.<br/>Backend default: Python | Python and any language you like for microservices. |
-| Frontend (and theming) | Python with Python CKAN extension | Flexible. Default is modern JS/NodeJS based | Can use old frontend but default to new JS-based frontend. |
-| Data Packages | Add-on, no integration | Default internal and external format | Data Packages with converter to old CKAN format. |
-| Extension | Extensions are libraries that are added to core runtime. They must therefore be built in python and are loaded into the core process at build time. "Template/inheritance" model where hooks are in core and it is core that loads and calls plugins. This means that if a hook does not exist in core then the extension is stymied. | Extensions are microservices and can be written in any language. They are loaded into the url space via kubernetes routing manager. Extensions hook into "core" via APIs (rather than in code). Follows a "composition" model rather than inheritance model | Can use old style extensions or microservices. |
-| Resource Scaling | You have a single application so scaling is of the core application. | You can scale individual microservices as needed. | Mix of v2 and v3 |
-
-## Why v3: Long Version
-
-What are the problems with CKAN v2's monolithic architecture in relation to microservices v3?
-
-* **Poor Developer Experience (DX), innovability, and scalability due to coupling**. Monolithic means "one big system" => Coupling & Complexity => hard to understand, change and extend. Changes in one area can unexpectedly affect other areas. 
-  * DX to develop a small new API requires wiring into CKAN core via an extension. Extensions can interact in unexpected ways.
-  * The core of people who fully understand CKAN has stayed small for a reason: there's a lot of understand.
-  * https://github.com/ckan/ckan/issues/5333 is an example of a small bug that's hard to track down due to various paths involved.
-  * Harder to make incremental changes due to coupling (e.g. Python 3 upgrade requires *everything* to be fixed at once - can't do rolling releases).
-* **Stability**. One bad extension crashes or slows down the whole system
-* **One language => Less developer flexibility (Poor DX)**. Have to write *everything* in Python, including the frontend. This is an issue especially for the frontend: almost all modern frontend development is heavily Javascript-based and theme is the #1 thing people want to customize in CKAN. At the moment, that requires installing *all* of CKAN core (using Docker) plus some familiarity with Python and Jinja templating. This is a big ask.
-* **Extension stablity and testing**. Testing of extensions is painful (at least without careful factoring in a separate mini library) and are therefore often not tested; they don't have Continuous Integration (CI) or Continuous Deployment (CD). As an example, a highly experienced Python developer at Datopian was still struggling to get extension tests working 6 months into their CKAN work.
-* **DX is poor especially when getting started**. Getting CKAN up and running requires multiple external services (database, Solr, Redis, etc.) making Docker the only viable way for bootstraping a local development environment. This makes getting started with CKAN daunting and painful.
-* **Vertical scalability is poor**. Scaling the system is costly as you have to replicate the whole core process in every machine.
-* **System is highly coupled.** Extensions b/c in process tend to end up with significant coupling to core which makes them brittle (has improved with plugins.toolkit)
-  * Upgrading core to Python 3 requires upgrading *all* extensions because they run in the same process.
-  * Search Index is not a separate API, but in Core. So replacing Solr is hard.
-
-The top 2 customizations of CKAN are slow and painful and require deep knowledge of CKAN:
-
-* Theming a site.
-* Customizing the metadata.
-
-## Architectures
-
-### CKAN v2 (Classic)
-
-This diagram is based on the file `docker-compose.yml` of [github.com/okfn/docker-ckan](https://github.com/okfn/docker-ckan) (`docker-compose.dev.yml` has the same components, but different configuration).
- 
-A difference from this diagram to the file is that we are not including DataPusher, as it is not a required dependency.
-
->[!tip]Databases may run as Docker containers, or rely on third-party services such as Amazon Relational Database Service (RDS).
-
-
-
-```mermaid
-graph LR
-
-CKAN[CKAN web app]
-
-CKAN --> DB[(Database)]
-CKAN --> Solr[(Solr)]
-CKAN --> Redis[(Redis)]
-
-subgraph Docker container
-  CKAN
-end
-```
-
-Same setup showing some of the key extensions explicitly:
-
-```mermaid
-graph LR
-  core[CKAN Core] --> DB[(Database)]
-  datastore --> DB2[(Database - DataStore)]
-  core --> Solr[(Solr)]
-  core --> Redis[(Redis)]
-  
-  subgraph Docker container
-    core
-    datastore
-    datapusher
-    imageview
-    ...
-  end
-```
-
-CKAN ships with several core extensions that are built-in. Here, together with the list of main components, we list a couple of them:
-
-Name | Type | Repository | Description
------|------|------------|------------
-CKAN | Application (API + Worker) | [Link](https://github.com/ckan/ckan) | Data management system (DMS) for powering data hubs and data portals. It's a monolithical web application that includes several built-in extensions and dependencies, such as a job queue service. In theory, it's possible to run it without any extensions.
-datapusher | CKAN Extension | [Link](https://github.com/ckan/ckan/tree/master/ckanext/datapusher) | It could also be called "datapusher-connect." It's a glue code to connect with a separate microservice called DataPusher, which performs actions when new data arrives.
-datastore | CKAN Extension | [Link](https://github.com/ckan/ckan/tree/master/ckanext/datastore) | The interface between CKAN and the structure database, the one receiving datasets and resources (CSVs). It includes an API for the database and an administrative UI.
-imageview | CKAN Extension | [Link](https://github.com/ckan/ckan/tree/master/ckanext/imageview) | It provides an interface for creating HTML templates for image resources.
-multilingual | CKAN Extension | [Link](https://github.com/ckan/ckan/tree/master/ckanext/multilingual) | It provides an interface for translation and localization.
-Database | Database | | People tend to use a single PostgreSQL instance for this. Separated in multiple databases, it's the place where CKAN stores its own information (sometimes referred as "MetaStore" and "HubStore"), rows of resources (StructuredStore or DataStore), and raw datasets and resources ("BlobStore" or "FileStore"). The latter may store data in the local filesystem or cloud providers, via extensions.
-Solr | Database | | It provides indexing and full-text search for CKAN.
-Redis | Database | | Lightweight key-value store, used for caching and job queues.
-
-### CKAN v3 (Next Gen)
-
-CKAN Next Gen is still a DMS, as CKAN Classic; but rather than a monolithical architecture, it follows the microservices approach. CKAN Classic is not a dependency anymore, as we have smaller services providing functionality that we may or many not choose to include. This description is based on [Datopian's Technical Documentation](/docs/dms/ckan-v3/next-gen/#roadmap).
-
-```mermaid
-graph LR
-  subgraph api3["..."]
-    api31["API"]
-  end
-
-  subgraph api2["Administration"]
-    api21["API"]
-  end
-  
-  subgraph api1["Authentication"]
-    api11["API"]
-  end
-
-  subgraph frontend["Frontend"]
-    frontendapi["API"]
-  end
-  
-  subgraph storage["Raw Resources Storage"]
-    storageapi["API"]
-  end
-  
-  storageapi --> cloudstorage[(Cloud Storage)]
-  
-  frontendapi --> storageapi
-  frontendapi --> api11
-  frontendapi --> api21
-  frontendapi --> api31
-```
-
-At this moment, many important features are only available through CKAN extensions, so that brings us to the hybrid approach.
-
-### CKAN Hybrid v3 (Next Gen)
-
-We may sometimes make an explit distinction between CKAN v3 "hybrid" and "pure." The reason is because we want to ensure that we're not there yet – we have many opportunities to extract features out of CKAN and CKAN Extensions.
-
-In this approach, we still rely on CKAN Classic and all its extensions. Many already had many tests and bugs fixed, so we can deliver more if not forced to rewrite everything from scratch.
-
-```mermaid
-graph TB
-  subgraph ckanapi3["CKAN API 3"]
-    ckanapi31["API 3"]
-  end
-
-  subgraph ckanapi2["CKAN API 2"]
-    ckanapi21["API 2"]
-  end
-  
-  subgraph ckanapi1["CKAN API 1"]
-    ckanapi11["API 1"]
-  end
-
-  subgraph ckanfrontend["Frontend"]
-    ckanfrontend1["Frontend v2"]
-    theme["[Project-specific theme]"]
-  end
-  
-  subgraph ckanclassic["CKAN Classic"]
-    ckancore["Core"] --> ckanext["CKAN Extension 1"]
-    ckancore --> ckanext2["[Project-specific extension]"]
-  end
-  
-  ckanfrontend1 --> ckancore
-  ckanfrontend1 --> ckanapi11
-  ckanfrontend1 --> ckanapi21
-  ckanfrontend1 --> ckanapi31
-```
-
-Name | Type | Repository | Description
------|------|------------|------------
-Frontend v2 | Application | [Link](https://github.com/datopian/frontend-v2) | Node application for Data Portals. It communicates with a CKAN Classic instance, through its API, to get data and render HTML. It is written to be extensible, such as connecting to other applications and theming.
-[Project-specific theme] | Frontend Theme | e.g., [Link](https://github.com/datopian/frontend-oddk) | Extension to Frontend v2 where you can personalize the interface, create different pages, and connect with other APIs.
-[API 1] | Application | e.g., [Link](https://github.com/datopian/data-subscriptions) | Any application with an API to communicate with the user-facing Frontend v2 or to run tasks in background. Given the current architecture, often, this API is usually designed to work with CKAN interfaces. Over time, we may choose to make it more generic, and even replace CKAN Core with other applications.
-
-## Job Stories
-
-In this spreadsheet, you will find a list of common job stories in CKAN projects. Also, how you can accomplish them in CKAN v2, v3, and Hybrid v3.
-
-https://docs.google.com/spreadsheets/d/1cLK8xylprmVsoQIbdphqz9-ccSpdDABQExvKdvNJqaQ/edit#gid=757361856
-
-## Glossary
-
-### API
-
-An HTTP API, usually following the REST style.
-
-### Application
-
-A Python package, an API, a worker... It may have other applications as dependencies.
-  
-### CKAN Extension
-
-A Python package following specification from [CKAN Extending guide](https://docs.ckan.org/en/2.8/extensions/index.html).
-  
-### Database
-
-An organized collection of data.
-
-### Dataset
-
-A group of resources made to be distributed together.
-  
-### Frontend Theme
-
-A Node project specializing behavior present in [Frontend v2](https://github.com/datopian/frontend-v2).
-  
-### Resource
-
-A data blob. Common formats are CSV, JSON, and PDF.
-  
-### System
-
-A group of applications and databases that work together to accomplish a set of tasks.
-  
-### Worker
-
-An application that runs tasks in background. They may run recurrently according to a given schedule, or as soon as it's requested by another application.
-
-## Appendix
-
-### Architecture - CKAN v2 with DataPusher
-
-```mermaid
-graph TB
-  subgraph DataPusher
-    datapusherapi["DataPusher API"]
-    datapusherworker["CKAN Service Provider"]
-    SQLite[(SQLite)]
-  end
-  
-  subgraph CKAN
-    core
-    datapusher[datapusher ext]
-    datastore
-    ...
-  end
-  
-  core[CKAN Core] --> datastore
-  datastore --> DB[(Database)]
-  datapusherapi --> core
-  datapusher --> datapusherapi
-```
-
-Name | Type | Repository | Description
------|------|------------|------------
-DataPusher | System | [Link](https://github.com/ckan/datapusher) | Microservice that parses data files and uploads them to the datastore.
-DataPusher API | API | [Link](https://github.com/ckan/datapusher) | HTTP API written in Flask. It is called from the built-in `datapusher` CKAN extension whenever a resource is created (and has the right type).
-CKAN Service Provider | Worker | [Link](https://github.com/ckan/ckan-service-provider) | Library for making web services that make functions available as synchronous or asynchronous jobs.
-SQLite | Database | | Unknown use. Possibly a worker dependency.
-
-### Old Next Gen Page
-
-Prior to this page, we had one called "Next Gen." It has intersections with this article, although it focuses more on the benefits of microservices. For the time being, the page still exists in [/ckan-v3/next-gen](/docs/dms/ckan-v3/next-gen), although it may get merged with this one in the future.

site/content/docs/dms/ckan-v3/next-gen.md

@@ -1,203 +0,0 @@
-# Next Gen
-
-“Next Gen” (NG) is our name for the evolution of CKAN from its current state as “CKAN Classic”.
-
-Next Gen has a decoupled, microservice architecture in contrast to CKAN Classic's monolithic architecture. It is also built from the ground up on the Frictionless Data principles and specifications which provide a simple, well-defined and widely adopted set of core interfaces and tooling for managing data.
-
-## Classic to Next Gen
-
-CKAN classic: monolithic architecture -- everything is one big python application. Extension is done at code level and "compiled in" at compile/run-time (i.e. you end up with one big docker file).
-
-CKAN Next Gen: decoupled, service-oriented -- services connected by network calls. Extension is done by adding new services,
-
-```mermaid
-graph LR
-
-subgraph "CKAN Classic"
-  plugins
-end
-
-subgraph "CKAN Next Gen"
-  microservices
-end
-
-plugins --> microservices
-```
-
-You can read more about monolithic vs microservice architectures in the [Appendix below](#appendix-monolithic-vs-microservice-architecture).
-
-
-## Next Gen lays the foundation for the future and brings major immediate benefits
-
-Next Gen's new approach is important in several major ways.
-
-### Microservices are the Future
-
-First, decoupled microservices have become *the* way to design and deploy (web) applications after first being pioneered by the likes of Amazon in the early 2000s. And in the last five to ten years have brought microservices "for the masses" with relevant tooling and technology standardized, open-sourced and widely deployed -- not only with containerization such as Docker, Kubernetes but also in programming languages like (server-side) Javascript and Golang.
-
-By adopting a microservice approach CKAN can reap the the benefits of what is becoming a mature and standard way to design and build (web) applications. This includes the immediate advantages of being aligned with the technical paradigm such as tooling and developer familiarity.
-
-### Microservices bring Scalability, Reliability, Extensibility and Flexibility
-
-In addition, and even more importantly, the microservices approach brings major benefits in:
-
-1. **Scalability**: dramatically easier and cheaper to scale up -- and down -- in size *and* complexity. Size-wise this is because you can replicate individual services rather than the whole application. Complexity-wise this is because monolithic architectures tend to become "big" where service-oriented encourages smaller lightweight components with cleaner interfaces. This means you can have a much smaller core making it easier to install, setup and extend. It also means you can use what you need making solutions easier to maintain and upgrade.
-2. **Reliability**: easier (and cheaper) to build highly reliable, high availability solutions because microservices make isolation and replication easier. For example, in a microservice architecture a problem in CKAN's harvester won't impact your main portal because they run in separate containers. Similarly, you can scale the harvester system separately from the web frontend.
-3. **Extensibility**: much easier to create and maintain extensions because they are a decoupled service and interfaces are leaner and cleaner.
-4. **Flexibility** aka "Bring your own tech": services can be written in any language so, for example, you can write your frontend in javascript and your backend in Python. In a monolithic architecture all parts must be written in the same language because everything is compiled together. This flexibility makes it easier to use the best tool for the job. It also makes it much easier for teams to collaborate and cooperate and fewer bottlenecks in development.
-
-ASIDE: decoupled microservices reflect the "unix" way of building networked applications. As with the "unix way" in general, whilst this approach better -- and simpler -- in the long-run, in the short-run it often needs sustantial foundational work (those Unix authors were legends!). It may also be, at least initially, more resource intensive and more complex infrastructurally. Thus, whilst this approach is "better" it was not suprising that it was initially used for for complex and/or high end applications e.g. Amazon. This also explains why it took a while for this approach to get adoption -- it is only in the last few year that we have robust, lightweight, easy to use tooling and patterns for microservices -- "microservices for the masses" if you like.
-
-In summary, the Next Gen approach provides an essential foundation for the continuing growth and evolution of CKAN as a platform for building world-class data portal and data management solutions.
-
-## Evolution not Revolution: Next Gen Components Work with CKAN Classic
-
-*Gradual evolution from CKAN classic (keep what is working, keep your investments, incremental change)*
-
-Next Gen components are specifically designed to work with CKAN "Classic" in its current form. This means existing CKAN users can immediately benefit from Next Gen components and features whilst retaining the value of their existing investment. New (or existing) CKAN-based solutions can adopt a "hybrid" approach using components from both Classic and Next Gen. It also means that the owner of a CKAN-based solution can incrementally evolve from "Classic" to "Next Gen" by replacing one component one at a time, gaining new functionality without sacrificing existing work.
-
-ASIDE: we're fortunate that CKAN Classic itself was ahead of its time in its level of "service-orientation". From the start, it had a very rich and robust API and it has continued to develop this with almost almost all functionality exposed via the API. It is this rich API and well factored design that makes it relatively straightforward to evolve CKAN in its current "Classic" form towards Next Gen.
-
-## New Features plus Existing Functionality Improved
-
-In addition to its architecture, Next Gen provides a variety of improvements and extensions to CKAN Classic's functionality. For example:
-
-* Theming and Frontend Customization: theming and customizing CKAN's frontend has got radically easier and quicker. See [Frontend section »][frontend]
-* DMS + CMS unified: integrate the full power of a modern CMS into your data portal and have one unified interface for data and content. See [Frontend section »][frontend]
-* Data Explorer: the existing CKAN data preview/explorer has been completely rewritten in modern React-based Javascript (ReclineJS is now 7y old!). See [Data Explorer section »][explorer]
-* Dashboards: build rich data-driven dashboards and integrate. See [Dashboards section »][dashboards]
-* Harvesting: simpler, more powerful harvesting built on modern ETL. See [Harvesting section »][harvesting]
-
-And each of these features is easily deployed into an existing CKAN solution!
-
-[frontend]: /docs/dms/frontend
-[explorer]: /docs/dms/data-explorer
-[dashboards]: /docs/dms/dashboards
-[harvesting]: /docs/dms/harvesting
-
-## Roadmap
-
-The journey to Next Gen from Classic can proceed step by step -- it does not need to be a big bang. Like refurbishing and extending a house, we can add a room here or renovate a room there whilst continuing to live happily in the building (and benefitting as our new bathroom comes online, or we get a new conservatory!).
-
-Here's an overview of the journey to Next Gen and current implementation status. More granular information on particular features may sometimes be found on the individual feature page, for example for [Harvesting here](/docs/dms/harvesting#design).
-
-```mermaid
-graph LR
-
-start[Start]
-themefe[Read Frontend]
-authfe[Authentication in FE]
-authzfe[Authorization in FE]
-previews[Previews]
-explorer[Explorer]
-permsserv[Permissions Service]
-orgs[Organizations]
-
-
-subgraph Start
-  start
-end
-
-subgraph Frontend
-  start --> themefe
-  themefe --> authfe
-  authfe --> authzfe
-  themefe --> revisioningfe[Revision UI]
-end
-
-subgraph Harvesting
-  start --> harvestetl[Harvesting ETL + Runner]
-  harvestetl --> harvestui[Harvest UI]
-end
-
-subgraph "Admin UI"
-  managedataset[Manage Dataset]
-  manageorg[Manage Organization]
-  manageuser[Manage Users]
-  manageconfig[Manage Config]
-  
-  start --> managedataset
-  start --> manageorg
-  managedataset --> manageconfig
-end
-
-subgraph "Backend (API)"
-  start --> permsserv
-  start --> revision[Backend Revisioning]
-end
-
-datastore[DataStore]
-
-subgraph DataStore
-  start --> datastore
-  datastore --> dataload[Data Load]
-end
-
-subgraph Explorer
-  themefe --> previews
-  previews --> explorer
-end
-
-subgraph Organizations
-  start --> orgs
-end
-
-subgraph Key
-  done[Done]
-  nearlydone[Nearly Done]
-  inprogress[In Progress]
-  next[Next Up]
-end
-
-classDef done fill:#21bf73,stroke:#333,stroke-width:3px;
-classDef nearlydone fill:lightgreen,stroke:#333,stroke-width:3px;
-classDef inprogress fill:orange,stroke:#333,stroke-width:2px;
-classDef next fill:pink,stroke:#333,stroke-width:1px;
-
-class done,themefe,previews,explorer,harvestetl done;
-class nearlydone,authfe,harvestui nearlydone;
-class inprogress,dataload inprogress;
-class next,permsserv next;
-```
-
-## Appendix: Monolithic vs Microservice architecture
-
-Monolithic: Libraries or modules communicate via function calls (inside one big application)
-
-Microservices: Services communicate over a network
-
-The best introduction and definition of microservices comes from Martin Fowler https://martinfowler.com/microservices/
-
-> Microservice architectures will use libraries, but their primary way of componentizing their own software is by breaking down into services. We define libraries as components that are linked into a program and called using in-memory function calls, while services are out-of-process components who communicate with a mechanism such as a web service request, or remote procedure call. https://martinfowler.com/articles/microservices.html
-
-### Monolithic
-
-```mermaid
-graph TD
-
-subgraph "Monolithic - all inside"
-  a
-  b
-  c
-end
-
-a --in-memory function all--> b
-a --in-memory function all--> c
-```
-
-### Microservice
-
-```mermaid
-graph TD
-subgraph "A Container"
-  a
-end
-subgraph "B Container"
-  b
-end
-subgraph "C Container"
-  c
-end
-a -.network call.-> b
-a -.network call.-> c
-```

site/content/docs/dms/ckan.md

@@ -1,23 +0,0 @@
----
-sidebar: auto
----
-
-# CKAN Classic
-
-CKAN (Classic) already has great documentation at: https://docs.ckan.org/
-
-This material is a complement to those docs as well as details of our particular setup.  Here, among other things, you'll learn how to: 
-
-* [Get Started with CKAN for Development -- install and run CKAN on your local machine](/docs/dms/ckan/getting-started)
-* [Play around with a CKAN instance including importing and visualising data](/docs/dms/ckan/play-around)
-* [Install Extensions](/docs/dms/ckan/install-extension)
-* [Create Your Own Extension](/docs/dms/ckan/create-extension)
-* [Client Guide](/docs/dms/ckan-client-guide)
-* [FAQ](/docs/dms/ckan/faq)
-
-[start]: /docs/dms/ckan/getting-started
-[play]: /docs/dms/ckan/play-around
-
-[CKAN]: https://ckan.org/
-[docs]: https://docs.ckan.org/
-

site/content/docs/dms/ckan/create-extension.md

@@ -1,162 +0,0 @@
----
-sidebar: auto
----
-
-# Introduction
-A CKAN extension is a Python package that modifies or extends CKAN. Each extension contains one or more plugins that must be added to your CKAN config file to activate the extension’s features.
-
-## Creating and Installing extensions
-1. Boot up your docker compose
-```
-docker-compose -f docker-compose.dev.yml up
-```
-
-
-2. To create an extension template using this docker composition execute:
-
-```
-docker-compose -f docker-compose.dev.yml exec ckan-dev /bin/bash -c "paster --plugin=ckan create -t ckanext ckanext-example_extension -o /srv/app/src_extensions"
-```
-
-This command will create an extension template in your local `./src` folder that is mounted inside the containers in the `/srv/app/src_extension` directory. Any extension cloned on the `src` folder will be installed in the CKAN container when booting up Docker Compose (`docker-compose up`). This includes installing any requirements listed in a `requirements.txt` (or `pip-requirements.txt`) file and running `python setup.py develop`.
-
-
-3. Add the plugin to the `CKAN__PLUGINS` setting in your `.env` file.
-
-```
-CKAN__PLUGINS=stats text_view recline_view example_extension
-```
-
-
-4. Restart your docker-compose:
-
-```
-# Shut down your instance with crtl+c and then run it again with:
-docker-compose -f docker-compose.dev.yml up
-```
-> [!tip]CKAN will be started running on the paster development server with the '--reload' option to watch changes in the extension files.
-
-You should see the following output in the console:
-
-```
-...
-ckan-dev_1    | Installed /srv/app/src_extensions/ckanext-example_extension
-...
-```
-
-## Edit the extension
-
-Let's edit a template to change the way CKAN is displayed to the user!
-
-1. First you will need write permissions to the extension folder since it was created by the user running docker. Replace `your_username` and execute the following command:
-
-> [!tip]You can find out your current username by typing 'echo $USER' in the terminal.
-
-```
-sudo chown -R <your_username>:<your_username> src/ckanext-example_extension
-```
-
-2. The previous comamand creates all the files and folder structure needed for our extension. Open `src/ckanext-example_extension/ckanext/example_extension/plugin.py` to see the main file of our extension that we will edit to add custom functionality:
-
-```python
-import ckan.plugins as plugins
-import ckan.plugins.toolkit as toolkit
-
-
-class Example_ExtensionPlugin(plugins.SingletonPlugin):
-    plugins.implements(plugins.IConfigurer)
-
-    # IConfigurer
-
-    def update_config(self, config_):
-        toolkit.add_template_directory(config_, 'templates')
-        toolkit.add_public_directory(config_, 'public')
-        toolkit.add_resource('fanstatic', 'example_theme')
-```
-
-3. We will create a custom Flask Blueprint to extend our CKAN instance with more endpoints. In order to create a new blueprint and add an endpoint we need to:
- - Import Blueprint and render_template from the flask module.
- - Create the functions that will be used as endpoints
- - Implement the IBlueprint interface in our plugin and add the new endpoint.
-
-4. From flask import Blueprint and render_template,
-
-```python
-import ckan.plugins as plugins
-import ckan.plugins.toolkit as toolkit
-
-from flask import Blueprint, render_template
-
-class Example_ExtensionPlugin(plugins.SingletonPlugin):
-    plugins.implements(plugins.IConfigurer)
-
-    # IConfigurer
-
-    def update_config(self, config_):
-        toolkit.add_template_directory(config_, 'templates')
-        toolkit.add_public_directory(config_, 'public')
-        toolkit.add_resource('fanstatic', 'example_extension')
-```
-
-5. Create a new function: hello_plugin
-```python
-import ckan.plugins as plugins
-import ckan.plugins.toolkit as toolkit
-
-from flask import Blueprint, render_template
-
-def hello_plugin():
-    u'''A simple view function'''
-    return u'Hello World, this is served from an extension'
-
-class Example_ExtensionPlugin(plugins.SingletonPlugin):
-    plugins.implements(plugins.IConfigurer)
-
-    # IConfigurer
-
-    def update_config(self, config_):
-        toolkit.add_template_directory(config_, 'templates')
-        toolkit.add_public_directory(config_, 'public')
-        toolkit.add_resource('fanstatic', 'example_extension')
-```
-6. Implement the IBlueprint interface in our plugin and add the new endpoint.
-
-```python
-import ckan.plugins as plugins
-import ckan.plugins.toolkit as toolkit
-
-from flask import Blueprint, render_template
-
-def hello_plugin():
-    u'''A simple view function'''
-    return u'Hello World, this is served from an extension'
-
-class Example_ExtensionPlugin(plugins.SingletonPlugin):
-    plugins.implements(plugins.IConfigurer)
-    plugins.implements(plugins.IBlueprint)
-
-    # IConfigurer
-
-    def update_config(self, config_):
-        toolkit.add_template_directory(config_, 'templates')
-        toolkit.add_public_directory(config_, 'public')
-        toolkit.add_resource('fanstatic', 'example_extension')
-
-    # IBlueprint
-
-    def get_blueprint(self):
-        u'''Return a Flask Blueprint object to be registered by the app.'''
-        # Create Blueprint for plugin
-        blueprint = Blueprint(self.name, self.__module__)
-        blueprint.template_folder = u'templates'
-        # Add plugin url rules to Blueprint object
-        blueprint.add_url_rule('/hello_plugin', '/hello_plugin', hello_plugin)
-        return blueprint
-
-```
-
-6. Go back to the browser and navigate to http://ckan:5000/hello_plugin. You should see the value returned by our view!
-
-![New Blueprint output](https://i.imgur.com/AZjTDbN.png)
-
-Now that you have added a new view and endpoint to your plugin you are ready for the next step of the tutorial! You can also check the complete code of this plugin in the [ckan repository](https://github.com/ckan/ckan/tree/master/ckanext/example_flask_iblueprint).

site/content/docs/dms/ckan/faq.md

@@ -1,110 +0,0 @@
----
-sidebar: auto
----
-
-# FAQ
-
-This page provides answers to some frequently asked questions.
-
-## How to create an extension template in my local machine
-
-You can use the `paster` command in the same way as a source install. To create an extension execute the following command:
-
-```
-docker-compose -f docker-compose.dev.yml exec ckan-dev /bin/bash -c "paster --plugin=ckan create -t ckanext ckanext-myext -o /srv/app/src_extensions"
-```
-
-This will create an extension template inside the container's folder `/srv/app/src_extensions` which is mapped to your local `src/` folder.
-
-Now you can navigate to your local folder `src/` and see the extension created by the previous command and open the project in your favorite IDE.
-
-
-## How to separate that extension in a new git repository so I can have the independence to install it in other instances
-
-Crucial thing is to understand that extensions get their repositories on GitHub (or elsewhere). You can first create a repository for extension and later clone in `src/` or do opposite as following:
-
-* Create the Extension, for example: `ckanext-myext`.
-```
-docker-compose -f docker-compose.dev.yml exec ckan-dev /bin/bash -c "paster --plugin=ckan create -t ckanext ckanext-myext -o /srv/app/src_extensions"
-```
-
-* Init your new git repository into the extension folder `src/ckanext-myext`
-```
-cd src/ckanext-myext
-git init
-```
-* Configure remote/origin
-```
-git remote add origin <remote_repository_url>
-```
-* Add your files and push the first commit
-```
-git add .
-git commit -m 'Initial Commit'
-git push
-```
-
-**Note:** The `src/` folder is gitignored in `okfn/docker-ckan` repository, so initializing new git repositories inside is ok.
-
-## How to quickly refresh the changes in my extension into the dockerized environment so I can have quick feedback of my changes
-
-This docker-compose setup for dev environment is already configured so that it sets `debug=True` inside configuration file and auto reloads on python and templates related changes. You do not have to reload when making changes to HTML, javascript or configuration files - you just need to refresh the page in the browser.
-
-See the CKAN images section of the [repository documentation](https://github.com/okfn/docker-ckan#ckan-images) for more detail
-
-## How to run tests for my extension in the dockerized environment so I can have a quick test-development cycle
-
-We write and store unit tests inside the `ckanext/myext/tests` directory. To run unit tests you need to be running the `ckan-dev` service of this docker-compose setup.
-
-* Once running, in another terminal window run the test command:
-```
-docker-compose -f docker-compose.dev.yml exec ckan-dev nosetests --ckan-dev --nologcapture --reset-db -s -v --with-pylons=/srv/app/src_extensions/ckanext-myext/test.ini /srv/app/src_extensions/ckanext-myext/
-```
-
-You can also pass nosetest arguments to debug
-```
---ipdb --ipdb-failure
-```
-
-**Note:** Right now all tests will be run, it is not possible to choose a specific file or test.
-
-## How to debug my methods in the dockerized environment so I can have a better understanding of whats going on with my logic
-
-To run a container and be able to add a breakpoint with `pdb`, run the `ckan-dev` container with the `--service-ports` option:
-
-```
-docker-compose -f docker-compose.dev.yml run --service-ports ckan-dev
-```
-
-This will start a new container, displaying the standard output in your terminal. If you add a breakpoint in a source file in the `src` folder (`import pdb; pdb.set_trace()`) you will be able to inspect it in this terminal next time the code is executed.
-
-## How to debug core CKAN code
-
-Currently, this docker-compose setup doesn't allow us to debug core CKAN code since it lives inside the container. However, we can do some hacks so the container uses a local clone of the CKAN core hosted in our machine. To do it:
-
-- Create a new folder called `ckan_src` in this `docker-ckan` folder at the same level of the `src/`
-- Clone ckan and checkout the version you want to debug/edit
-
-```
-git https://github.com/ckan/ckan/ ckan_src
-cd ckan_src
-git checkout ckan-2.8.3
-```
-
-- Edit `docker-compose.dev.yml` and add an entry to ckan-dev's and ckan-worker-dev's volumes. This will allow the docker container to access the CKAN code hosted in our machine.
-
-```
-   - ./ckan_src:/srv/app/ckan_src
-```
-
-- Create a script in `ckan/docker-entrypoint.d/z_install_ckan.sh` to install CKAN inside the container from the cloned repository (instead of the one installed in the Dockerfile)
-
-```
-#!/bin/bash
-echo "*********************************************"
-echo "overriding with ckan installation with ckan_src"
-pip install -e /srv/app/ckan_src
-echo "*********************************************"
-```
-
-That's it. This will install CKAN inside the container in development mode, from the shared folder. Now you can open the `ckan_src/` folder from your favorite IDE and start working on CKAN.

site/content/docs/dms/ckan/getting-started.md

@@ -1,77 +0,0 @@
-# CKAN: Getting Started for Development
-
-## Prerequisites
-
-CKAN has a rich tech stack so we have opted to standardize our instructions with Docker Compose, which will help you spin up every service in a few commands.
-
-If you already have Docker-compose, you are ready to go!
-
-If not, please, follow instructions on [how to install docker-compose](https://docs.docker.com/compose/install/).
-
-On Ubuntu you can run:
-
-```
-sudo apt-get update
-sudo apt-get install docker-compose
-```
-
-## Cloning the repo
-
-```
-git clone https://github.com/okfn/docker-ckan
-# or git clone git@github.com:okfn/docker-ckan.git
-cd docker-ckan
-```
-
-## Booting CKAN
-
-Create a local environment file:
-
-```
-cp .env.example .env
-```
-
-Build and Run the instances:
-
-> [!tip]'docker-compose' must be run with 'sudo'. If you want to change this, you can follow the steps below. NOTE: The 'docker' group grants privileges equivalent to the 'root' user.  
-
-Create the `docker` group: `sudo groupadd docker`  
-
-Add your user to the `docker` group: `sudo usermod -aG docker $USER`  
-
-Change the storage directory ownership from `root` to `ckan` by adding the commads below to the `ckan/Dockerfile.dev`
-
-```
-RUN mkdir -p /var/lib/ckan/storage/uploads
-RUN chown -R ckan:ckan /var/lib/ckan/storage
-```
-
-At this point, you can log out and log back in for these changes to apply. You can also use the command `newgrp docker` to temporarily enable the new group for the current terminal session.
-
-```
-docker-compose -f docker-compose.dev.yml up --build
-```
-
-When you see this log message:
-
-![](https://i.imgur.com/WUIiNRt.png)
-
-You can navigate to `http://localhost:5000`
-
-![CKAN Home Page](https://i.imgur.com/T5LWo8A.png)
-
-and log in with the credentials that docker-compose setup created for you [user: `ckan_admin` password:`test1234`].
-
->[!tip]To learn key concepts about CKAN, including what it is and how it works, you can read the User Guide.
-[CKAN User Guide](https://docs.ckan.org/en/2.8/user-guide.html).
-
-
-## Next Steps
-
-[Play around with CKAN portal](/docs/dms/ckan/play-around).
-
-## Troubleshooting
-
-Login / Logout button breaks the experience:
-
-- Change the URL from `http://ckan:5000` to `http://localhost:5000`. A complete fix is described in the [Play around with CKAN portal](/docs/dms/ckan/play-around). (Your next step. ;))

site/content/docs/dms/ckan/install-extension.md

@@ -1,76 +0,0 @@
----
-sidebar: auto
----
-
-# Installing extensions
-
-A CKAN extension is a Python package that modifies or extends CKAN. Each extension contains one or more plugins that must be added to your CKAN config file to activate the extension’s features.
-
-In this sections we will teach you only how to install existing extensions. See [next steps](/docs/dms/ckan/create-extension) in case you need to create or modify extensions
-
-## Add new extension
-
-Lets install [Hello World](https://github.com/rclark/ckanext-helloworld) on the portal. For that we need to do 2 thing:
-
-1. Install extension when building docker image
-2. Add new extension to CKAN plugins
-
-### Install extension on docker build
-
-For this we need to modify Dockerfile for ckan service. Let's edit it:
-
-```
-vi ckan/Dockerfile.dev
-
-# Add following
-RUN pip install -e git+https://github.com/rclark/ckanext-helloworld.git#egg=ckanext-helloworld
-```
-
-*Note:* In this example we use vi editor, but you can choose any of your choice.
-
-### Add new extension to plugins
-
-We need to modify .env file for that - Search for `CKAN_PLUGINS` and add new extension to the existing list:
-
-```
-vi .env
-
-CKAN__PLUGINS=helloworld envvars image_view text_view recline_view datastore datapusher
-```
-
-## Check extension is installed
-
-After modifying configuration files you will need to restart the portal. If your CKAN protal is up and running bring it down and re-start
-
-```
-docker-compose -f docker-compose.dev.yml stop
-docker-compose -f docker-compose.dev.yml up --build
-```
-
-### Check what extensions you already have:
-
-http://ckan:5000/api/3/action/status_show
-
-Response should include list of all extensions including `helloworld` in it.
-
-```
-"extensions": [
-  "envvars",
-  "helloworld",
-  "image_view",
-  "text_view",
-  "recline_view",
-  "datastore",
-  "datapusher"
-]
-```
-
-### Check the extension is actually working
-
-This extension simply adds new route `/hello/world/name` to the base ckan and says hello
-
-http://ckan:5000/hello/world/John-Doe
-
-## Next steps
-
-[Create your own extension](/docs/dms/ckan/create-extension)

site/content/docs/dms/ckan/play-around.md

@@ -1,285 +0,0 @@
----
-sidebar: auto
----
-
-# How to play around with CKAN
-
-In this section, we are going to show some basic functionality of CKAN focused on the API.
-
-## Prerequisites
-
-- We assume you've already completed the [Getting Started Guide](/docs/dms/ckan/getting-started).
-- You have a basic understanding of Key data portal concepts:
-
-CKAN is a tool for making data portals to manage and publish datasets. You can read about the key concepts such as Datasets and Organizations in the User Guide -- or you can just dive in and play around!
-
-https://docs.ckan.org/en/2.9/user-guide.html
-
->[!tip]
-Install a [JSON formatter plugin for Chrome](https://chrome.google.com/webstore/detail/json-formatter/bcjindcccaagfpapjjmafapmmgkkhgoa?hl=en) or browser of your choice.
-
-If you are familiar with the command line tool `curl`, you can use that.
-
-In this tutorial, we will be using `curl`, but for most of the commands, you can paste a link in your browser. For POST commands, you can use [Postman](https://www.getpostman.com/) or [Google Chrome Plugin](https://chrome.google.com/webstore/detail/postman/fhbjgbiflinjbdggehcddcbncdddomop).
-
-
-## First steps
-
->[!tip]
-By default the portal is accessible on http://localhost:5000. Let's update your `/etc/hosts` to access it on http://ckan:5000:
-
-```
-vi /etc/hosts      # You can use the editor of your choice
-# add following
-127.0.0.1 ckan
-```
-
-
-At this point, you should be able to access the portal on http://ckan:5000.
-
-![CKAN Home Page](https://i.imgur.com/T5LWo8A.png)
-
-Let's add some fixtures to it. For software, a fixture is something used consistently (in this case, data for you to play around with). Run the following from your terminal (do NOT cut the previous docker process as this one depends on the already launched docker, run in another terminal):
-
-```sh
-docker-compose -f docker-compose.dev.yml exec ckan-dev ckan seed basic
-```
-
-Optionally you can `exec` into a running container using 
-
-```sh
-docker exec -it [name of container] sh
-```
-
-and run the `ckan` command there
-```sh
-ckan seed basic
-```
-
-You should be able to see 2 new datasets on home page:
-
-![CKAN with data](https://i.imgur.com/BiSifyb.png)
-
-To get more details on ckan commands please visit [CKAN Commands Reference](https://docs.ckan.org/en/2.9/maintaining/cli.html#ckan-commands-reference).
-
-### Check CKAN API
-
-This tutorial focuses on the CKAN API as that is central to development work and requires more guidance. We also invite you to explore the user interface which you can do directly yourself by visiting http://ckan:5000/.
-
-#### Let's check the portal status
-
-Go to http://ckan:5000/api/3/action/status_show.
-
-You should see something like this:
-
-```json
-{
-  "help": "https://ckan:5000/api/3/action/help_show?name=status_show",
-  "success": true,
-  "result": {
-  "ckan_version": "2.9.x",
-  "site_url": "https://ckan:5000",
-  "site_description": "Testing",
-  "site_title": "CKAN Demo",
-  "error_emails_to": null,
-  "locale_default": "en",
-  "extensions": [
-    "envvars",
-    ...
-    "demo"
-    ]
-  }
-}
-```
-
-This means everything is OK: the CKAN portal is up and running, the API is working as expected. In case you see an internal server error, please check the logs in your terminal.
-
-### A Few useful API endpoints to start with
-
-CKAN's Action API is a powerful, RPC-style API that exposes all of CKAN's core features to API clients. All of a CKAN website's core functionality (everything you can do with the web interface and more) can be used by external code that calls the CKAN API.
-
-#### Get a list of all datasets on the portal
-
-http://ckan:5000/api/3/action/package_list
-
-```json
-{
-  "help": "http://ckan:5000/api/3/action/help_show?name=package_list",
-  "success": true,
-  "result": ["annakarenina", "warandpeace"]
-}
-```
-
-#### Search for a dataset
-
-http://ckan:5000/api/3/action/package_search?q=russian
-
-```json
-{
-  "help": "http://ckan:5000/api/3/action/help_show?name=package_search",
-  "success": true,
-  "result": {
-    "count": 2,
-    ...
-  }
-}
-```
-
-#### Get dataset details
-
-http://ckan:5000/api/3/action/package_show?id=annakarenina
-
-```json
-{
-  "help": "http://ckan:5000/api/3/action/help_show?name=package_show",
-  "success": true,
-  "result": {
-    "license_title": "Other (Open)",
-    ...
-  }
-}
-```
-
-#### Search for a resource
-
-http://ckan:5000/api/3/action/resource_search?query=format:plain%20text
-
-```json
-{
-  "help": "http://ckan:5000/api/3/action/help_show?name=resource_search",
-  "success": true,
-  "result": {
-    "count": 1,
-    "results": [
-      {
-        "mimetype": null,
-        ...
-      }
-    ]
-  }
-}
-```
-
-#### Get resource details
-
-http://ckan:5000/api/3/action/resource_show?id=288455e8-c09c-4360-b73a-8b55378c474a
-
-```json
-{
-  "help": "http://ckan:5000/api/3/action/help_show?name=resource_show",
-  "success": true,
-  "result": {
-    "mimetype": null,
-    ...
-  }
-}
-```
-
-*Note:* These are only a few examples. You can find a full list of API actions in the [CKAN API guide](https://docs.ckan.org/en/2.9/api/#action-api-reference).
-
-### Create Organizations, Datasets and Resources
-
-There are 4 steps:
-
-- Get an API key;
-- Create an organization;
-- Create dataset inside an organization (you can't create a dataset without a parent organization);
-- And add resources to the dataset.
-
-#### Get a Sysadmin Key
-
-To create your first dataset, you need an API key.
-
-You can see sysadmin credentials in the file `.env`. By default, they should be
-
-- Username: `ckan_admin`
-- Password: `test1234`
-
-1. Navigate to http://ckan:5000/user/login and login.
-2. Click on your username (`ckan_admin`) in the upright corner.
-3. Scroll down until you see `API Key` on the left side of the screen and copy its value. It should look similar to `c7325sd4-7sj3-543a-90df-kfifsdk335`.
-
-#### Create Organization
-
-You can create an organization from the browser easily, but let's use [CKAN API](https://docs.ckan.org/en/2.9/api/#ckan.logic.action.create.organization_create) to do so.
-
-```sh
-curl -X POST http://ckan:5000/api/3/action/organization_create -H "Authorization: 9c04a69d-79f4-4b4b-b4e1-f2ac31ed961c" -d '{
-  "name": "demo-organization",
-  "title": "Demo Organization",
-  "description": "This is my awesome organization"
-}'
-```
-
-Response:
-
-```json
-{
-  "help": "http://ckan:5000/api/3/action/help_show?name=organization_create",
-  "success": true,
-  "result": {"users": [
-    {
-    "email_hash":
-    ...
-    }
-  ]}
-}
-```
-
-#### Create Dataset
-
-Now, we are ready to create our first dataset.
-
-```sh
-curl -X POST http://ckan:5000/api/3/action/package_create -H "Authorization: 9c04a69d-79f4-4b4b-b4e1-f2ac31ed961c" -d '{
- "name": "my-first-dataset",
- "title": "My First Dataset",
- "description": "This is my first dataset!",
- "owner_org": "demo-organization"
-}'
-```
-
-Response:
-
-```json
-{
-  "help": "http://ckan:5000/api/3/action/help_show?name=package_create",
-  "success": true,
-  "result": {
-    "license_title": null,
-    ...
-  }
-}
-```
-
-This will create an empty (draft) dataset.
-
-#### Add a resource to it
-
-```sh
-curl -X POST http://ckan:5000/api/3/action/resource_create -H "Authorization: 9c04a69d-79f4-4b4b-b4e1-f2ac31ed961c" -d '{
-  "package_id": "my-first-dataset",
-  "url":  "https://raw.githubusercontent.com/frictionlessdata/test-data/master/files/csv/100kb.csv",
-  "description": "This is the best resource ever!" ,
-  "name": "brand-new-resource"
-}'
-```
-
-Response:
-
-```json
-{
-  "help": "http://ckan:5000/api/3/action/help_show?name=resource_create",
-  "success": true,
-  "result": {
-    "cache_last_updated": null,
-    ...
-  }
-}
-```
-
-That's it! Now you should be able to see your dataset on the portal at http://ckan:5000/dataset/my-first-dataset.
-
-## Next steps
-
-* [Install Extensions](/docs/dms/ckan/install-extension).

site/content/docs/dms/cms-for-data-portals.md

@@ -1,81 +0,0 @@
----
-sidebar: auto
----
-
-# Content Management System (CMS) for Data Portals
-
-## Summary
-
-When selecting a CMS solution for Data Portals, we always recommend using headless CMS solution as it provides full flexibility when building your system. Headless CMS means only content (no HTML, CSS, JS) is created in the CMS backend and delivered to Frontend via API.
-
-> The traditional CMS approach to managing content put everything in one big bucket — content, images, HTML, CSS. This made it impossible to reuse the content because it was commingled with code. Read more - https://www.contentful.com/r/knowledgebase/what-is-headless-cms/.
-
-## Features
-
-Core features:
-
-* Create and manage blog posts (or news), e.g., `/news/abcd`
-* Create and manage static pages, e.g., `/about`, `/privacy` etc.
-
-Important features:
-
-* User management, e.g., ability to manage editors so that multiple users can edit content.
-* User roles, e.g., ability to assign different roles for users so that we can have admins, editors, reviewers.
-* Draft content, e.g., useful when working on content development for review/feedback loop. However, this is not essential if you have multiple environments.
-* A syntax for writing content with text formatting, multi-level headings, links, images, videos, bullet points. For example, markdown.
-* User-friendly interface (text editor) to write content.
-
-```mermaid
-graph LR
-
-CMS -.-> Blog["Blog or news section"]
-CMS -.-> IndBlog["Individual blog post"]
-CMS -.-> About["About page content"]
-CMS -.-> TC["Terms and conditions page content"]
-CMS -.-> Privacy["Privacy policy"]
-CMS -.-> Other["Other static pages"]
-```
-
-## Options
-
-Headless CMS options:
-
-* WordPress (headless option)
-* Drupal (headless option)
-* TinaCMS - https://tina.io/
-* Git-based CMS - custom soltion based on Git repository.
-* Strapi - https://docs.strapi.io/developer-docs/latest/getting-started/introduction.html
-* Ghost - https://ghost.org/docs/ 
-* CKAN Pages (built-in CMS option) - https://github.com/ckan/ckanext-pages 
-
-*Note, there are loads of CMS available both in open-source and proprietary software. We are only considering few of them in this article and our requirement is that we should be able to fetch content via API (headless CMS). Readers are welcome to add more options into the list.*
-
-Comparison criteria:
-
-* Self-hosting (note this isn't criteria for most of projects and using managed hosting is a better option sometimes)
-* Free and open source
-* Multi language posts (unnecessary if your portal is single language)
-
-Comparison:
-
-| Options  | Hosting  | Free     | Multi language |
-| -------- | -------- | -------- | -------------- |
-| Drupal   | Tedious  | Yes      | Not straigtforward|
-| WordPress| Tedious  | Yes      | Terrible UX    |
-| TinaCMS  | Medium   | Yes      | Limited        |
-| Git-based| Easy     | Yes      | Custom         |
-| Strapi   | Medium   | Yes      | Simple         |
-| Ghost    | Medium   | Yes      | Simple         |
-| CKAN Pages| Easy    | Yes      | ?              |
-
-
-## Conclusion and recommendation
-
-Final decision should be made based on the following items:
-
-* How often editors will create content? E.g., daily, weekly, monthly, occasionally.
-* How much content you already have and need to migrate?
-* How many content editors you are planning to have? What are their technical expertise?
-* Is there any specific requirements, e.g., you must host in your cloud?
-
-By default, we would recommend considering options such as Strapi, TinaCMS and Git-based CMS. We can even start with simple CKAN's built-in Pages and only move to sophisticated CMS once it is required.