diff --git a/.prettierrc b/.prettierrc
index d8ffdc2f..cf631165 100644
--- a/.prettierrc
+++ b/.prettierrc
@@ -1,11 +1,11 @@
{
- "printWidth": 80,
+ "printWidth": 180,
"tabWidth": 4,
"useTabs": false,
"semi": true,
"singleQuote": false,
"quoteProps": "as-needed",
- "proseWrap": "always",
+ "proseWrap": "preserve",
"htmlWhitespaceSensitivity": "css",
"endOfLine": "auto",
"bracketSameLine": true
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index e01f0fe1..e08002e3 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -2,17 +2,11 @@
## Our Pledge
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of
-experience, nationality, personal appearance, race, religion, or sexual identity
-and orientation.
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
## Our Standards
-Examples of behavior that contributes to creating a positive environment
-include:
+Examples of behavior that contributes to creating a positive environment include:
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
@@ -22,53 +16,31 @@ include:
Examples of unacceptable behavior by participants include:
-- The use of sexualized language or imagery and unwelcome sexual attention or
- advances
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
-- Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
- professional setting
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
## Our Responsibilities
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-Project maintainers have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, or to ban temporarily or permanently any
-contributor for other behaviors that they deem inappropriate, threatening,
-offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
## Scope
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
## Enforcement
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at tryzencss@gmail.com. The project team
-will review and investigate all complaints, and will respond in a way that it
-deems appropriate to the circumstances. The project team is obligated to
-maintain confidentiality with regard to the reporter of an incident. Further
-details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at tryzencss@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
## Attribution
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/
diff --git a/README.md b/README.md
index 0c07ff19..1dfaf8fa 100644
--- a/README.md
+++ b/README.md
@@ -1,14 +1,11 @@
# zencss
-An open-source, website authoring and design toolkit that helps you build,
-style, and debug websites. Current Release is v2.0.2-beta
+An open-source, website authoring and design toolkit that helps you build, style, and debug websites. Current Release is v2.0.2-beta
### Pre-Launch Installation
-- Download or clone the latest files
- [from the zencss repository](https://github.com/zen-solutions/zencss).
-- Follow the instructions in the
- [zenCSS setup documentation](https://zencss.com/docs/help-desk/installation.html).
+- Download or clone the latest files [from the zencss repository](https://github.com/zen-solutions/zencss).
+- Follow the instructions in the [zenCSS setup documentation](https://zencss.com/docs/help-desk/installation.html).
## Features
@@ -23,54 +20,30 @@ style, and debug websites. Current Release is v2.0.2-beta
### Dependencies
-For the core framework, none - just pure CSS and Vanilla JavaScript. If you want
-to work with our SASS files or JavaScript modules, there are a few dependencies.
-We provide
-[instructions for that here](https://zencss.com/docs/help-desk/installation-source.html).
+For the core framework, none - just pure CSS and Vanilla JavaScript. If you want to work with our SASS files or JavaScript modules, there are a few dependencies. We provide [instructions for that here](https://zencss.com/docs/help-desk/installation-source.html).
### Best Practices for Customization
-When working with zenCSS, we recommend using override files instead of directly
-modifying the core files. This approach ensures that your customizations are
-preserved when updating to newer versions of zenCSS.
+When working with zenCSS, we recommend using override files instead of directly modifying the core files. This approach ensures that your customizations are preserved when updating to newer versions of zenCSS.
-1. **For CSS:** Create separate CSS files for your custom styles and link them
- after the core zenCSS files in your HTML. This will allow your styles to take
- precedence.
+1. **For CSS:** Create separate CSS files for your custom styles and link them after the core zenCSS files in your HTML. This will allow your styles to take precedence.
-2. **For JavaScript:** If you need to extend or modify the JavaScript
- functionality, create separate JS modules and import the core zenCSS modules
- as dependencies. This way, you can enhance or override specific
- functionalities without altering the original source.
+2. **For JavaScript:** If you need to extend or modify the JavaScript functionality, create separate JS modules and import the core zenCSS modules as dependencies. This way, you can enhance or override specific functionalities without altering the original source.
# Contributing
-Help us make zenCSS better for everyone, any contribution will be considered.
-Use the issue tracker for bug reports, features requests and submitting pull
-requests.
+Help us make zenCSS better for everyone, any contribution will be considered. Use the issue tracker for bug reports, features requests and submitting pull requests.
# Bug Reports
-Please try to be as detailed as possible in your report. What is your
-environment? What steps will reproduce the issue? What browser(s) and OS
-experience the problem? What would you expect to be the outcome? All these
-details will help us fix any potential bugs. Please reproduce any issues
-[here](https://codepen.io/ScrmSe4L6/pen/ExrQRdE) and include with your bug
-report.
+Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What browser(s) and OS experience the problem? What would you expect to be the outcome? All these details will help us fix any potential bugs. Please reproduce any issues [here](https://codepen.io/ScrmSe4L6/pen/ExrQRdE) and include with your bug report.
# Feature Requests
-Before opening a feature request, please 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.
+Before opening a feature request, please 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.
# Pull Requests
-Please ask first before embarking on any significant pull request (e.g.
-implementing features, re-factoring code, porting to a different language),
-otherwise you risk spending a lot of time working on something that the
-project's developers might not want to merge into the project. When contributing
-code to this project always ask yourself these questions.
+Please ask first before embarking on any significant pull request (e.g. implementing features, re-factoring code, porting to a different language), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project. When contributing code to this project always ask yourself these questions.
Is it essential? Will it add value? Is this change necessary?
diff --git a/dist/hello-world/index.html b/dist/hello-world/index.html
index 3264e79d..93d23f83 100644
--- a/dist/hello-world/index.html
+++ b/dist/hello-world/index.html
@@ -8,12 +8,10 @@
-
-
@@ -24,10 +22,7 @@
+