51 |
52 | ## Installation
53 |
54 | 1. Install a [base16 builder](https://github.com/chriskempson/base16#builder-repositories). I like [pybase16](https://github.com/InspectorMustache/base16-builder-python), so this is what we're going to use in these instructions.
55 | 2. Make a folder to hold all the builder's files. For example: `~/base16`.
56 | 3. In that folder, run `pybase16 update`. This will download all of the official base16 [schemes](https://github.com/chriskempson/base16#scheme-repositories) and [templates](https://github.com/chriskempson/base16#template-repositories).
57 | 4. Now that all of the official [schemes](https://github.com/chriskempson/base16#scheme-repositories) and [templates](https://github.com/chriskempson/base16#template-repositories) have been downloaded, run `pybase16 build -s shades-of-purple`.
58 | 5. There will now be an `output` folder with all of the generated themes for various applications.
59 |
60 | Alternatively, if you don't want to mess with the builders, I went ahead and generated all the output themes and sent them to another repository [here](https://github.com/demartini/base16-shades-of-purple-exported-themes).
61 |
62 | ## Roadmap
63 |
64 | See the [open issues](https://github.com/demartini/base16-shades-of-purple/issues) for a list of proposed features (and known issues).
65 |
66 | ## Contributing
67 |
68 | If you are interested in helping contribute, please take a look at our [Contributing](CONTRIBUTING.md) guide.
69 |
70 | ### Contributors
71 |
72 |
73 |
74 |
75 |
76 | ## Inspired By
77 |
78 | - The amazing VSCode theme [Shades of Purple](https://github.com/ahmadawais/shades-of-purple-vscode) by [Ahmad Awais](https://github.com/ahmadawais).
79 |
80 | ## Thanks To
81 |
82 | - [Chris Kempson](https://github.com/chriskempson/base16) for the logo.
83 | - [Alex Meyer](https://github.com/reyemxela/base16-helios-scheme) for the installation instructions.
84 |
85 | ## Changelog
86 |
87 | See [Changelog](CHANGELOG.md) for a human-readable history of changes.
88 |
89 | ## License
90 |
91 | Distributed under the MIT License. See [LICENSE](LICENSE) for more information.
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # File created using '.gitignore Generator' for Visual Studio Code: https://bit.ly/vscode-gig
2 |
3 | # Created by https://www.toptal.com/developers/gitignore/api/windows,visualstudiocode,node,macos,linux
4 | # Edit at https://www.toptal.com/developers/gitignore?templates=windows,visualstudiocode,node,macos,linux
5 |
6 | ### Linux ###
7 | *~
8 |
9 | # temporary files which can be created if a process still has a handle open of a deleted file
10 | .fuse_hidden*
11 |
12 | # KDE directory preferences
13 | .directory
14 |
15 | # Linux trash folder which might appear on any partition or disk
16 | .Trash-*
17 |
18 | # .nfs files are created when an open file is removed but is still being accessed
19 | .nfs*
20 |
21 | ### macOS ###
22 | # General
23 | .DS_Store
24 | .AppleDouble
25 | .LSOverride
26 |
27 | # Icon must end with two \r
28 | Icon
29 |
30 | # Thumbnails
31 | ._*
32 |
33 | # Files that might appear in the root of a volume
34 | .DocumentRevisions-V100
35 | .fseventsd
36 | .Spotlight-V100
37 | .TemporaryItems
38 | .Trashes
39 | .VolumeIcon.icns
40 | .com.apple.timemachine.donotpresent
41 |
42 | # Directories potentially created on remote AFP share
43 | .AppleDB
44 | .AppleDesktop
45 | Network Trash Folder
46 | Temporary Items
47 | .apdisk
48 |
49 | ### Node ###
50 | # Logs
51 | logs
52 | *.log
53 | npm-debug.log*
54 | yarn-debug.log*
55 | yarn-error.log*
56 | lerna-debug.log*
57 |
58 | # Diagnostic reports (https://nodejs.org/api/report.html)
59 | report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
60 |
61 | # Runtime data
62 | pids
63 | *.pid
64 | *.seed
65 | *.pid.lock
66 |
67 | # Directory for instrumented libs generated by jscoverage/JSCover
68 | lib-cov
69 |
70 | # Coverage directory used by tools like istanbul
71 | coverage
72 | *.lcov
73 |
74 | # nyc test coverage
75 | .nyc_output
76 |
77 | # Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
78 | .grunt
79 |
80 | # Bower dependency directory (https://bower.io/)
81 | bower_components
82 |
83 | # node-waf configuration
84 | .lock-wscript
85 |
86 | # Compiled binary addons (https://nodejs.org/api/addons.html)
87 | build/Release
88 |
89 | # Dependency directories
90 | node_modules/
91 | jspm_packages/
92 |
93 | # TypeScript v1 declaration files
94 | typings/
95 |
96 | # TypeScript cache
97 | *.tsbuildinfo
98 |
99 | # Optional npm cache directory
100 | .npm
101 |
102 | # Optional eslint cache
103 | .eslintcache
104 |
105 | # Microbundle cache
106 | .rpt2_cache/
107 | .rts2_cache_cjs/
108 | .rts2_cache_es/
109 | .rts2_cache_umd/
110 |
111 | # Optional REPL history
112 | .node_repl_history
113 |
114 | # Output of 'npm pack'
115 | *.tgz
116 |
117 | # Yarn Integrity file
118 | .yarn-integrity
119 |
120 | # dotenv environment variables file
121 | .env
122 | .env.test
123 |
124 | # parcel-bundler cache (https://parceljs.org/)
125 | .cache
126 |
127 | # Next.js build output
128 | .next
129 |
130 | # Nuxt.js build / generate output
131 | .nuxt
132 | dist
133 |
134 | # Gatsby files
135 | .cache/
136 | # Comment in the public line in if your project uses Gatsby and not Next.js
137 | # https://nextjs.org/blog/next-9-1#public-directory-support
138 | # public
139 |
140 | # vuepress build output
141 | .vuepress/dist
142 |
143 | # Serverless directories
144 | .serverless/
145 |
146 | # FuseBox cache
147 | .fusebox/
148 |
149 | # DynamoDB Local files
150 | .dynamodb/
151 |
152 | # TernJS port file
153 | .tern-port
154 |
155 | # Stores VSCode versions used for testing VSCode extensions
156 | .vscode-test
157 |
158 | ### VisualStudioCode ###
159 | .vscode/*
160 | !.vscode/settings.json
161 | !.vscode/tasks.json
162 | !.vscode/launch.json
163 | !.vscode/extensions.json
164 | *.code-workspace
165 |
166 | ### VisualStudioCode Patch ###
167 | # Ignore all local history of files
168 | .history
169 |
170 | ### Windows ###
171 | # Windows thumbnail cache files
172 | Thumbs.db
173 | Thumbs.db:encryptable
174 | ehthumbs.db
175 | ehthumbs_vista.db
176 |
177 | # Dump file
178 | *.stackdump
179 |
180 | # Folder config file
181 | [Dd]esktop.ini
182 |
183 | # Recycle Bin used on file shares
184 | $RECYCLE.BIN/
185 |
186 | # Windows Installer files
187 | *.cab
188 | *.msi
189 | *.msix
190 | *.msm
191 | *.msp
192 |
193 | # Windows shortcuts
194 | *.lnk
195 |
196 | # End of https://www.toptal.com/developers/gitignore/api/windows,visualstudiocode,node,macos,linux
197 |
198 | # Custom rules (everything added below won't be overriden by 'Generate .gitignore File' if you use 'Update' option)
199 |
200 | src/shades-of-purple/Cached Theme.pak
201 | src/shades-of-purple.zip
202 | src/shades-of-purple.pem
203 | src/shades-of-purple.crx
204 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 |
2 | # Contributor Covenant Code of Conduct
3 |
4 | ## Our Pledge
5 |
6 | We as members, contributors, and leaders pledge to make participation in our
7 | community a harassment-free experience for everyone, regardless of age, body
8 | size, visible or invisible disability, ethnicity, sex characteristics, gender
9 | identity and expression, level of experience, education, socio-economic status,
10 | nationality, personal appearance, race, religion, or sexual identity
11 | and orientation.
12 |
13 | We pledge to act and interact in ways that contribute to an open, welcoming,
14 | diverse, inclusive, and healthy community.
15 |
16 | ## Our Standards
17 |
18 | Examples of behavior that contributes to a positive environment for our
19 | community include:
20 |
21 | * Demonstrating empathy and kindness toward other people
22 | * Being respectful of differing opinions, viewpoints, and experiences
23 | * Giving and gracefully accepting constructive feedback
24 | * Accepting responsibility and apologizing to those affected by our mistakes,
25 | and learning from the experience
26 | * Focusing on what is best not just for us as individuals, but for the
27 | overall community
28 |
29 | Examples of unacceptable behavior include:
30 |
31 | * The use of sexualized language or imagery, and sexual attention or
32 | advances of any kind
33 | * Trolling, insulting or derogatory comments, and personal or political attacks
34 | * Public or private harassment
35 | * Publishing others' private information, such as a physical or email
36 | address, without their explicit permission
37 | * Other conduct which could reasonably be considered inappropriate in a
38 | professional setting
39 |
40 | ## Enforcement Responsibilities
41 |
42 | Community leaders are responsible for clarifying and enforcing our standards of
43 | acceptable behavior and will take appropriate and fair corrective action in
44 | response to any behavior that they deem inappropriate, threatening, offensive,
45 | or harmful.
46 |
47 | Community leaders have the right and responsibility to remove, edit, or reject
48 | comments, commits, code, wiki edits, issues, and other contributions that are
49 | not aligned to this Code of Conduct, and will communicate reasons for moderation
50 | decisions when appropriate.
51 |
52 | ## Scope
53 |
54 | This Code of Conduct applies within all community spaces, and also applies when
55 | an individual is officially representing the community in public spaces.
56 | Examples of representing our community include using an official e-mail address,
57 | posting via an official social media account, or acting as an appointed
58 | representative at an online or offline event.
59 |
60 | ## Enforcement
61 |
62 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
63 | reported to the community leaders responsible for enforcement at
64 | iolardemartini@gmail.com.
65 | All complaints will be reviewed and investigated promptly and fairly.
66 |
67 | All community leaders are obligated to respect the privacy and security of the
68 | reporter of any incident.
69 |
70 | ## Enforcement Guidelines
71 |
72 | Community leaders will follow these Community Impact Guidelines in determining
73 | the consequences for any action they deem in violation of this Code of Conduct:
74 |
75 | ### 1. Correction
76 |
77 | **Community Impact**: Use of inappropriate language or other behavior deemed
78 | unprofessional or unwelcome in the community.
79 |
80 | **Consequence**: A private, written warning from community leaders, providing
81 | clarity around the nature of the violation and an explanation of why the
82 | behavior was inappropriate. A public apology may be requested.
83 |
84 | ### 2. Warning
85 |
86 | **Community Impact**: A violation through a single incident or series
87 | of actions.
88 |
89 | **Consequence**: A warning with consequences for continued behavior. No
90 | interaction with the people involved, including unsolicited interaction with
91 | those enforcing the Code of Conduct, for a specified period of time. This
92 | includes avoiding interactions in community spaces as well as external channels
93 | like social media. Violating these terms may lead to a temporary or
94 | permanent ban.
95 |
96 | ### 3. Temporary Ban
97 |
98 | **Community Impact**: A serious violation of community standards, including
99 | sustained inappropriate behavior.
100 |
101 | **Consequence**: A temporary ban from any sort of interaction or public
102 | communication with the community for a specified period of time. No public or
103 | private interaction with the people involved, including unsolicited interaction
104 | with those enforcing the Code of Conduct, is allowed during this period.
105 | Violating these terms may lead to a permanent ban.
106 |
107 | ### 4. Permanent Ban
108 |
109 | **Community Impact**: Demonstrating a pattern of violation of community
110 | standards, including sustained inappropriate behavior, harassment of an
111 | individual, or aggression toward or disparagement of classes of individuals.
112 |
113 | **Consequence**: A permanent ban from any sort of public interaction within
114 | the community.
115 |
116 | ## Attribution
117 |
118 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119 | version 2.0, available at
120 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
121 |
122 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
123 | enforcement ladder](https://github.com/mozilla/diversity).
124 |
125 | [homepage]: https://www.contributor-covenant.org
126 |
127 | For answers to common questions about this code of conduct, see the FAQ at
128 | https://www.contributor-covenant.org/faq. Translations are available at
129 | https://www.contributor-covenant.org/translations.
130 |
131 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing
2 |
3 | First of all, thanks for thinking of contributing to this project! 👏
4 |
5 | Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are **greatly appreciated**.
6 |
7 | As a contributor, here are the guidelines we would like you to follow:
8 |
9 | ## Table of Contents
10 |
11 | - [Table of Contents](#table-of-contents)
12 | - [Code of Conduct](#code-of-conduct)
13 | - [How can I contribute?](#how-can-i-contribute)
14 | - [Give Feedback on Issues](#give-feedback-on-issues)
15 | - [Fix bugs and implement features](#fix-bugs-and-implement-features)
16 | - [Using the issue tracker](#using-the-issue-tracker)
17 | - [Bug report](#bug-report)
18 | - [Feature request](#feature-request)
19 | - [Submitting a Pull Request](#submitting-a-pull-request)
20 | - [Style Guides](#style-guides)
21 | - [Commit Messages](#commit-messages)
22 |
23 | We also recommend that you read [How to Contribute to Open Source](https://opensource.guide/how-to-contribute).
24 |
25 | ## Code of Conduct
26 |
27 | Please note that this project have a [code of conduct](CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
28 |
29 | ## How can I contribute?
30 |
31 | ### Give Feedback on Issues
32 |
33 | Some issues are created without information requested in the [Bug report guideline](#bug-report). Help make them easier to resolve by adding any relevant information.
34 |
35 | Issues with the **`enhancement`** label are meant to discuss the implementation of new features. Participating in the discussion is a good opportunity to get involved and influence our future direction.
36 |
37 | ### Fix bugs and implement features
38 |
39 | Confirmed bugs and ready-to-implement features are marked with the **`help wanted`** label. Post a comment on an issue to indicate you would like to work on it and to request help from the **maintainers** and the **community**.
40 |
41 | ## Using the issue tracker
42 |
43 | The issue tracker is the channel for [bug reports](#bug-report), [features requests](#feature-request) and [submitting pull requests](#submitting-a-pull-request) only.
44 |
45 | Before opening an issue or a Pull Request, please use the **GitHub issue search** to make sure the bug or feature request hasn't been already reported or fixed.
46 |
47 | ### Bug report
48 |
49 | A good bug report shouldn't leave others needing to chase you for more information. Please try to be as detailed as possible in your report and fill the information requested in the **Bug report template**.
50 |
51 | ### Feature request
52 |
53 | Feature requests are welcome, but take a moment to find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible and fill the information requested in the **Feature request template**.
54 |
55 | ## Submitting a Pull Request
56 |
57 | Good pull requests, whether patches, improvements, or new features, are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.
58 |
59 | **Please ask first** before embarking on any significant pull requests (e.g. implementing features, refactoring code), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project.
60 |
61 | If you have never created a pull request before, welcome 🎉 😄. [Here is a great tutorial](https://opensource.guide/how-to-contribute/#opening-a-pull-request) on how to send one. 😃
62 |
63 | This is our preferred process for opening a PR on GitHub:
64 |
65 | 1. Fork this repository
66 | 2. Create your feature branch (`git checkout -b feature/AmazingFeature`)
67 | 3. Commit your changes (`git commit -m 'Add some AmazingFeature'`)
68 | 4. Push to the branch (`git push origin feature/AmazingFeature`)
69 | 5. Open a pull request
70 |
71 | ## Style Guides
72 |
73 | ### Commit Messages
74 |
75 | This project uses the [conventional commit](https://www.conventionalcommits.org) for your commit messages. This format is used to generate changelogs and ensures consistency and better filtering.
76 |
77 | Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes a **type**, a **scope** and a **subject**:
78 |
79 | ```commit
80 | ():
81 |
82 |
83 |
84 |
4 |
5 | 
50 | 
12 | 
15 | 
18 | 
21 | 
24 |