Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/iconify/website

New Iconify website, created with VitePress.
https://github.com/iconify/website

Last synced: 15 days ago
JSON representation

New Iconify website, created with VitePress.

Awesome Lists containing this project

README 

        
# Iconify Website



This repository contains source code for Iconify website, built with Vitepress.



Website is live at https://iconify.design/



## Build process



Read out [contributing guidelines](./CONTRIBUTING.md) before making any changes.



To build website, first install dependencies:



```bash

pnpm install

```



Then you can build the website. To build production code, run this:



```bash

nr build

```



Build process will put all HTML files in directory `dist`.



To build production code and preview it, run



```bash

nr preview

```



Do not commit changes that aren't ready for production.



If you want to preview website without building, run this:



```bash

nr dev

```



## Sources



Source files are written in Markdown and are stored in the following directories:

- `about`

- `docs`

- `getting-started`

- `news`

- `privacy`

- `sponsors`

- `support`



Main entry file for each directory is `index.md`.



Documentation uses slightly modified Markdown syntax, see "Markdown" section below.



## Assets



Assets are stored in directory `public`.



## Markdown



Documentation uses extended Markdown syntax.



### Headings



First big change is in headings. Every Markdown file must have a heading, which is written in YAML.



Heading properties:



- title. Page title that is used in `` tag in HTML. This is a mandatory property.

- replacements. This is used to dynamically replace strings in output. For example, to make sure the latest version of the project is always the same in all documents without updating every document. See "Replacements" section below.

- types, functions, classes. Links to types, functions and classes that are used in documents.



### Inline code



Each inline code entry can have a type. This is used to apply different syntax highlight to inline code, add links to types.



Type is placed at the beginning of inline code in brackets: `[type]string`.



Available types:



- attr: used for HTML attributes, with or without values: `[attr]data-inline`, `[attr]foo="bar"`.

- key, prop: used for keys and object properties. Usually used when describing types: `[prop]hFlip`.

- var: variable name: `[var]Iconify`.

- tag: HTML tag: `[tag]svg`. Syntax highlighter will add "<" and ">" to tag if missing.

- type: variable type: `[type]IconifyIcon`. If heading in a document has "types" section with a relative link to type documentation, syntax highlighter will wrap type in a link.

- class: used for class names: `[class]Collection`, `[class]Promise`. If a link for class is present in metadata, parser will also convert it to link.

- func: used for function names: `[func]addIcon`, `[func]addCollection()`. If a link for function is present in metadata, parser will also convert it to link.

- npm, packagist: used for names of NPM and Packagist packages: `[npm]@iconify/react`.

- icon: used for icon names: `[icon]mdi:home`.

- str, bool, num, object, null: used for values: `[str]Hello World`, `[bool]true`, `[num]12345`.

- js, bash, json, php, css, html: used to highlight syntax for any of those languages: `[js]console.log('Success!');`

- url: URL or domain name: `[url]github.com`, `[url]https://github.com/iconify`.

- file: filename: `[file]src/themes.ts`.



### External code



Instead of writing code in Markdown files, many documents use external code.



Most of the external code files are stored in `code-samples`. Stylesheets used in `css` property, could also be located in `.vitepress/theme/samples`.



External code is written as YAML code block with various properties. The only mandatory property is "src", other properties are optional.



Examples:



```yaml

src: iconify1/size-demo.html

title: 'HTML:'

css: iconify1/size-demo.scss

cssTitle: 'Stylesheet:'

demo: true

demoTitle: 'Demo:'

class: iconify1-size-demo

```



This will display 2 chunks of code + demonstration.



```yaml

src: types/alias-raw.json

title: 'IconifyAlias:'

extra:

  - src: types/alias-json.json

    title: 'IconifyJSON:'

  - src: types/alias-merged.json

    title: 'Merged "arrow-right" icon as IconifyIcon:'

```



This will display 3 chunks of code in one contained block. Property "src" points to filename, property "title" adds caption above code block.



Code block properties:



- src: source for the main code file.

- title: title for the main code file. Displayed above code block.

- hint: hint for the main code file. Displayed below code block.

- copy: boolean, if set to `false`, disables copy to clipboard function for code sample.



Properties for stylesheet:



- css: source for stylesheet.

- cssTitle: title for stylesheet.

- cssHint: hint for stylesheet.



Stylesheet code is displayed below main code, but in the same container.



Properties for demo:



- demo: boolean. If true, demo will be shown.

- demoTitle: title for demo.

- demoHint: hint for demo.

- class: class to wrap demo. See `.vitepress/theme/samples/_samples.scss`.



Demo block will render raw HTML code from source. It will be rendered below main code and optional stylesheet.



Sometimes demo code might be different from raw code. For example, when using samples for Iconify SVG Framework version 1 that work differently in new version. Website uses the latest version of Iconify SVG Framework, so code samples might not display correctly. To avoid that, create second sample file with ".demo" before filename. That file will be rendered instead of original source file. See documentation for Iconify SVG Framework version 1 for examples.



Extra chunks of code:



- extra: array of extra code chunks. Each chunk has the same 3 properties as original code: `src`, `title` and `hint`.



Extra chunks of code are often used to display several code samples that should be placed in the same container.



### Partials



To avoid repeating the same text over and over again, parser supports partial documents.



Partial documents can be in Markdown and in HTML format, they are located in `partials`.



Partial files are included in documents using inline code that starts with "include": `include notices/iconify1`.



## Replacements



Text replacements are used in documentation to re-use common data, such as version numbers and counters without updating every document.



Replacements are applied to document and to external code included in that document.



Example of replacements in heading:



```yaml

replacements:

  - code: '/1/1.0.3/'

    value: '/${iconify1.version.major}/${iconify1.version.full}/'

```



This will replace all entries of `/1/1.0.3/` with the current data. Syntax `${iconify1.version.major}` is used for variables. Variables are stored in `.vitepress/markdown/config.ts`.



## Links



Links in the markdown syntax must be links to .md files, not URLs. Vitepress will clean them up and point to correct URL.



In Vitepress, markdown can include HTML code. Links in HTML code are not parsed, so they must link to correct URL, not md file.



## Licence



Iconify documentation is dual-licensed under Apache 2.0 licence. You can use this repository to build custom documentation for your project.



`SPDX-License-Identifier: Apache-2.0`



© 2020-PRESENT Vjacheslav Trushkin