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

rhyla

v1.0.8

Published

Simple, template-driven Markdown documentation generator (CLI)

Readme

📚 Rhyla Documentation

Rhyla Documentation is a simple and flexible tool to quickly create and organize documentation using Markdown files and customizable templates.
The main idea is to allow developers to keep all project documentation organized, navigable, and with support for light and dark themes, without relying on heavy tools or complex configurations.


🚀 Motivation

  • Make it easy to create local and static documentation.
  • Use Markdown so content is easy to write and maintain.
  • Allow full customization of header, footer, sidebar, and themes.
  • Provide a simple development (rhyla dev) and build (rhyla build) workflow.

🛠 Basic Usage

  1. Install the project globally or use it via local CLI.
  2. Run:
    rhyla init

This will create the initial structure with:

  • header.html
  • config.yaml
  • home.md (this page)
  • body folder for your topics
  1. During development, use:
    rhyla dev

This will start a local server at http://localhost:3000 for preview.

  1. To generate static documentation, use:
    rhyla build

This will create the rhyla/ folder with the generated HTML files.


✏️ Start customizing!

The first recommended action is to adapt this home.md to your project's context.

How navigation is built

The sidebar is automatically generated from the directory tree inside rhyla/body/:

  • Each FOLDER inside body/ works as a GROUP / CATEGORY.
  • Each .md FILE becomes a processed page (Markdown → HTML).
  • Each .html FILE is included as-is (useful for highly customized pages).
  • The file path defines the route. Example: rhyla/body/guides/install.md → route /guides/install.
  • The default order is alphabetical (folder and file names). Use clear and consistent names.

Creating groups and topics

Example structure:

rhyla/
  body/
    introduction.md
    quickstart.md
    guide/
      install.md
      config.md
    api/
      auth.md
      users.html

Generated routes:

/introduction
/quickstart
/guide/install
/guide/config
/api/auth
/api/users

Naming best practices

  • Use lowercase and hyphens or camelCase: advanced-install.md or advancedInstall.md.
  • Avoid spaces and special characters.
  • Choose short, descriptive, and stable names.

When to use .md or .html

| Situation | Use .md | Use .html | |-----------|---------|-----------| | Common text, narrative docs | ✅ | | | Code with simple formatting | ✅ | | | Fully custom layout | | ✅ | | Ready-made HTML components | | ✅ |

Extra tips

  • Start simple: create just a few .md files and check the navigation.
  • Need a special page (internal landing)? Create a .html in that folder.
  • Restructuring? Just move/rename folders/files and restart the server (or reload) to reflect changes.

🆕 New in Version 1.0.8

🔒 Password Protection

Protect your documentation with password authentication:

{
  "password_doc": {
    "enabled": true,
    "passwords": [
      "yourSecurePassword123",
      "anotherValidPassword456"
    ]
  }
}

Features:

  • ✅ Multiple valid passwords support
  • ✅ Automatic 5-minute lockout after 5 failed attempts
  • ✅ Beautiful centered login card with blurred background
  • ✅ Persistent authentication across sessions
  • ✅ Real-time attempt counter

Developer Note: Use rhylaLogout() in the browser console to clear authentication during development.

📑 Custom Sidebar Groups

Organize your documentation with custom groups:

{
  "sidebar": [
    "home",
    {
      "title": "Getting Started",
      "children": [
        "introduction",
        "installation"
      ]
    },
    {
      "title": "API Reference",
      "children": [
        "api/endpoints",
        "api/authentication"
      ]
    }
  ]
}

Features:

  • ✅ Custom group titles
  • ✅ Expandable/collapsible folders
  • ✅ Support for nested paths
  • ✅ Direct file references within folders

⚠️ Limitations

  • Navigation and structure depend on using .md or .html files.
  • The sidebar is generated based on the folder structure, so folder and file names define groups and topics.
  • The system does not automatically process external links in the menu.
  • For global layout changes, you need to edit header.html, footer.html, and theme styles.
  • No plugin or extension support at the moment.

🔎 About Search and Indexing

  • All documentation pages (.md and .html) are automatically indexed and used in the search page (/buscar).
  • The search system relies on this index to provide fast and relevant results.
  • For correct operation, do not delete or rename the search page (search.html in rhyla/body).
  • The home.md file is required and must not be deleted, as it is the main entry page of your documentation. You should edit it to fit your project, but never remove it.

Contributing

Contributions are welcome! Feel free to open issues or submit pull requests on the GitHub repository.


📄 License

This project is licensed under the MIT License. See the LICENSE file for more details.


🔗 Project link

https://github.com/joseRibamar21/rhyla_documentation