1. Add a donate button. Some folks probably just want to see more examples (or an example in their field, but don't have a specific paper in mind.)
2. Have a way to nominate papers to be examples. You could do this in the HN thread without any product changes. This could give good coverage of different fields and uncover weaknesses in the product.
It would be fun if the donate button let you see how many additional papers your gift would enable. I'm thinking of something like the ticker you see on the right side of a GoFundMe page, where you might see "$175 donated today, 112 papers translated, credit for 96 papers remaining"; one might choose to donate $20 rather than, say, $5, if there were a clear connection to the benefit you were providing.
I commit the images alongside the markdown files in GitHub. My site is has numerous images and there are logical groups of posts. I make those logical groups of posts a git submodule, so I don't have all posts on my machine (or iPad) at one time.
Working Copy (git for iPad) handles submodules reasonably well, I have a few that I'm working on cloned on it and others are not so I don't use so much space.
There are a number of church presentation systems that integrate with planning center to get data, like ProPresenter, EasyWorship, etc. You'd need to get them to update their software to support your system as well. The easy way for you to do that is to clone the planning center API worts and all, which means you're probably just building a planning center clone.
churchapps.org is competing in this space with open source software and the price of free for their hosted versions. I don't know what their adoption rate is.
The switching costs are large in terms of time and effort for small churches. It's often one or two persons leading the charge to switch. They may not fully understand how every person interacts with the system, but they would need to set up the new system and do a trial run, likely in parallel with the existing system. Then train staff and volunteers how to use their part of the system.
Thanks for this feedback. I wasn't aware of churchapps.org. There's a fair bit of overlap both in terms of scope and intended tech stack. I'd be curious to know their adoption rate, too.
The company isn't shutting down, probably just an attempt to get more subscriptions.
The company used to support Strava integration from their app in Free Ride mode. That broke last year, the app still reports that a ride happened, but the ride is reported as 0 miles, 0 minutes long. I have the low end bike and rower from them. The machines are great physically.
I use the render hooks feature of Hugo to generate srcset attributes for my images. I don't see render hooks in many other SSGs.
Downsides of Hugo are the documentation isn't great and the go templating language is quirky. I suspect that poor documentation is a common issue for many static site generators.
I remember that time. I was taking a graduate level intro to graphics class and we had an assignment to write a ray-tracer and turn in a printout of the final image along with a printout of the source code. The instructor allowed any programming language, so I used a different one for each assignment.
For the ray tracing assignment I used postscript, the PS image operator calls a function to return each sample in the image. The transform matrix made scaling the image easy.
My code was two pages long, up from one page because of the many comments. I think the next shortest was 15 pages. It also ran faster than most others because of the faster processor.
1. Add a donate button. Some folks probably just want to see more examples (or an example in their field, but don't have a specific paper in mind.)
2. Have a way to nominate papers to be examples. You could do this in the HN thread without any product changes. This could give good coverage of different fields and uncover weaknesses in the product.