With Khemarato Bhikkhu
Alas! Asaṅga spent twelve years in the wilderness, practising meditation.
Without achieving any success in meditation,
He has instead compiled these treatises
As a burden for an elephant’s back.
The library contains all the best content I’ve found on the internet organized by topic. These topical bibliographies are then compiled into course syllabi which can be studied online or used more formally in your study group or class. There are already students and teachers around the world using the free material here in a variety of ways and I couldn’t be prouder!
This webpage started its life as my personal library of Buddhist stuff on Google Drive.
After reading stuff I found online, I would contemplate what I learned from it and who I’d recommend it to. Only after answering these questions would I then squirrel away the e.g. PDF into an appropriate Google Drive folder.
In this way, my library (like all personal libraries) has slowly grown to serve two purposes:
- to organize my own media for their safe-keeping, retrieval and revision, and
- for others (hello!) to peruse and, hopefully, benefit from.
These two aims find unity in the pride that any book-worm feels towards their library. As a map of my mind, this website contains (editorially and structurally) my own biases. This is a feature not a bug. I named my elephants with a great deal of thought, care, and delight and I hope that, as you explore my library, you will feel some of that delight too. 😊 🐘
About the Code
Running the site locally
To speed that up, you have two options:
- You can add the
--config _config.yml,_quick_build.ymlbuild flag for a faster, but partial build.
- You can serve the production build locally like so:
rm -rf _site git pull git checkout prod cp -r . ~/obu-prod git checkout master mv ~/obu-prod _site JEKYLL_ENV=production bundle exec jekyll serve --incremental --skip-initial-build
For more information on the build process, see the Jekyll docs.
The Source Code
You can think of each of the
_folders in the source code as representing individual object types. Each folder is a different “table” in the hardcoded “database.”
- _authors - Each author with their own page.
- _content - All of the individual works in the library, divided by
categorybased on the type. Each content item has a number of metadata fields listing its bibliographic information (e.g.
pages) in Bibtex format, or linking the entry out to its file (e.g.
external_url) or linking it to its internal groups (e.g.
authors). Conventionally, I put raw strings in
"Quotes"and I represent links to other objects as
unquoted-slugs. The templates then use these slugs to fetch the related objects at page render time.
- _categories - This folder houses the
index.htmlpages for the
/content/*folders and contains a little metadata about the categories, such as their plain English titles.
- _courses - The University’s courses.
- _data - Site configuration variables.
- _drafts - Unpublished courses or blog posts.
- _includes - A Jekyll folder which houses the site’s reusable UI components.
- _journals - Periodicals which get their own page.
- _layouts houses the html page templates.
- _plugins is not a collection but rather contains native Ruby extensions for quickly running complex algorithms or for dynamically generating content. Currently my only custom plugin is the similar content engine which you can read about here
- _posts are the blog posts which make up the newsletter.
- _publishers are the publishers which I have granted their own hub.
- _sass contains the site’s css.
- _series - Are collections of
_contentitems that were published as part of a
series(specified by fields on the content item)
- _tags - The bibliographic topics, arranged in a directed, ontological graph via the
- _tests - A couple of pages with Integration Tests I have used during development in the past, and decided to keep around in case the code is useful in the future.
- .github/workflows contains my GitHub Actions Workflow files which build the site and check for certain errors.
For questions about the source code, feel free to email me or post an issue or comment on GitHub.
The beauty of Jekyll is that it outputs plain HTML, which you can find in the repo’s “prod” branch. This raw html can be reworked in a variety of ways. Feel free to reuse it in any (ethical) way you like. If you would like to contribute anything back, please message me, open an issue or fork the repository and open a pull request!
Over the next few years, I would like to expand the University’s offerings further and further: into various regional forms of Buddhism, subtler points of Buddhist philosophy, the grand arcs of history, and much, much more. I’d also like to continue to improve the site’s design and marketing, so it can be as accessible as possible to as many people as possible.
I have also tried to select content with “staying power” to avoid, as much as possible, anything that will become outdated in a few years. This site, while technically a “blog,” is not yet another newsfeed of digital ephemera. It is an experiment in a somewhat slower technology. It is my hope that this curriculum will provide a solid basis for Buddhist Studies for decades to come.
- This repository, like all other things in life, is imperfect and subject to change.
- While I have taken some pains to ensure that everything here is accurate and legal, please know that you use the University at your own risk.
- The various views expressed in each work are the opinions of the respective author(s) and may or may not reflect my own.
A big thank you to the content sources, to Google (for hosting the Drive library), to GitHub for hosting the site, and to all the various content creators and publishers who generously put their work out there for free. It’s a testament to Buddhist generosity that such an expansive and outstanding collection can be compiled (almost entirely) from free material.
To all my teachers—past, present and future. Especially you.