GitXplorerGitXplorer
a

arjun.is

public
1 stars
1 forks
10 issues

Commits

List of commits on branch master.
Verified
75e7547c176bd7ffdbf96b61a3750c4bfb2d53fb

Bump ws from 8.13.0 to 8.17.1 (#49)

ddependabot[bot] committed 7 months ago
Unverified
f8693f03812dd47f6d4e60a29dd114c251dc7cbc

update intro

aarjunattam committed a year ago
Unverified
5e3a40f0da445d0692fd265d82c96c01d4075da8

fix

aarjunattam committed a year ago
Unverified
fc2def6428dcde6cfb901322b70b1ea0538e93f5

fix

aarjunattam committed a year ago
Unverified
6b1655237eac86b326387eeb797c4dff1cac1e2c

fix img size

aarjunattam committed a year ago
Verified
0e240c2ee13f38109395f54b23364733c4b42694

new post (#47)

aarjunattam committed a year ago

README

The README file for this repository.

arjun.is

This repo powers arjun.is. Built with Eleventy and hosted on Vercel.

Usage

npm install
npm run build

For local setup, run the following (fetchPosts.js fetches posts from GitHub Issues). Delete scripts/.cached-issues.json to force a re-fetch.

node scripts/fetchPosts.js
npm run serve

Pre-requisites for local:

  • Setup a PAT in GITHUB_TOKEN=xyz in .env. This token needs to have permissions to access issues on this repo
  • (Note to self) While committing changes, don't stage .md changes in .gitignore

How it works

The current version supports two sources of content (blog posts): markdown files and GitHub Issues. Effectively, this makes GitHub Issues the CMS for my blog. My intent was to move over to GitHub Issues completely, but given that I had existing posts in markdown, I went ahead with this approach (instead of neater? approaches that build on 11ty magic.)

Website arch

Issue tag convention

  • All tags are passthrough — except ones prefixed with meta:
  • For example
    • meta:internal for issues related to site fixes
    • meta:published for issues that are published