[setup](web): base_files

Signed-off-by: Ralph Hightower <[email protected]>

Author: RalphHightower

CODEOWNERS

@@ -0,0 +1,5 @@
+# Repository Owner
+* @RalphHightower
+
+# Ruby Gems are owned by different developers/organizations 
+# _plugins/ @rubygems

CODE_OF_CONDUCT.md

@@ -1,3 +1,4 @@
+
 # Contributor Covenant Code of Conduct
 
 ## Our Pledge
@@ -6,8 +7,8 @@ We as members, contributors, and leaders pledge to make participation in our
 community a harassment-free experience for everyone, regardless of age, body
 size, visible or invisible disability, ethnicity, sex characteristics, gender
 identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
 
 We pledge to act and interact in ways that contribute to an open, welcoming,
 diverse, inclusive, and healthy community.
@@ -22,17 +23,17 @@ community include:
 * Giving and gracefully accepting constructive feedback
 * Accepting responsibility and apologizing to those affected by our mistakes,
   and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
 * Trolling, insulting or derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
 * Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
@@ -52,15 +53,15 @@ decisions when appropriate.
 
 This Code of Conduct applies within all community spaces, and also applies when
 an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
+Examples of representing our community include using an official email address,
 posting via an official social media account, or acting as an appointed
 representative at an online or offline event.
 
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-[email protected].
+<ralph.hightower+blog@gmail.com>.
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
@@ -82,15 +83,15 @@ behavior was inappropriate. A public apology may be requested.
 
 ### 2. Warning
 
-**Community Impact**: A violation through a single incident or series
-of actions.
+**Community Impact**: A violation through a single incident or series of
+actions.
 
 **Consequence**: A warning with consequences for continued behavior. No
 interaction with the people involved, including unsolicited interaction with
 those enforcing the Code of Conduct, for a specified period of time. This
 includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
 
 ### 3. Temporary Ban
 
@@ -106,23 +107,27 @@ Violating these terms may lead to a permanent ban.
 ### 4. Permanent Ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
+standards, including sustained inappropriate behavior, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
 
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
 
-[homepage]: https://www.contributor-covenant.org
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
 
 For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTORS.md

@@ -0,0 +1,17 @@
+# Contributors
+
+Thank you very much for contributing to this project!
+
+Due to the way event triggers work with GitHub actions it's a bit harder to test your changes.
+
+Simple changes that can be unit tested can be implemented with the regular workflow where you fork the repo and create a pull request. Note however that the new version of the action won't be executed in the workflows of this repository. We have to rely on the unit tests in this case.
+
+If e.g. environment parameters are changed, the action should be tested end-to-end in a workflow.
+
+To do this, please follow this process:
+
+1. Fork the repo.
+2. Create a PR in **your own repo**.
+3. The "Lint PR title preview (current branch)" workflow will run the new version and will help you validate the change.
+4. Create a PR to this repo with the changes. In this case the preview workflow will fail, but we'll know that it works since you've tested it in the fork. Please include a include a link to a workflow where you've tested the current state of this pull request.
+~~5. Don't run `npm run build` to update the `dist` folder as it will be generated on CI during the build~~

Gemfile

@@ -0,0 +1,49 @@
+source 'https://rubygems.org'
+
+# jekyll/minima — theme
+# Hello! This is where you manage which Jekyll version is used to run.
+# When you want to use a different version, change it below, save the
+# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
+#
+#     bundle exec jekyll serve
+#
+# This will help ensure the proper Jekyll version is running.
+# Happy Jekylling!
+
+gem 'jekyll', '~> 4.3', '>= 4.3.4'
+gem 'kramdown', '~> 2.5', '>= 2.5.1'
+gem 'sassc-embedded', '~> 1.78'
+gem 'rake', '~> 13.2', '>= 13.2.1'
+gem 'minima', '~> 2.5', '>= 2.5.2'
+
+# If you have any plugins, put them here!
+group :jekyll_plugins do
+
+gem 'jekyll_ai_related_posts', '~> 0.1.4'
+gem 'jekyll-avatar', '~> 0.8.0'
+gem 'jekyll-default-layout', '~> 0.1.5'
+gem 'jekyll-feed', '~> 0.17.0'
+gem 'jekyll-github-metadata', '~> 2.16', '>= 2.16.1'
+# gem 'jekyll-include-cache', '~> 0.2.1'
+gem 'jekyll-last-modified-at', '~> 1.3', '>= 1.3.2'
+gem 'jekyll-mentions', '~> 1.6'
+gem 'jekyll-optional-front-matter', '~> 0.3.2'
+gem 'jekyll-paginate', '~> 1.1'
+gem 'jekyll-readme-index', '~> 0.3.0'
+gem 'jekyll-relative-links', '~> 0.7.0'
+gem 'jekyll-seo-tag', '~> 2.8'
+gem 'jekyll-sitemap', '~> 1.4'
+# gem 'jekyll-tagging', github: 'RalphHightower/jekyll-tagging', branch: 'master'
+# gem 'jekyll-tagging', '~> 1.1'
+gem 'jekyll-titles-from-headings', '~> 0.5.3'
+
+# { 2024-09-29 @RalphHightower
+# /home/runner/work/blog/blog/vendor/bundle/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll.rb:28: warning: csv was loaded from the standard library, but will no longer be part of the default gems since Ruby 3.4.0. Add csv to your Gemfile or gemspec. Also contact author of jekyll-4.3.4 to add csv into its gemspec.
+gem 'csv', '~> 3.3'
+# /home/runner/work/blog/blog/vendor/bundle/ruby/3.3.0/gems/safe_yaml-1.0.5/lib/safe_yaml/transform.rb:1: warning: base64 was loaded from the standard library, but will no longer be part of the default gems since Ruby 3.4.0. Add base64 to your Gemfile or gemspec. Also contact author of safe_yaml-1.0.5 to add base64 into its gemspec.
+gem 'base64', '~> 0.2.0'
+# } 2024-09-29 @RalphHightower
+# { 2024-10-29 @RalphHightower 
+gem 'nuggets', '~> 1.6', '>= 1.6.1'
+# } 2024-10-29 @RalphHightower
+end

SECURITY.md

@@ -0,0 +1,9 @@
+# Reporting Security Issues
+
+To report a security issue, please email [[email protected]](milto:[email protected])
+with a description of the issue, the steps you took to create the issue,
+affected versions, and, if known, mitigations for the issue.
+
+I respond within 3 working days of your email. If the issue is confirmed as a vulnerability,
+I will open a Security Advisory and acknowledge your contributions as part of it. This project
+follows a 90 day disclosure timeline.

SUPPORT.md

@@ -0,0 +1,11 @@
+# Support 
+
+## How to file issues and get help
+
+This project uses GitHub issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue.
+
+- **[RalphHightower/blog](https://github.com/RalphHightower/blog/)** is under active development and maintained by @RalphHightower. I will do my best to respond to support, feature requests, and community questions in a timely manner.
+
+## @RalphHightower Support Policy
+
+Support for this project is limited to the resources listed above.