Since several years, in the fusing beads community, we saw a bunch of Google Spreadsheet defining beads colors in color code formats. However these Sheets ofter lacks of updates or correctness.
This project aims to centralize, maintain and expose an exhaustive list of all beads colors references using GitHub.
Brands | Color Count | Style |
---|---|---|
Hama | 73 | Melty Bead |
Perler | 96 | Melty Bead |
Perler Mini | 41 | Melty Bead |
Perler Caps | 26 | Bead |
Nabbi | 30 | Melty Bead |
Artkal A-2.6MM | 145 | Melty Bead |
Artkal C-2.6MM | 157 | Melty Bead |
Artkal R-5MM | 89 | Melty Bead |
Artkal S-5MM | 199 | Melty Bead |
Yant | 119 | Melty Bead |
Diamond Dotz | 461 | Diamond Painting |
In order to prevent breaking change in the future, this repository is organized in several folders :
Folder | Description |
---|---|
/raw |
Very simple .csv for each brands, in the following format :[reference_code, name, rgb_r, rgb_g, rgb_b, contributor] Note: Contribution should be made on this folder, orders folders will be generated with Github Actions. |
/v1 |
[reference_code, name, rgb_r, rgb_g, rgb_b, rgb_hex, contributor] |
/v2 |
[reference_code, name, rgb_r, rgb_g, rgb_b, hsl_h, hsl_s, hsl_l, lab_l, lab_a, lab_b, contributor] |
/v3 |
[reference_code, name, symbol, rgb_r, rgb_g, rgb_b, hsl_h, hsl_s, hsl_l, lab_l, lab_a, lab_b, contributor] |
Simply create a PR applying modification under /raw
folder only.
If you are updating references, you should provide explanation about why your reference is more accurate than the current one.
Method | Usage |
---|---|
Browsing website | Beadscolors |
Static files |
Goal of automation are multiple :
- Maintain only
raw
folder, contains minimal data, only[ref, name, r, g, b, contributor]
- Enhance the
raw
folder by adding new fields to each color reference (eg:hex
,hsl
,lab
) - Generate bunch of format (eg:
csv
,json
,yaml
)
v1
folder is more a proof of concept of what it could be done in a later time.