Started off as the Marvel Master Reading Order + Others but has rapidly changed into support for all facets of reading lists.
These lists are not created by me. Credit goes to the original authors. I'm just curating them into a single place to hopefully make it easier for people to find what they want to read.
We now have a discord server to help coordinate changes and discuss things in an open and public place. Join us!
- The main intention of this project is to create an organized source of reading lists for use with comic readers/management software
- All reading lists are provided in CBL format, with book data verified on ComicVine
- The data used to create these reading lists is based on CBRO, CMRO and sometimes just people saying "read it this way". The intention of this project is not to create an alternative to these tools, but to make the information in these tools usable in comic reading/management software.
There are a number of websites that host reading lists in a visual display (no CBL files available). These include the following:
- Comic Book Reading Orders (CBRO)
- Complete Marvel Reading Orders (CMRO)
- Comic Book Herald (CBH)
- Comic Book Treasury (CBT)
- Marvel Guides (MG)
- Comicvine
- The Marvel Comics Guide
- Marvel Fandom
- How To Love Comics (HTLC)
- League of ComicGeeks (LoCG)
- Marvel.com Reading Orders (Official)
There are only a handful of software packages out there that can consume .CBL files. If you know of more, let us know.
We are looking for people who want to assist in the efforts to make the best reading lists possible. There is a nightly report created that lists problems we detect that need fixing: https://cbl-report.packetmancer.com/corpus-integrity/
If you have time, look up which lists are listed as having problems and create PR's fixing the issues.
- Please explain your logic when submitting each PR. You're probably going to get some comments or questions from us, to ensure consistency and maintainability.
- Keep the top level updated as you add / remove issues.
- Each PR should come with a meaningful name (what is being added/fixed)
- Make meaningful commits, squash them if necessary
- Try to keep it to one group of fixes per pull request to keep things clean and easy to understand. ie; don't edit 25 different files across publishers in a single request. However, you can group up changes like
$List with eventsand$List without eventsin the same PR.
- If you have any constructive feedback on the data structure, how reading lists are handled, or issues within the reading-lists themselves, please create an issue on Github which clearly explains your thoughts, or join our discord to talk it over.
- If you have programming abilities there is always some small script that could be useful. Join the discord and ask in the #tools channel.