I’d like to point out Gramps.js, a web frontend to your Gramps database. I’ve been using it already for half a year, but would like to advertise it now to have more users give it a try and hopefully more developers joining and adding new features.
What is it? It’s a web app that can be used to browse all the information in your Gramps tree - people, relationships, media objects, places, … - via a web browser.
What is it meant for? It’s meant for sharing all your genealogical research data - that you are of course organizing with Gramps! - with others, e.g. family or relatives; additionally, it is meant as an alternative way to access (and later also edit) the information in Gramps, e.g. when you’re on the go with a mobile device but without a PC.
How does it compare to the narrated or dynamic web site reports? The philosophy is very different, as the backend (the API) runs directly on top of your Gramps database (or a copy of it), so no export is necessary. Arbitrarily many views can be generated dynamically without having to generate a huge number of HTML files. And in principle, the app scales to enormously large databases, as the objects are only fetched in chunks. However, there are downsides. First and foremost, the app is currently much more difficult to deploy - you can’t use a vanilla web hosting service but need docker hosting or your own (virtual) server. (This is actually a limitation of the Gramps Web API, not the Gramps.js frontend.) So, whether this app or one of the existing reports are right for your depends on your use case.
What is it the motivation for & history of this project? I always wanted a way to share all the research I collect in Gramps with my family/relatives, but didn’t want to work with static HTML exports. I was interested in the Gramps Connect app but it never really materialized. Nevertheless, in Gramps 5.0 much work was done by the developers to make the code more modular and to make many functions accessible to other Python packages. Based on this, I developed a first, simpler Gramps web app. Following a discussion on this board, we started developing an app-independent backend (the Gramps Web API), so I split the frontend code into a new project that became Gramps.js.
What is the development status & roadmap for the project? The frontend reached its first usable state in December 2020 and I have used it in production since. There hasn’t been much activity in the repository recently since I was busy with other things, but I will definitely keep developing this (I need it for myself!) and would love to have more devs join. For me, the most important addition will be to add read/edit support, which of course requires adding this to the Web API first.
I want screenshots!
OK, here are some screenshots from the demo server that uses the Gramps example tree: