liuliangsir / periodic-table-of-the-html5-elements Goto Github PK

View Code? Open in Web Editor NEW

7.0 2.0 1.0 2.01 MB

A periodic table of the HTML5 Elements created by css gird layout

Home Page: https://html5.tool.webfrontend.dev

License: MIT License

JavaScript 25.19% CSS 14.69% Pug 60.11%

html5-elements grid-layout

periodic-table-of-the-html5-elements's Introduction

Periodic Table Of The HTML5 Elements

This is a periodic table for the HTML5 elements. Inspired by another demos, Periodic Table of Elements - HTML/CSS and Periodic Table of the HTML5 Elements.

Getting Started

These instructions below will get you a copy of the project up and running on your local machine for development. See deployment section for more details about how to deploy the project on Github Pages or your own deploy environment like Ubuntu.

Prerequisites

Make sure you have installed all of the following prerequisites on your development machine:

Git - Download & Install Git. OSX and Linux machines typically have this already installed.
Node.js - Download & Install Node.js and the npm package manager. If you encounter any problems, you can also use this GitHub Gist to install Node.js.
nvm - Download & Install nvm. You might need to install an alternative tool(nvm-windows/nodist) if you are a Windows user.

Installing

Clone this repository to your local machine with https or ssh
Install npm packages

npm ci

Deployment

It may be the most convenient for users who have forked the github repository and would like to deploy the project on Github Pages, since that github repository takes full advantage of Github Pages and Travis CI. So you only need to do one thing that is to push the file changes in local master branch to remote repository.

Note: no github actions have been used in that github repository.

Built With

webpack - The most popular module bundler used

Contributing

To get started...

Step 1

Option 1
- Fork this repository!
Option 2
- Clone this repository to your local machine with https or ssh

Step 2

Feel free to hack away

Step 3

Create a new pull request

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

Authors

流浪大法师 - liuliangsir

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

License

This project is licensed under the MIT License - see the LICENSE file for details.

periodic-table-of-the-html5-elements's People

Contributors

Stargazers

Watchers

Forkers

relliv

periodic-table-of-the-html5-elements's Issues

An in-range update of eslint-plugin-import is breaking the build 🚨

The devDependency eslint-plugin-import was updated from `2.16.0` to `2.17.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 61 commits.

0499050 bump to v2.17.0
f479635 [webpack] v0.11.1
8a4226d Merge pull request #1320 from bradzacher/export-ts-namespaces
988e12b fix(export): Support typescript namespaces
70c3679 [docs] make rule names consistent
6ab25ea [Tests] skip a TS test in eslint < 4
405900e [Tests] fix tests from #1319
2098797 [fix] export: false positives for typescript type + value export
70a59fe [fix] Fix overwriting of dynamic import() CallExpression
e4850df [ExportMap] fix condition for checking if block comment
918567d [fix] namespace: add check for null ExportMap
2d21c4c Merge pull request #1297 from echenley/ech/fix-isBuiltIn-local-aliases
0ff1c83 [dev deps] lock typescript to ~, since it doesn’t follow semver
40bf40a [*] [deps] update resolve
28dd614 Merge pull request #1304 from bradennapier/feature/typescript-export-type

There are 61 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

CircleCI
Travis CI
Buildkite
CodeShip
Azure Pipelines
TeamCity
Buddy
AppVeyor
But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.