Flip site

Signed-off-by: Stephen Michael Kellat <[email protected]>

Author: skellat

.github/FUNDING.yml

@@ -1,7 +1,7 @@
 # These are supported funding model platforms
 
-github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
-patreon: erielookingproductions
+github: skellat
+patreon: # Replace with a single Patreon username
 open_collective: # Replace with a single Open Collective username
 ko_fi: smkellat
 tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel

.github/ISSUE_TEMPLATE/programming-request.md renamed to .github/ISSUE_TEMPLATE/general-patch.md

@@ -1,6 +1,6 @@
 ---
 name: General Patch
-about: A Proposed Patch 
+about: A Proposed Patch
 title: 'Patch Proposal'
 labels: ''
 assignees: ''

.github/workflows/static-mkdocs.yml

@@ -0,0 +1,56 @@
+# Simple workflow for deploying static content to GitHub Pages
+name: Deploy mkdocs content to Pages
+
+on:
+  # Runs on pushes targeting the default branch
+  push:
+    branches: ["master"]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  # Build job
+  build:
+    runs-on: ubuntu-latest
+    env:
+      MKDOCS_VERSION: 1.5.3
+    steps:
+      - uses: actions/checkout@v4
+      - name: Setup Pages
+        id: pages
+        uses: actions/configure-pages@v5
+      - name: Install mkdocs
+        run: |
+          sudo apt-get update ; 
+          sudo apt-get -y install mkdocs 
+      - name: Build with mkdocs
+        run: mkdocs build
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: ./docs
+          
+   # Deployment job
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

CODE_OF_CONDUCT.md

@@ -1,5 +1,5 @@
 CODE OF CONDUCT
-================
+=================
 
 ## Ubuntu Code of Conduct v2.0
 
@@ -16,65 +16,81 @@ The Code of Conduct governs how we behave in public or in private whenever the p
 We strive to:
 
 #### Be considerate
+
 Our work will be used by other people, and we in turn will depend on the work of others. Any decision we take will affect users and colleagues, and we should consider them when making decisions.
 
 #### Be respectful
+
 Disagreement is no excuse for poor manners. We work together to resolve conflict, assume good intentions and do our best to act in an empathic fashion. We don’t allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one.
 
 #### Take responsibility for our words and our actions
+
 We can all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully, and work to right the wrong.
 
 #### Be collaborative
+
 What we produce is a complex whole made of many parts, it is the sum of many dreams. Collaboration between teams that each have their own goal and vision is essential; for the whole to be more than the sum of its parts, each part must make an effort to understand the whole.
 
 Collaboration reduces redundancy and improves the quality of our work. Internally and externally, we celebrate good collaboration. Wherever possible, we work closely with upstream projects and others in the free software community to coordinate our efforts. We prefer to work transparently and involve interested parties as early as possible.
 
 #### Value decisiveness, clarity and consensus
+
 Disagreements, social and technical, are normal, but we do not allow them to persist and fester leaving others uncertain of the agreed direction.
 
 We expect participants in the project to resolve disagreements constructively. When they cannot, we escalate the matter to structures with designated leaders to arbitrate and provide clarity and direction.
 
 #### Ask for help when unsure
+
 Nobody is expected to be perfect in this community. Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful.
 
 #### Step down considerately
+
 When somebody leaves or disengages from the project, we ask that they do so in a way that minimises disruption to the project. They should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off.
 
 #### Leadership, authority and responsibility
+
 We all lead by example, in debate and in action. We encourage new participants to feel empowered to lead, to take action, and to experiment when they feel innovation could improve the project. Leadership can be exercised by anyone simply by taking action, there is no need to wait for recognition when the opportunity to lead presents itself.
 
 #### Delegation from the top
+
 Responsibility for the project starts with the “benevolent dictator”, who delegates specific responsibilities and the corresponding authority to a series of teams, councils and individuals, starting with the Community Council (“CC”). That Council or its delegated representative will arbitrate in any dispute.
 
 We are a meritocracy; we delegate decision making, governance and leadership from senior bodies to the most able and engaged candidates.
 
 #### Support for delegation is measured
+
 Nominations to the boards and councils are at the discretion of the Community Council, however the Community Council will seek the input of the community before confirming appointments.
 
 Leadership is not an award, right, or title; it is a privilege, a responsibility and a mandate. A leader will only retain their authority as long as they retain the support of those who delegated that authority to them.
 
 #### We value discussion, data and decisiveness
