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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@elastic/docsmobile

v2.0.3-rc.1

Published

The engine that makes your docs go!

Downloads

3,150

Readme

Docsmobile 🚌

Docsmobile is a documentation system and syntax shell that is built upon NextJS, EUI and MDX. It can be used either with local documentation within the /docs folder, or you can consume MDX pages from separate repos.

Some things have changed recently so let's chat!

How to work with the system now

Docsmobile is the engine for our documentation. An engine can't do much without being hooked up to something that makes it go--so for now I've been doing most of my docsmobile development using doc-site as my test site. You'll see info on how to get started in the root README. For the most part, you'll do two things:

  1. Initialize with yarn init-docs which runs docsmobile init --symlink under the hood. This allows docsmobile to be set up with symlinks to docsmobile/template so your changes will immediately go through.
  2. Then develop with yarn dev (which runs docsmobile dev). Note that if it isn't a component change (e.g. style or text change) you'll likely have to refresh the page once your code is done compiling.

Deploying the docs with CI

To understand how the CI picks up content from outside repos, as well as how to manually deploy the docs, please check https://docs.elastic.dev/docs/ci

docsmobile.config.js

Bare minimum, docsmobile needs a content.js with nav and sources config to run. See the docsmobile.config.js in doc-site for a living example. While the search engine config is optional, not providing it will remove all search related UI.

Navigation

Even if you add more docs to your sources key of content.js/content-dev.js, you won't see the pages appear on the home page or in the side nav without either including the new pages into an existing nav or adding a new navigation unit. If a source has already relocated its .docnav.json files into it, then they'll compile as expected.

Sourcing docs

You'll have two source configs--content.js is always used in the production build and mostly shouldn't be touched unless you're intentionally adding a new source. For local development we always use content-dev.js. You can read more on the syntax used in these json blobs in Docs Setup: Add MDX content sources.