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

confluence-static-site-builder

v1.0.0-m12

Published

confluence static site builder

Downloads

16

Readme

confluence-static-site

Quality Gate Status Known Vulnerabilities npm version

install it

  • with npm
npm install confluence-static-site-builder -g
  • [ ] with homebrew

configure your site

confsite env

it creates a .env file with the following properties

  • CONFLUENCE_SITE_NAME : the Confluence cloud instance you want to generate a site from
  • CONFLUENCE_USERNAME : the username to use to consume Confluence APIs
  • CONFLUENCE_API_TOKEN : the user personal access token to consume Confluence APIs
  • TARGET_SITE : the domain name of where your generated site will be hosted
  • TWITTER_SITE : the twitter handle for seo purposes
  • GOOGLE_ANALYTICS_TRACKING_ID: Google Analytics tracking id
confsite config

it creates a .confluence-static-site.json file with the following configuration

{
  "title": "confluence-static-site",
  "iconUrl": "",
  "name": "space name",
  "theme": {
    "name": "confluence-static-site",
    "backgroundColor": "rgb(0, 102, 68)",
    "highlightColor": "#FFFFFF"
  }
}

extract your site content

confsite extract <spaceKey>

build your site

confsite build <spaceKey>
confsite build <spaceKey> --serve # with webpack dev server
confsite build <spaceKey> --assets my-assets-folder # copy your assets to the site output assets (i.e. site logo ...)

everything in the output directory

Once your content is extracted and the site is built, you will have an output directory created in the root of your project folder with the following structure

- output
    - site
        - <spaceKey>
            - articles
                - <blog-title-1>
                - <blog-title-2>
                - ...
            - assets
                - avatars
                - emojis
            - attachments
            - notes
                - <page-title-1>
                - <page-title-2>
                - ...
            - object-resolver
    - templates

What you need to deploy is the output/site/<spaceKey>

deploy your site

  • [ ] with GitHub pages
  • [ ] with Google Firebase