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

@axdspub/landing-page-components

v0.7.18

Published

Building blocks for landing pages

Downloads

15

Readme

landing-page-components

Building blocks for landing pages

Installation

npm install @axdspub/landing-page-components

Configuration

The StaticMap component requires a Mapbox access token. For Storybook use, you'll need to export a STORYBOOK_MAPBOX_TOKEN environment variable. Create an .envrc (for use with direnv), or export that env var into whatever shell you run Storybook from.

Usage

These components are styled with Tailwind CSS classes; therefore it is a peer dependency of this package. These components also rely on a custom color names which must be defined in your project.

Configuring Next.js

Follow these steps to configure Tailwind if you are adding these components to a Next.js app.

Install peer dependencies

npm install -D tailwindcss@latest postcss@latest autoprefixer@latest

Create configuration files

npx tailwindcss init -p

Update configuration

Ensure that your pages, components, and this package's components are checked when Tailwind purges unused classes.

// tailwind.config.js
module.exports = {
    // ...
    purge: [
        './pages/**/*.{js,ts,jsx,tsx}',
        './components/**/*.{js,ts,jsx,tsx}',
        './node_modules/@axdspub/landing-page-components/**/*.{js,ts,jsx,tsx}',
    ],
    // ...
};

Add primary and secondary colors, including lighter and darker varieties.

// tailwind.config.js
module.exports = {
    // ...
    theme: {
        extend: {
            colors: {
                primary: {
                    lighter: '#8c4fd1',
                    DEFAULT: '#7138b2',
                    darker: '#553197',
                },
                secondary: {
                    lighter: '#63B3ED',
                    DEFAULT: '#4299E1',
                    darker: '#3182CE',
                },
            },
        },
    },
    // ...
};

Some component support the display of Markdown content. If those components are being used and you want the generated HTML to be styled by default, ensure you have Tailwind's typography plugin enabled:

// tailwind.config.js
module.exports = {
  theme: {
    // ...
  },
  plugins: [
    require('@tailwindcss/typography'),
    // ...
  ],
}

Development

See DEVELOPMENT.md