+
 We gather opinions, data and commitments from concerned parties before taking a decision. We expect leaders to help teams come to a decision in a reasonable time, to seek guidance or be willing to take the decision themselves when consensus is lacking, and to take responsibility for implementation.
 
 The poorest decision of all is no decision: clarity of direction has value in itself. Sometimes all the data are not available, or consensus is elusive. A decision must still be made. There is no guarantee of a perfect decision every time - we prefer to err, learn, and err less in future than to postpone action indefinitely.
 
 We recognise that the project works better when we trust the teams closest to a problem to make the decision for the project. If we learn of a decision that we disagree with, we can engage the relevant team to find common ground, and failing that, we have a governance structure that can review the decision. Ultimately, if a decision has been taken by the people responsible for it, and is supported by the project governance, it will stand. None of us expects to agree with every decision, and we value highly the willingness to stand by the project and help it deliver even on the occasions when we ourselves may prefer a different route.
 
 #### Open meritocracy
+
 We invite anybody, from any company, to participate in any aspect of the project. Our community is open, and any responsibility can be carried by any contributor who demonstrates the required capacity and competence.
 
 #### Teamwork
+
 A leader’s foremost goal is the success of the team.
 
 “A virtuoso is judged by their actions; a leader is judged by the actions of their team.” A leader knows when to act and when to step back. They know when to delegate work, and when to take it upon themselves.
 
 #### Credit
+
 A good leader does not seek the limelight, but celebrates team members for the work they do. Leaders may be more visible than members of the team, good ones use that visibility to highlight the great work of others.
 
 #### Courage and considerateness
+
 Leadership occasionally requires bold decisions that will not be widely understood, consensual or popular. We value the courage to take such decisions, because they enable the project as a whole to move forward faster than we could if we required complete consensus. Nevertheless, boldness demands considerateness; take bold decisions, but do so mindful of the challenges they present for others, and work to soften the impact of those decisions on them. Communicating changes and their reasoning clearly and early on is as important as the implementation of the change itself.
 
 #### Conflicts of interest
+
 We expect leaders to be aware when they are conflicted due to employment or other projects they are involved in, and abstain or delegate decisions that may be seen to be self-interested. We expect that everyone who participates in the project does so with the goal of making life better for its users.
 
 When in doubt, ask for a second opinion. Perceived conflicts of interest are important to address; as a leader, act to ensure that decisions are credible even if they must occasionally be unpopular, difficult or favourable to the interests of one group over another.

CONTRIBUTING.md

@@ -1,8 +1,4 @@
 CONTRIBUTING
 ============
 
-Please file an issue first explaining your request before proposing a patch.  A patch without an explanatory issue may be rejected summarily without further explanation.  Help us understand how you want to help us, please.
-
-Follow the template provided.  That's a key step.  If you need to deviate heavily from the template you really must contact us directly instead.
-
-We reserve the right to take any and all actions necessary to preserve the operation of this site that in our judgment we deem necessary.
+Contributions are not accepted at this time.

README.md

@@ -1,5 +1,5 @@
 # skellat.github.io
 
-There presently is no proper site hosted here.  Hosting of things is migrating to safe harbors abroad.  It should never have come to this.
+There presently is no proper site hosted here.  The hosting paradim is migrating.  It should never have come to this.
 
 America is in a bad place right now...

SECURITY.md

@@ -2,7 +2,7 @@
 
 ## Supported Versions
 
-There is no deployable software as this is a static site.  In theory there may be an interception problem if there is a man-in-the-middle attack upon GitHub Pages.  There can also be a problem if the Internet Archive is attacked as we may not be fully aware of problems on their end.
+This is the scaffolding to a Jekyll site so there is no set single version.  There is only continuous integration.
 
 ## Reporting a Vulnerability
 

docs/index.html

@@ -0,0 +1,20 @@
+site_name: skellat.github.io
+# theme: readthedocs
+# locale: en
+site_url: https://skellat.github.io/
+site_description: The GitHub Pages Website of Stephen Michael Kellat
+site_author: Stephen Michael Kellat
+repo_url: https://github.com/skellat/skellat.github.io
+repo_name: GitHub
+remote_branch: master
+docs_dir: page
+site_dir: docs
+copyright: Copyright © 2019-2025 Stephen Michael Kellat.  
+plugins: []
+markdown_extensions:
+  - smarty
+  - toc:
+      permalink: true
+  - sane_lists
+nav:
+     - Home: index.md

mkdocs.yml

@@ -0,0 +1,3 @@
+## Stay Tuned
+
+A site may appear here soon?