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

shell-css

v1.1.0

Published

Retro CSS framework in the style of classic operating systems

Downloads

26

Readme

Shell.css

Join us on Slack!

Documentation

npm package

Installation

To use in your own project, the quickest way is to install through npm:

npm i shell-css

Prerequisites

Bootstrap's grid is recommended, but not required. The documentation site currently uses Bootstrap 5's grid only.

npm i bootstrap

<link rel="stylesheet" href="node_modules/bootstrap/dist/css/bootstrap-grid.min.css" />

Usage

<link rel="stylesheet" href="node_modules/shell-css/dist/shell.css" />

Icons and images are embedded, fonts are included in the dist folder and imported.

The documentation site has examples of possible uses; viewing its source is the easiest way to get up and running.

Building from Source

Parcel is used to compile the SCSS. Clone the repository and npm install, then npm run build.

The src folder has styles, icons, etc. while dist contains the build output.

Viewing the documentation site locally

The documentation site is located in doc and links a level up to the compiled CSS output in the dist folder.

npm run watch will start up a server as well as watch the SCSS and let you view all changes to either documentation or the project's source. You'll need to do this to get everything running, as it builds an un-minified copy of Shell.css and copies it into the documentation site's directory.

Resources Used

Thank you to the authors of these resources:

License

The Windows 3.1 name and trademark are property of Microsoft. This project's source code is provided under the MIT license.

Contributing

Bug reports, feature requests and PRs are welcome, however I may not merge all PRs into this repo. If you want your PR merged into the repo it's probably best to report an issue first for tracking and to nail down the requirements. Of course, being open source, you can always fork or spin the project off into your own new project too!

A note about artwork

I've made icons for this project in Aseprite by looking at screenshots and doing my best to re-draw everything from a reference, rather than ripping assets directly off a disk image. Any new icons or art should try to follow this spirit to avoid issues with copyrights.

Roadmap

I don't have a timeline for implementing these features, but here are some ideas I've got for improving the project:

  • Styles from different eras and operating systems. I'm envisioning a future release where you can wrap your entire site in a class like you already can with .theme-* and you can switch skins from Windows to Macintosh or Linux.
  • Perfect compatibility with CSS resets, like the one that Bootstrap uses when you include the full Bootstrap CSS.
  • An optional library of Web Components, either framework-independent or specialized for popular frameworks like Svelte, Aurelia, Vue, React, etc.
  • A demo site containing a game to showcase more advanced uses of the framework than the documentation site has.