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

@arc-core-components/feature_global-story-card

v0.2.4-beta.0

Published

Arc Core Component representing a flexible Story Card feature.

Downloads

90

Readme

Feature: Story Card

What does this do?

When used in a Fusion Project, this Core Component can be used to render a series of elements (Overline, Headline*, Deck, Image*) associated with a piece of content.

Commonly used in Section fronts and Homepages, though can also be used for rail or "widget" type features (Authors Feed, Recirc Well, etc.), or even additional page types, ex: Search Results.

Which elements to be displayed, as well as in what order, are explicitly semantic.

Enables quick view toggling through a single click, rather than numerous show/hide, left/right, above/below Custom Field options, as with a traditional "Flex Feature".

*-Incorporates element_headline and element_image Core Components

How do I use it?

Take a look in the src folder to see a suggested implementation in index.mdx

List of all possible props:

  import StoryCard from '@arc-core-components/feature_global-story-card'

  <StoryCard
    data={PropTypes.object},
    deckClasses={PropTypes.string},
    deckText={PropTypes.string},
    classes={PropTypes.string},
    customFields={PropTypes.shape({
      view={PropTypes.string}
    })},
    customViews={PropTypes.array},
    headlineClasses={PropTypes.string},
    headlineLevel={PropTypes.number},
    headlineText={PropTypes.string},
    imageClasses={PropTypes.string},
    imageHeight={PropTypes.number},
    imageWidth={PropTypes.number},
    indexedComponents={PropTypes.shape({})},
    pbData={PropTypes.shape({
      isAdmin={PropTypes.bool}
    })},
    overlineClasses={PropTypes.string},
    overlineText={PropTypes.string},
    replacementComponents={PropTypes.shape({})},
    subdheadlineClasses={PropTypes.string},
    subheadlineLevel={PropTypes.number},
    subheadlineText={PropTypes.string},
    view={PropTypes.string},
    url={PropTypes.string}
};

Data Defaults

If no data values are passed in for Deck, Headline, Image, Overline or url, fallbacks point to the following ANS values:

deckText = {data.description.basic};
headlineText = {data.headlines.basic};
imageHeight = {data.promo_items.basic.height}
imageWidth = {data.promo_items.basic.width}
overlineText = {data.taxonomy.primary_section.name}
url = {data.canonical_url}

How can I view what's in there quickly?

Run npm i && npm run docz:dev after cloning to see what is within.

Testing & Linting

We are using Jest and XO for testing and linting.

We are using Husky to run a pre-push hook, preventing un-linted or code that fails tests from making it into the repo.

To test: npm test

To lint: npm run lint - This will also fix any simple linter errors automatically.

To push without testing or linting: git push --no-verify - This can often be helpful if you just need to push a branch for demonstration purposes or for help.