Skip to content

Latest commit

 

History

History
74 lines (50 loc) · 2.27 KB

README.md

File metadata and controls

74 lines (50 loc) · 2.27 KB
  • Build: npm run build
  • Development: npm start

How it works

Each "post" is a markdown file. File names follow this format: YYYY-MM-DDTHHMM.md. Examples:

  • New files:
    • 2023-08-01T1036.md
    • 2023-08-05T1222.md
  • Ported "reading notes" are:
    • 2022-01-12T1230.md
    • 2022-01-12T1229.md
    • 2022-01-12T1228.md

Each markdown file follows this pattern (tags optional but prefixed with _ to differentiate them in iA Writer from my blog’s posts). No exceptions.

#_article #_twitter #_rss

# [Name of the article I link to](https://example.com/path/to/article)

I liked this excerpt:

> Lorem ipsum santa dolor

Each markdown file gets parsed into a JSON feed item:

[
  {
    // Filename (minus extension)
    id: "2022-01-08T0905",

    // <h1> stripped from markup and extracted into `title` and `external_url`
    title: "Name of article I link to",
    external_url: "https://example.com/..."

    // Body of markdown gets converted to HTML
    content_html: "<p>I liked this..."

    // Other meta info (derived from file name/structure)
    date_published: "2022-01-08T09:05-06:00"
    url: "https://notes.jim-nielsen.com/#2022-01-08T0905",
    tags: ["article", "twitter", "rss"]
  }
]

And then templates produce the index.html file (along with an XML and JSON feed).

URLs

All content is loaded into one giant HTML file.

Why one big file? Because I want to be able to search/filter all notes at once and one page makes that easy. Plus, content should always be written/formatted as text (no embedded images, videos, etc., those must all be linked).

Individual posts are anchor linked in the main file:

  • notes.jim-nielsen.com/#2022-05-01T1200

Perhaps one day they can have their own URLs

  • notes.jim-nielsen.com/2022-05-01T1200

Will require:

  1. Port all exisiting reading notes into new repository as .md files
  2. Script that gets all files, parses them into db.json file, and turns them into static files (and feed files)
  3. Add a thing to all reading notes posts that indicate they are now reposted on notes.jim-nielsen.com — or do a redirect? from old blog reading notes posts to new notes.jim-nielsen.com - this might be a little weird...