← Back to the portfolio
Content

MJRP Knowledge Garden

A place where I share knowledge, the books I've read, recommendations, inspirations, and the notes and summaries I produce.

The problem

Years of reading and synthesis sat in private notes, with no place others could consult.

The solution

A two-language site published from Obsidian through Git, with a page for each book.

The outcome

Live, with the shelf open to anyone who wants to read.

The Garden's home page: the tree's canopy, with the title
The problem

Years of reading and synthesis sat in private notes, with no place others could consult.

What sat in notes: the week's reflection and the featured summaries, now in plain view.

What sat in notes: the week's reflection and the featured summaries, now in plain view.

The solution

A two-language site published from Obsidian through Git, with a page for each book.

A book's page: cover, reading status, executive summary and connections to other books.

A book's page: cover, reading status, executive summary and connections to other books.

The concept

A garden, not a blog: each idea starts as a seed, grows as a sprout and matures into a tree, in its own time.

The concept: seeds, sprouts and trees, according to how mature each idea is.

The concept: seeds, sprouts and trees, according to how mature each idea is.

The outcome

Live, with the shelf open to anyone who wants to read.

The shelf, with filters by reading status and category that combine and reach down to the subcategory.

The shelf, with filters by reading status and category that combine and reach down to the subcategory.

The CMS

The site has its own CMS, the admin: there I find the books, AI drafts the summaries, and I review and publish.

Inside the CMS: the AI processing queue.

Inside the CMS: the AI processing queue.

More screens

The shelf organized by category.
Another book, the same page: Machine, Platform, Crowd, with its connections.
The shelf in spines: each colour comes from a cover, and the ribbon marks open summaries.
Recent summaries, trees and the garden's roots.
The forest: the books linked by the maps, each category a grove.
The admin: what needs attention, the next reads and each page of the Garden.
The reading plan: dragging between columns changes the reading and the order.

The shelf organized by category.

Content

MJRP Knowledge Garden

A place where I share knowledge, the books I've read, recommendations, inspirations, and the notes and summaries I produce.

The problem

Years of reading and synthesis sat in private notes, with no place others could consult.

The solution

A two-language site published from Obsidian through Git, with a page for each book.

The outcome

Live, with the shelf open to anyone who wants to read.

The Garden's home page: the tree's canopy, with the title
The problem1 / 5

Years of reading and synthesis sat in private notes, with no place others could consult.

What sat in notes: the week's reflection and the featured summaries, now in plain view.

The solution2 / 5

A two-language site published from Obsidian through Git, with a page for each book.

A book's page: cover, reading status, executive summary and connections to other books.

The concept3 / 5

A garden, not a blog: each idea starts as a seed, grows as a sprout and matures into a tree, in its own time.

The concept: seeds, sprouts and trees, according to how mature each idea is.

The outcome4 / 5

Live, with the shelf open to anyone who wants to read.

The shelf, with filters by reading status and category that combine and reach down to the subcategory.

The CMS5 / 5

The site has its own CMS, the admin: there I find the books, AI drafts the summaries, and I review and publish.

Inside the CMS: the AI processing queue.

More screens1 / 7

The shelf organized by category.

More screens2 / 7

Another book, the same page: Machine, Platform, Crowd, with its connections.

More screens3 / 7

The shelf in spines: each colour comes from a cover, and the ribbon marks open summaries.

More screens4 / 7

Recent summaries, trees and the garden's roots.

More screens5 / 7

The forest: the books linked by the maps, each category a grove.

More screens6 / 7

The admin: what needs attention, the next reads and each page of the Garden.

More screens7 / 7

The reading plan: dragging between columns changes the reading and the order.

What sat in notes: the week's reflection and the featured summaries, now in plain view.
A book's page: cover, reading status, executive summary and connections to other books.
The concept: seeds, sprouts and trees, according to how mature each idea is.
The shelf, with filters by reading status and category that combine and reach down to the subcategory.
Inside the CMS: the AI processing queue.
The shelf organized by category.
Another book, the same page: Machine, Platform, Crowd, with its connections.
The shelf in spines: each colour comes from a cover, and the ribbon marks open summaries.
Recent summaries, trees and the garden's roots.
The forest: the books linked by the maps, each category a grove.
The admin: what needs attention, the next reads and each page of the Garden.
The reading plan: dragging between columns changes the reading and the order.
Content

MJRP Knowledge Garden

A place where I share knowledge, the books I've read, recommendations, inspirations, and the notes and summaries I produce.

The shelf organized by category.
Another book, the same page: Machine, Platform, Crowd, with its connections.
The Garden's home page: the tree's canopy, with the title
What sat in notes: the week's reflection and the featured summaries, now in plain view.
A book's page: cover, reading status, executive summary and connections to other books.
The concept: seeds, sprouts and trees, according to how mature each idea is.
The shelf, with filters by reading status and category that combine and reach down to the subcategory.
Inside the CMS: the AI processing queue.

What sat in notes: the week's reflection and the featured summaries, now in plain view.

The problem

Years of reading and synthesis sat in private notes, with no place others could consult.

What sat in notes: the week's reflection and the featured summaries, now in plain view.

What sat in notes: the week's reflection and the featured summaries, now in plain view.

The solution

A two-language site published from Obsidian through Git, with a page for each book.

A book's page: cover, reading status, executive summary and connections to other books.

A book's page: cover, reading status, executive summary and connections to other books.

The concept

A garden, not a blog: each idea starts as a seed, grows as a sprout and matures into a tree, in its own time.

The concept: seeds, sprouts and trees, according to how mature each idea is.

The concept: seeds, sprouts and trees, according to how mature each idea is.

The outcome

Live, with the shelf open to anyone who wants to read.

The shelf, with filters by reading status and category that combine and reach down to the subcategory.

The shelf, with filters by reading status and category that combine and reach down to the subcategory.

The CMS

The site has its own CMS, the admin: there I find the books, AI drafts the summaries, and I review and publish.

Inside the CMS: the AI processing queue.

Inside the CMS: the AI processing queue.

Built with

Next.js · TypeScript · Obsidian · Vercel · CMS (Content Management System)