Awesome

<h1 align="center">Docsify PUML</h1> <p align="center"> <img alt="logo" src="./docs/_media/logo.svg" width="250"> </p> <p align="center">Docsify plugin to parse PlantUML content</p> <p align="center"> <img src="https://badgen.net/github/issues/indieatom/docsify-puml?style=for-the-badge" alt="issues"/> <img src="https://badgen.net/npm/node/docsify-puml?style=for-the-badge" alt="node-version"/> <img src="https://badgen.net/npm/v/docsify-puml?style=for-the-badge" alt="version"/> <img src="https://badgen.net/badgesize/normal/https/unpkg.com/docsify-puml/dist/docsify-puml.min.js?style=for-the-badge" / </p> <p align="center"> <a href="#install">Install</a> • <a href="#usage">Usage</a> • <a href="#features">Features</a> • <a href="#options">Options</a> • <a href="#examples">Examples</a> • <a href="#meta">Meta</a> • <a href="#contributing">Contributing</a> </p>

Install

It's just simple like insert that into your index.html

<script>
window.$docsify = {
  plantuml: {
    skin: 'default',
  },
}
</script>
...
<script src="//unpkg.com/docsify-puml/dist/docsify-puml.min.js"></script>

See Options for more details.

Usage

There are two ways to use that in your documentations. You can write directly into your markdown doc or you can import that from an external .puml file.

In code

Just create an code block with plantuml at lang type.

Ex.:

### Section X

```plantuml
@startuml
Alice -> Bob: Authentication Request
Bob --> Alice: Authentication Response

Alice -> Bob: Another authentication Request
Alice <-- Bob: another authentication Response
@enduml
```

Include External `.puml`

To include a .puml file into your doc, need to use an sitaxe like the !include from default PUML, but surrounded by [[ and ]].

Ex.:

### Section X

```plantuml
@startuml
[[!include ../assets/pumls/my-chart.puml]]

Alice -> Bob: Another authentication Request
Alice <-- Bob: another authentication Response
@enduml
```

Features

Options

At now, that are options we have, with default their values:

{
  "skin": "default",
  "renderAsObject": false,
  "asLink": false,
  "serverPath": "https://custom-server.local/plantuml/png/"
}

skin

That param says what skin(theme) should use in all plantuml blocks. By default, it's default, an clean implementation created by @matthewjosephtaylor.

Value	Description
`default`	An clean implementation
`classic`	Default ~~ugly~~ PlantUML theme
`./assets/local-puml-theme.pu`	An string pointing to a local file with your custom theme
`https://external.link/my-puml-theme.pu`	An url to a external server hosting a theme

renderAsObject

That param says if any rendered object will be inside a <img src=''/> tag (if true) or inside a <object type='image/svg+xml' data=''/> tag (if false).

That second option is most used when you want to interact with generated svg, like using links. To use with an link, for example, should be like that:

```plantuml
@startuml
Alice -> Bob: Authentication Request [[$./other-file docs]]
Bob --> Alice: Authentication Response [[$../other-file docs]]
@enduml
```

Note: Is VERY IMPORTANT use an $ to say that is a link.

asLink

That param says if your generate image would be a link to open on blank page. By default it's false.

Note: Using with an <object type='image/svg+xml' data=''/> tag still not work properly.

serverPath

That param says what server should use to render the svg. By default, use the official PlantUML server. If you're using an own server, set in this option.

Examples

For now, has three examples into examples folder:

Basic - with an in code implementation;
Themeable - with a theme implementation (from external source theme);
Import PUML - with implementation using an .puml file;

Contributing

Fork it (https://github.com/indieatom/docsify-puml/fork)
Create your feature branch (git checkout -b feature/fooBar)
Commit your changes (git commit -am 'Add some fooBar')
Push to the branch (git push origin feature/fooBar)
Create a new Pull Request