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

at-article

v1.0.8

Published

Web components and layout for blog and academic articles

Downloads

14

Readme

Table of Contents

Introduction

npm npm Conventional Commits license

Features

  • 12 web-components for web native article writing
  • usable in any web environment
  • clean and flat design

Install

Use one of this solution to "install" the at-article component in your project.

Script tag

  • Put a script tag similar to this <script src='https://unpkg.com/at-article@latest/dist/at-article.js'></script> in the head of your index.html
  • Then you can use the element anywhere in your template, JSX, html, etc.

Node Modules

  • Run npm install at-article --save
  • Put a script tag similar to this <script src='node_modules/at-article/dist/at-article.js'></script> in the head of your index.html
  • Then you can use the element anywhere in your template, JSX, html, etc.

In a stencil-starter app

  • Run npm install at-article --save
  • Add an import to the npm packages import my-component;
  • Then you can use the element anywhere in your template, JSX, html, etc.

Usage

Check the documentation for more informations : Documentation

Example with the at-block component

The block element allows to highlight content with a contrasted graphic aspect with the rest of the article.

<at-block caption="true" heading="Heading example" type="info">Lorem ispum</at-block>

Property | Default | Explanations --- | --- | --- caption | false | If true, display a numbered caption heading | | Display a heading type | default | The values can be default, info, example, warning, definition or fact

Build with

  • Stencil is a compiler for building fast web apps using Web Components.

Building

git clone https://github.com/ionic-team/stencil-component-starter.git my-component
cd my-component
git remote rm origin

and run:

npm install
npm start

To watch for file changes during develop, run:

npm run dev

To build the component for production, run:

npm run build

To run the unit tests for the components, run:

npm test

Need help? Check out our docs here.

Contributing

We’re really happy to accept contributions from the community, that’s the main reason why we open-sourced it! There are many ways to contribute, even if you’re not a technical person.

  1. Fork it (https://github.com/michaelravedoni/at-article/fork)
  2. Create your feature branch (git checkout -b feature/fooBar)
  3. Commit your changes (git commit -am 'Add some fooBar')
  4. Push to the branch (git push origin feature/fooBar)
  5. Create a new Pull Request

Release History

You will find the releases history in the release section. For more detail, you can check the changelog.md file.

Roadmap

  • citeproc-js implementation
  • themes implementation
  • pdf export

Authors and acknowledgment

See also the list of contributors who participated in this project.

License

MIT License