Added blog for cross-posting (#88)

* Added blog for cross-posting

* Updated wording

* Fixed build

astro.config.js

@@ -3,6 +3,7 @@ import starlight from "@astrojs/starlight"
 import { defineConfig } from "astro/config"
 import rehypeAutolinkHeadings from "rehype-autolink-headings"
 import { remarkHeadingId } from "remark-custom-heading-id"
+import starlightBlog from "starlight-blog"
 
 // import starlightLinksValidator from "starlight-links-validator"
 
@@ -31,7 +32,19 @@ export default defineConfig({
       customCss: ["/assets/styles.css"],
       tableOfContents: { minHeadingLevel: 2, maxHeadingLevel: 5 },
       // The link validator is useful for debugging but it cleates a lot of false positives
-      // plugins: [starlightLinksValidator()],
+      plugins: [
+        starlightBlog({
+          authors: {
+            sapetti9: {
+              name: "sapetti9",
+              title: "Sara Petti",
+              picture: "https://avatars.githubusercontent.com/u/74717970?v=4",
+              url: "https://github.com/sapetti9",
+            },
+          },
+        }),
+        // starlightLinksValidator(),
+      ],
       sidebar: [
         { label: "Overview", autogenerate: { directory: "overview" } },
         { label: "Standard", autogenerate: { directory: "standard" } },

content/config.ts

@@ -1,9 +1,11 @@
 import { docsSchema } from "@astrojs/starlight/schema"
 import { defineCollection } from "astro:content"
-
-// import { i18nSchema } from '@astrojs/starlight/schema';
+import { blogSchema } from "starlight-blog/schema"
 
 export const collections = {
-  docs: defineCollection({ schema: docsSchema() }),
-  // i18n: defineCollection({ type: 'data', schema: i18nSchema() }),
+  docs: defineCollection({
+    schema: docsSchema({
+      extend: context => blogSchema(context),
+    }),
+  }),
 }

content/docs/blog/2023-11-15-v2-anouncement.md

@@ -0,0 +1,72 @@
+---
+title: Data Package (v2) work started
+date: 2023-11-15
+excerpt: We are very pleased to announce that thanks to the generous support of NLnet we have kickstarted the Data Package (v2) work. After a first discussion with the community in the last call, we are setting up a working group to help us with the v2 release.
+tags:
+  - news
+authors:
+  - sapetti9
+---
+
+We are very pleased to announce that thanks to the generous support of [NLnet](https://nlnet.nl/) we have kickstarted the [Data Package (v2)](https://specs.frictionlessdata.io/) update.
+
+After a first discussion with the community in [the last call](https://frictionlessdata.io/blog/2023/11/06/community-call/), we are setting up a working group to help us with the v2 release.
+
+Taking into account the group's concerns about the shortness of the initial timeline we proposed, we were able to work out an extension of the initial time frame until mid-2024. We are now aiming at **releasing the v2 of the Frictionless specs by June 2024**.
+
+## Goal
+
+**Our overarching goal is to make the Frictionless specs**, namely the Data Package, Data Resource, File Dialect, and Table Schema standards, **a finished product**, establishing a sustainable mechanism for future maintenance extension.
+
+The modular approach will of course still be the cornerstone of the Frictionless specs v2, and we won’t introduce any breaking changes.
+
+## Additional deliverables
+
+- Together with the working group, we will start a reference collection of data types we want the v2 to support in a GitHub issue.
+
+- We will work with leading data publishing portals, namely CKAN and Zenodo, to provide native Data Package export integration.
+
+- The Frictionless core team at OKFN, will work on a new small Python library, a metadata mapper, with the objective of making it simpler to create standard extensions, and being able to use it in the data publishing systems integrations (Zenodo/CKAN/etc).
+
+- A new website and new documentation will be published, with improved technical language and better accessibility.
+
+## Roadmap
+
+The project roadmap will be mainly guided by the list of issues submitted by the community throughout the years, and collected [here](https://github.com/frictionlessdata/specs/milestone/6).
+
+## Social Aspect
+
+We will hold **monthly update calls** for the working group, which are of course not compulsory, and which will be open to the broader community too. In parallel **we will work asynchronously with the working group, using a review model** for any changes in the specifications themselves.
+
+## Decision-making
+
+For every GitHub issue on the specs submitted by the community throughout the years, the Frictionless core team or any working group member will propose a recommended action to the working group. The action proposed will be **accepted if consensus with the working group is reached**, meaning we have arrived at a decision, or at least a compromise, that everyone can live with.
+
+The working group will be invited to share their view in a devoted GitHub issue. If a broader conversation is needed, the proposal discussion can be elevated to the monthly call for deliberation. The working group will be given a reasonable amount of time to review the proposed action.
+
+**Consensus is reached and the issue is closed if at least ⅔ of the working group members participate in the discussion and express their favourable opinion**. In case of serious and explicitly stated concerns, working group members who are core library investors (at the moment: OKFN, INBO, Datopian) may veto a proposed action.
+
+The community manager at OKFN will reach out to working group members who did not participate in the discussion to make sure their opinion is also captured. We want to ensure that reminders of your participation are handled with care. You can expect a gentle and considerate approach, such as receiving an email once every two weeks highlighting any issues where your vote is pending. Our goal is to keep you informed without causing any unnecessary inconvenience, so you can feel confident and at ease with the process
+
+Decision-making on the technical maintenance of the specs will be centralised by OKFN.
+
+## Diversity
+
+Leveraging diversity is an opportunity that we must embrace for the benefits it brings. Extensive research consistently demonstrates that diverse participation leads to better outcomes and more resilient technologies — diverse communities are unequivocally stronger communities.
+
+We acknowledge the need for greater diversity in our community, and we understand that fostering diversity, equity, and inclusion requires substantial effort. We cannot underestimate the challenges before us. Confronting the deep-rooted and centuries-old racist components of our system is a huge challenge, and we understand that achieving racial equity is a continual journey with no predefined endpoint.
+
+Our mission is to build equity within our community, fostering inclusion and amplifying diversity across all aspects of the Frictionless project. For our specs update, we are proactively encouraging every member of the community involved in the working group to identify and invite candidates interested in contributing to the update work, with a particular emphasis on enhancing the diversity of our group.
+
+We welcome contributors from diverse backgrounds, recognising that individuals with varied experiences bring forth new and innovative ideas that help create an inclusive and welcoming ecosystem. Our goal is to create an inclusive and friendly environment based on mutual respect and exchange, ensuring that no one feels isolated, and everyone is motivated to actively contribute to the project's development.
+
+Acknowledging the ethical imperative, we understand that recruiting individuals into a community historically designed to exclude them is neither ethical nor effective without adequate support. We therefore prioritise transparency with new community members, providing a [contributor's guide](https://frictionlessdata.io/work-with-us/contribute/), a [published roadmap](https://frictionlessdata.io/development/roadmap/), and comprehensive documentation to ensure clarity and support throughout their engagement. Our [Code of Conduct](https://frictionlessdata.io/work-with-us/code-of-conduct/) applies to all activities linked to the Frictionless Data project, and it is enforced by our community manager. As part of this project, we will make it a priority to enhance the accessibility of our documentation and website, aiming to make them as inclusive as possible.
+
+We welcome any other suggestions that would help us enhance diversity, equity, and inclusion in our work. Please let us know if you have a good idea to share!
+
+## Funding
+
+This project is funded through [NGI0 Entrust](https://nlnet.nl/entrust), a fund established by [NLnet](https://nlnet.nl) with financial support from the European Commission's [Next Generation Internet](https://ngi.eu) program. Learn more at the [NLnet project page](https://nlnet.nl/project/FrictionlessStandards/).
+
+[<img src="https://nlnet.nl/logo/banner.png" alt="NLnet foundation logo" width="20%" />](https://nlnet.nl)
+[<img src="https://nlnet.nl/image/logos/NGI0_tag.svg" alt="NGI Zero Logo" width="20%" />](https://nlnet.nl/entrust)

package.json

@@ -35,7 +35,8 @@
     "prettier": "^3.3.2",
     "prettier-plugin-astro": "^0.14.0",
     "rehype-autolink-headings": "^7.1.0",
-    "starlight-links-validator": "^0.9.0",
-    "remark-custom-heading-id": "^2.0.0"
+    "remark-custom-heading-id": "^2.0.0",
+    "starlight-blog": "^0.9.0",
+    "starlight-links-validator": "^0.9.0"
   }
 }

src/content/config.ts

@@ -0,0 +1,15 @@
+import { docsSchema } from "@astrojs/starlight/schema"
+import { defineCollection } from "astro:content"
+import { blogSchema } from "starlight-blog/schema"
+
+// TODO:
+// remove this file when starlight-blog is updated to support Astro's `srcDir`
+// this file is just a copy of `content/config.ts`
+
+export const collections = {
+  docs: defineCollection({
+    schema: docsSchema({
+      extend: context => blogSchema(context),
+    }),
+  }),
+}