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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@robinmordasiewicz/f5xc-docs-theme

v1.22.0

Published

F5 Distributed Cloud branded Starlight documentation theme

Readme

F5 XC Documentation Theme

Branding assets for all F5 XC documentation sites. Changes pushed here are picked up automatically on the next build of any content site.

What's in this repo

| Folder | Contents | What to edit | |--------|----------|--------------| | fonts/ | Custom web fonts (woff2) and font-face.css declarations | Replace font files or update font-face.css to change typefaces | | styles/ | custom.css -- colors, spacing, code blocks, Mermaid diagrams | Edit CSS variables and rules to change the look and feel | | assets/ | f5-logo.svg -- sidebar logo | Replace the SVG to update the logo across all sites | | components/ | Footer.astro -- custom footer with social links | Edit HTML/SVG to change footer links or icons |

How to make changes

  1. Edit the file you want to change (use the GitHub web editor or clone locally)
  2. Commit and push to main
  3. The next time any documentation site rebuilds, it will use your updated theme

No npm, no build tools, no technical setup required.

File reference

Fonts (fonts/)

  • font-face.css -- Declares which font files to load and at which weights
  • neusaNextProWide-*.woff2 -- Heading font (weights: 300, 400, 500, 700)
  • proximaNova-*.woff2 -- Body text font (weights: 400, 500, 600, 700)

To change a font: replace the .woff2 file with a new one (keep the same filename), or update font-face.css to point to a different file.

Styles (styles/custom.css)

Key CSS variables you can change:

:root {
  --sl-font: "proximaNova", ...;    /* Body font family */
  --sl-content-width: 60rem;         /* Main content area width */
  --sl-sidebar-width: 15rem;         /* Left sidebar width */
}

The file also controls:

  • Heading font family
  • Mermaid diagram container styling (border, shadow, background)
  • Code block appearance (rounded corners, terminal-style header)
  • Aside/callout box styling

Logo (assets/f5-logo.svg)

The SVG file displayed in the sidebar header. Replace it with any SVG file using the same filename.

Footer (components/Footer.astro)

Custom footer with social media links (Facebook, X, LinkedIn, Instagram, YouTube). Edit the HTML to change links, add new icons, or update styling.

Architecture

This repo is checked out at build time by the f5xc-docs-builder reusable workflow into a theme/ directory. The Astro config references these files as ./theme/fonts/..., ./theme/styles/..., etc.

Content repo push
  -> Builder workflow runs
     -> Checks out this theme repo into builder/theme/
     -> Astro build uses theme files
     -> Site deployed with your branding