Make a new blog

.github/ISSUE_RESPONSES/comment.md

@@ -0,0 +1,5 @@
+## Thank you!
+
+We appreciate your contribution to this project! Please be sure to read the [_**contributing guide**_](https://github.com/coder-lg/Type-on-Strap/blob/master/CONTRIBUTING-GUIDE.md) to learn how you can help make this project better!
+
+If you've created this issue with the 'bug' label, rest assured that we've added it to backlog for triage.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,27 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: 'coder-lg'
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: 'coder-lg'
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/tasks.md

@@ -0,0 +1,15 @@
+---
+name: Tasks
+about: Describe this issue template's purpose here.
+title: 'Tasks:'
+labels: tasks
+assignees: 'coder-lg'
+
+---
+
+- [ ] 
+- [ ] 
+- [ ] 
+- [ ] 
+- [ ] 
+- [ ]

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+# Pull Request for LG's blog
+Thanks for opening a PR here. Be sure to read the contributing guidelines to see how to contribute here!
+## Description
+
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
+
+Fixes # (issue)
+
+## Type of change
+
+Please delete options that are not relevant.
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] This change requires a documentation update
+
+## Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published in downstream modules
+- [ ] I have checked my code and corrected any misspellings

.github/config.yml

@@ -0,0 +1,27 @@
+# Configuration for request-info
+# https://github.com/behaviorbot/request-info
+
+# *OPTIONAL* Comment to reply with
+requestInfoReplyComment: >
+  We would appreciate it if you could provide us with more info about this issue/pr!
+
+# *OPTIONAL* default titles to check against for lack of descriptiveness (MUST BE ALL LOWERCASE)
+requestInfoDefaultTitles:
+  - update readme.md
+  - updates
+
+# *OPTIONAL* Label to be added to Issues and Pull Requests with insufficient information given
+requestInfoLabelToAdd: need-more-info
+
+# *OPTIONAL* Require Pull Requests to contain more information than what is provided in the PR template (Will fail if the pull request's body is equal to the provided template)
+checkPullRequestTemplate: true
+
+# *OPTIONAL* Only warn about insufficient information on these events type (Keys must be lowercase. Valid values are 'issue' and 'pullRequest')
+requestInfoOn:
+  pullRequest: true
+  issue: true
+
+# *OPTIONAL* Add a list of people whose Issues/PRs will not be commented on (keys must be GitHub usernames)
+requestInfoUserstoExclude:
+  - coder-lg
+  - # the other users you wanna add here

.github/hooks/README.md

@@ -0,0 +1,11 @@
+# Git hooks
+
+Git hooks are provided in `hooks/`. The pre-commit hook, when enabled, will check for non-staged assets before commit and abort if found any.
+
+## Setup
+
+`ln lib/hooks/pre-commit .git/hooks/pre-commit`
+
+## Bypass
+
+`git commit -n`

.github/hooks/pre-commit

