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

industries-integrations

v0.6.102-amfup

Published

This is a sample template repo for Documentation teams

Downloads

4

Readme

Example Repository: Sample Content Respository

This is a sample repo for our testing (within SF/CCX teams)

Note

This is still work in progress.

Folder structure

TODO

How to build it locally

On the terminal, navigate to the doc-set repo (e.g., knowledge-center)

Till we are on mono-repo

- go to the parent folder (doc-framework-monorepo)

- To build content (to create htmls)
    - salesforcedocs build packages/knowledge-center
- To validate content (to check whether the .md files are proper + linting + broken link checks)
    - salesforcedocs validate packages/knowledge-center
- To run a local server (development mode - hot reload feature)
    - salesforcedocs watch packages/knowledge-center

- To run as production server (Less logs + no hot reload + cached files)
    - salesforcedocs start packages/knowledge-center

To preview your documentation site locally, goto http://localhost:3000

Utilize Automated Remote Builds and Preview Apps

When you send a pull request to any of the protected branches, a remote build check gets triggered automaticaly. If the build for the content in your branch is successful, you will be notified of a preview enviornment on the GitHub PR page.