Welcome! We are a few open source sanskrit programmers, and this is our centralized repository + user inteface of data pertaining to the ashtadhyayi and its commentaries. We welcome you to contribute corrections to the content or improvements to the UI.


This data is presented in many places on the internet (wikisource,, avg-sanskrit, etc..), but there was no centralized place where corrections and curations could happen in a crowdsourced yet controlled fashion. Hence this repository.


Format and location

The content is curated in Each vritti file is devanagari encoded markdown text with yaml frontmatter. Shorter files (padachcheda, anuvritti, adhikara, full_sutra) are plain text files (to avoid extra work for static website generators who might be using this data). Helpful scripts are located here.

Contributing corrections

Preferring repo

Since 2020, shrI nIlesh of reports that several study groups are actively contributing corrections to the repo (see here). Hence, for classical vRtti-s such as siddhAnta-kaumudI, kAshikA, mahAbhAShyam - contribute to his repo directly - you can use the links to links to site and edit url on our interface (pictured below).


Via Github pull requests (preferred)

Follow the following steps (which only seem complicated at first, but are very simple):

  • Just click on the appropriate icon.
    • This will take you to a Github page, where you will be prompted to sign up/in, and “make a fork” as necessary.
  • Make and save your edits.
  • Send us a “pull request”.
    • Helpful videos: here, here
  • Some repository moderator will then review, accept your changes and regenerate the site.

Manual notification (Not preferred)

Just send us a message (with the full corrected vritti text).

Data origin

Many vrittis were typeset via the short-lived sansknet project by Rashtriya Sanskrit Vidyapeetha, Tirupati. The content was originally gathered by diligent folks such as shrI ajit and shrI dhaval from such files ephemerally shared on the internet. This content then went through many hands. Some of this content was also retrieved from the excellent site (where shrI nIlesh personally curates the content). We plan to periodically compare with such independently maintained sources and correct the content.

User Interface (UI)

We use the Hugo static site generator to generate webpages, and github to host the site at The UI heavily copies shrI nIlesh’s

Automatic updates

Ordinarily, wercker piplenes set up under the ashtadhyayi and ashtadhyayi-ui projects are automatically triggered upon updates to the respective repositories, leading to the updated UI.

  • Status
    • content triggering UI builds: wercker status
    • ui builds: wercker status

Updating the UI with the latest content (Manully)

  • Update the content - git submodule foreach "(git checkout master; git pull)&"
  • Install Hugo
  • Run hugo (Takes ~ 16s as of 20181224.)
  • Check in and push the changed files in the doc directory to github gh-page branch.

Technical considerations

  • is a convenient place to present the data (no money needed for server resources).
  • The Jekyll static site generator is just too slow for data of this magnitude.
  • Content is loaded from github.

Running off internet

  • clone the data repository within static subdirectory and point the attributes in the js_include tags in the details page to point to it.
  • Fix the variables in the hugo config.toml file appropriately.