open-index/open-npm huggingface dataset:
npm package: @hestia-earth/blog
Description: Hestia Blog pages
Author: Guillaume Royer
Latest version: 0.0.1

# Hestia Blog

This repository contains the raw content of the blog posts written in Markdown language.

Every file under _src/posts_ will be automatically deploy to https://hestia-earth.gitlab.io/hestia-blog domain.

Example:
- src/posts/welcome.md will be deployed to https://hestia-earth.gitlab.io/hestia-blog/welcome
- src/posts/my-first-blog.md will be deployed to https://hestia-earth.gitlab.io/hestia-blog/my-first-blog

Note: only lower chars, dashes (`-`) and numbers are allowed in the filenames.

## Featuring an article

The list of featured articles can be found in the `featured.txt` file.
Each featured article must be on a new line, and must point to the name of the markdown file.

Example:
```
article1
article2
```

## Writing Guidelines

1. Create a new file under `src/posts` and make sure the filename only uses lowercase letters, numbers and dashes.
2. Start the file with a header level 1 using a single `#`. Example:

```markdown
# This is the header

This is the content.

## This is a sub-header
```

The header level 1 will be automatically used as Title for the Post, so please try to keep it short.

The second line (omitting the blank lines) will be used as abstract.

### References or citations

To reference or cite another article, please use the following format:

```markdown
This article references <cite><a href="https://www.nature.com/articles/nature10452">another article</a></cite>
```

This will be parsed so it is displayed as a reference, using the content inside the link as the full reference name:

> 1 another article https://www.nature.com/articles/nature10452

### Adding metadata

It is possible to add a list of metadata, using the following format:
```
/<name of metadata> ~Title~
```

These metadata must be added at the end of the file, one per line. The list of metadata is:

| Name | Required | Can be added multiple times |
| ---- | ---- | ---- |
| `category` | Yes | ❌ |
| `tag` | No | ✅ |

**Example:**

```markdown
# This is the title

This is the abstract.

/category ~Hestia for dummies~
/tag ~Hestia~
/tag ~Beginners~
```

### Adding images or videos

To add an image or a video to a post:
- add the file under the `src/assets` folder. Note: you can use sub-directories to organise the files.
- make sure to use a simple name, without special characters. So only letters and numbers, dashes or underscores.
- in the content of the post, use either
  ```html
  <img src="/blog/assets/<path to the file>" alt="Text to describe the image" height="auto">
  ```
  or to use videos in different formats
  ```html
  <video width="320" height="240" controls>
    <source src="/blog/assets/<path to the file>.mp4" type="video/mp4">
    <source src="/blog/assets/<path to the file>.ogg" type="video/ogg">
  </video>
  ```
npm package: @hestia-earth/bulma-tagsinput
Description: A full-featured user interface for managing tags with Bulma supporting autocomplete.
Author: Guillaume Royer
Latest version: 1.0.5

