npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

docsify-puml

v1.1.1

Published

Docsify plugin to parse PlantUML content

Readme


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
```

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;

Meta

Indie Atom – [email protected]

This repo is completelly based on @imyelo docsify-plantuml version.

Distributed under the MIT license. See LICENSE for more information.

Contributing

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