@@ -0,0 +1,28 @@
+#!/bin/sh
+#
+# Called by "git commit" with no arguments.
+# The hook should run gulp to optimize assets.
+# Will exit with non-zero status if it wants to stop the commit.
+
+: << 'END' # Ancillary code to ensure environment before running gulp
+# If it's on the right directory, proceed. Else, try to fix it. If fail, abort commit.
+if [ ${PWD##*/} != "lib" ] ; then
+    cd lib || exit 1
+fi 
+
+# If gulp is intalled and gulpfile.js is present, then proceed. Else, abort commit.
+if ! [ -f "gulpfile.js" ] || ! command -v gulp; then  
+    printf "gulpfile.js not found or gulp-cli not installed!\n"
+    exit 1
+fi
+END
+
+# If there are non-staged assets, abort commit.
+if git status --porcelain | grep -E '^(\?\?|AM|\nM).*assets/.*$' >/dev/null; then
+    printf "There are non-staged assets, be sure to run gulp before commiting changes!\n"
+    exit 1
+fi
+
+# Proceed with the commit.
+exit 0
+

.github/labeler.yml

@@ -0,0 +1,8 @@
+critical:
+    - '(critical|urgent)'
+
+bug:
+    - '(bug|issue|problem)'
+
+triage:
+    - '(bug|issue|problem)'

.github/release-drafter.yml

@@ -0,0 +1,20 @@
+name-template: 'v$NEXT_PATCH_VERSION'
+tag-template: 'v$NEXT_PATCH_VERSION'
+categories:
+  - title: '🚀 Features'
+    labels:
+      - 'feature'
+      - 'custom'
+      - 'enhancement'
+  - title: '🐛 Bug Fixes'
+    labels:
+      - 'fix'
+      - 'bug'
+  - title: '🧰 Maintenance'
+    labels:
+      - 'devops'
+      - 'custom'
+template: |
+  ## What’s new:
+
+  $CHANGES

.github/stale.yml

@@ -0,0 +1,22 @@
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 15
+
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 7
+
+# Issues with these labels will never be considered stale
+exemptLabels:
+  - pinned
+  - security
+
+# Label to use when marking an issue as stale
+staleLabel: wontfix
+
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed if no further activity occurs. Thank you
+  for your contributions.
+
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false

.github/workflows/approval-workflow.yml

@@ -0,0 +1,14 @@
+on: pull_request_review
+name: Label approved pull requests
+jobs:
+  labelWhenApproved:
+    name: Label when approved
+    runs-on: ubuntu-latest
+    steps:
+    - name: Label when approved
+      uses: pullreminders/label-when-approved-action@master
+      env:
+        APPROVALS: "2"
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        ADD_LABEL: "approved"
+        REMOVE_LABEL: "awaiting%20review"

.github/workflows/issue-and-project.yml

@@ -0,0 +1,38 @@
+name: Issue comments and project triage adding
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  comment-and-project-adding:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v2
+
+      - name: Comment on new issue
+        uses: actions/github-script@0.8.0
+        with:
+          github-token: ${{secrets.GITHUB_TOKEN}}
+          script: |
+             const fs = require('fs')
+             const issueBody = fs.readFileSync(".github/ISSUE_RESPONSES/comment.md", "utf8")
+             github.issues.createComment({
+             issue_number: context.issue.number,
+             owner: context.repo.owner,
+             repo: context.repo.repo,
+             body: issueBody
+             })
+
+      - name: Add issue to project board
+        if: contains(github.event.issue.labels.*.name, 'bug', 'triage')
+        uses: actions/github-script@0.8.0
+        with:
+          github-token: ${{secrets.GITHUB_TOKEN}}
+          script: |
+            github.projects.createCard({
+            column_id: 15285613, # make the project so that i add the column id here.
+            content_id: context.payload.issue.id,
+            content_type: "Issue"
+            });

.github/workflows/jekyll.yml

@@ -0,0 +1,20 @@
+name: Jekyll site CI
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Build the site in the jekyll/builder container
+      run: |
+        docker run \
+        -v ${{ github.workspace }}:/srv/jekyll -v ${{ github.workspace }}/_site:/srv/jekyll/_site \
+        jekyll/builder:latest /bin/bash -c "chmod -R 777 /srv/jekyll && jekyll build --future"

.github/workflows/labeler.yml

@@ -0,0 +1,15 @@
+name: "Issue Labeler"
+on:
+  issues:
+    types: [opened, edited]
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: github/issue-labeler@v2.0
+      with:
+        repo-token: "${{ secrets.GITHUB_TOKEN }}"
+        configuration-path: .github/labeler.yml
+        not-before: 2020-01-15T02:54:32Z
+        enable-versioned-regex: 0

src/markdown/2021-07-26-blog-1.md

@@ -0,0 +1,42 @@
+> :Title
+>
+> Blog 1(from my jekyll site)
+
+> :Author name=LG,
+>         date=2021-07-26,
+>         avatar=src/assets/images/me.png
+
+Good upgrade, bad mistake
+
+Good news + bad news
+
+Bad news: my official github blog, the one I had with 200 commits and more, is gone :sad: angry
+
+I wish, if GitHub reads this, they will send me an email that my official blog can be reclaimed. I would be happy to get that.
+
+Good news?
+
+I started a tech blog.
+
+Not so bad. Because, tech is one big part of our life.
+
+So, if you wanna read the first post, click the button here and head over to the first post and if and only IF you want, sub the RSS. See ya!
+
+> :SeeTypo$
+
+# Tags
+
+The [tags feature of Coding Blog Plugin](https://connect-platform.github.io/coding-blog-plugin/tags) is still being developed.  Eventually the tags will link somewhere.
+
+[express-anger-sometimes](:Tag)
+
+# Comments
+
+> :DarkLight
+> > :InLight
+> >
+> > > :Utterances theme=github-light
+>
+> > :InDark
+> >
+> > > :Utterances theme=github-dark-orange

src/markdown/archive.md

@@ -4,6 +4,9 @@
 
 > :Collapse label=2021, default=open
 >
+> > :Collapse label=July, default=open 
+> > - July 26 of 2021 » [Blog 1](/2021-07-26-blog-1)
+
 > > :Collapse label=June, default=open
 <!-- > > - June 21, 2021 » [Lock Hunter](/2021-06-21_lock_hunter) -->
 >
@@ -36,4 +39,4 @@
 <!-- > > - July 14, 2020 » [Identity as As](/2020-07-14_identity_as_as) -->
 <!-- > > - July 13, 2020 » [Process Explorer](/2020-07-13_process_explorer) -->
 <!-- > > - July 12, 2020 » [Lead with an Executable Project](/2020-07-12_executable_project_first) -->
-<!-- > > - July 11, 2020 » [Systematic Cleaning](/2020-07-11_systematic_cleaning) -->
+<!-- > > - July 11, 2020 » [Systematic Cleaning](/2020-07-11_systematic_cleaning) -->

src/markdown/index.md

@@ -4,6 +4,8 @@
 
 # Latest Posts
 
+> :ArticleCard src=/2021-07-26-blog-1
+
 See the [archive](/archive) for older posts.
 
-> :ToCPrevNext
+> :ToCPrevNext