# Introduction
This components has been developped as a [Bulma](https://bulma.io) extension and brings **a full-featured user interface for managing tags  supporting autocomplete** to your project.

[![npm](https://img.shields.io/npm/v/@creativebulma/bulma-tagsinput.svg)](https://www.npmjs.com/package/@creativebulma/bulma-tagsinput)
[![npm](https://img.shields.io/npm/dm/@creativebulma/bulma-tagsinput.svg)](https://www.npmjs.com/package/@creativebulma/bulma-tagsinput)
[![](https://data.jsdelivr.com/v1/package/npm/@creativebulma/bulma-tagsinput/badge)](https://www.jsdelivr.com/package/npm/@creativebulma/bulma-tagsinput)

---

## Prerequisites
This component extends [Bulma CSS Framework](https://bulma.io) and requires it to work.

## Get Started
```shell
npm i -D @creativebulma/bulma-tagsinput
```
Full installation steps can be found here: [installation steps](https://bulma-tagsinput.netlify.app/get-started)

## Documentation & Demo
Full documentation and demo are available [here](https://bulma-tagsinput.netlify.app)

## About the project
BulmaTagsInput is © 2020 by [CreativeBulma](https://github.com/CreativeBulma).

## License
BulmaTagsInput is distributed under [MIT](https://github.com/CreativeBulma/bulma-tagsinput/blob/master/LICENSE) license.

## Contributing
**Contribution are welcome!**  
You found a bug, a typo issue ? Feel free to create a PR on the [github repository](https://github.com/CreativeBulma/bulma-tagsinput/) of this project.

When contributing to this project, please first discuss the change you wish to make via issue on the [github repository](https://github.com/CreativeBulma/bulma-tagsinput/issues), email, or any other method with the owners of this project before making a change.
npm package: @hestia-earth/glossary
Description: HESTIA Earth Glossary library
Author: Guillaume Royer
Latest version: 0.91.1

# HESTIA Glossary

Describing data consistently with the same terms makes data exchange possible. HESTIA maintains a [Glossary of Terms](https://hestia.earth/glossary) to describe the agri-food system. Only these Terms can be used to describe data.

Terms are created or amended as follows:

1) Glossaries for each termType are initially created in Excel files. Each column header must either be a field in the schema for Term, a Property from the Glossary of Terms, or a lookup.

2) To update or change an Excel file, carefully follow the [contribution guidelines](/CONTRIBUTING.md). The HESTIA team will review your updates and approve them.

3) Each row of the Excel file is converted into a JSON-LD file following the schema for the Term.

4) The terms are then indexed, assigned `@id` fields, and are available for use when uploading new data or performing calculations on existing data.

# Properties versus lookups

Properties are data items that describe a Term in more depth or differentiate a Term from another Term. For example, the dry matter of a crop defines the nature of the crop (e.g. whether it is pre-drying, dried, or expressed in dry matter equivalents). Properties can be overridden by the user.

Lookups provide additional information about each Term for use in environmental models. Lookups cannot be overridden by the user.

# Property and lookup colour coding

The data in Properties and lookups can be of variable quality and might be missing. For lookups we indicate this with `dataState`. For both Properties and lookups we also use the following colour coding.

| `dataState`           | Colour      | Definition                                                                  |
|-----------------------|-------------|-----------------------------------------------------------------------------|
| `complete`            | Dark green  | The data are complete with no validation issues identified.                 |
| `not required`        | Dark green  | The data are not required or relevant.                                      |
| `requires validation` | Light Green | The data require validation due to possible or known errors.                |
| `missing`             | Pink        | The data are missing and need to be added to run models based on this Term. |
| `unassigned`          | White       | A data state has not been assigned.                                         |

# Contributing

Please read the [contribution guidelines](/CONTRIBUTING.md) before making contributions to the Glossary of Terms.
npm package: @hestia-earth/schema-convert
Description: HESTIA Schema Converters
Author: Guillaume Royer
Latest version: 36.1.0

# HESTIA Schema Converter

Module to convert CSV to JSON or JSON to CSV following HESTIA's Schema

## Install

```sh
npm install @hestia-earth/schema-convert
```

## Usage

### Converting CSV to JSON

```sh
hestia-convert-to-json <folder containing .csv files>
```

### Converting JSON to CSV

```sh
hestia-convert-to-csv <folder containing .json or .jsonld files>
```
npm package: @hestia-earth/schema-validation
Description: HESTIA Schema Validation
Author: Guillaume Royer
Latest version: 36.1.0

# HESTIA Schema Validation

Module to validate data using the HESTIA Schema and Ajv.

## Install

```sh
npm install @hestia-earth/schema @hestia-earth/schema-validation
```

## Example validating JSON

```javascript
const { SchemaType } = require('@hestia-earth/schema');
const { validator } = require('@hestia-earth/schema-validation/validate');

// Set to `true` to validate existing Nodes (@type/@id) or `false` for Nodes to upload (type/id)
const strictMode = false;
// Initialise the validation function, do this only once
const schemaValidation = validator(undefined, strictMode);

const node = {
  type: SchemaType.Cycle,
  id: 'my first cycle'
};

(async () => {
  const { success, errors } = await schemaValidation(node);
  console.log(success);
  // list of errors in Ajv formatting. See https://github.com/ajv-validator/ajv/tree/v6.12.6#validation-errors
  console.log(errors);
})();
```