I feel the inconsistencies of available time to work on my game myself so I understand.
I feel my devlogs are great, but time availability does hinder progress and subsequently the devlogs. (I don't have anything playable that is interesting enough yet.)

Maybe in a jam about devlogs, start with goals at the beginning, then end with where progress got you at the end of the month. Maybe at least one update a week even if it is to show where you are or what you are planning.
Each time tick off something you want to accomplish, even if it is part of a whole, it helps write the devlog.
Each time you patch something, put it on a list. Then the devlogs write themselves.

A lot of released games follow the cadence of giving patch notes of the things they remember, but I feel players want to know what they are working on.
I know  bugs come up unexpected and obviously no bug is planned, so patch notes are a great medium for that, but if adding features, that is where I think the goals come in.

How many times have you heard in a game that the "developers didn't listen to the fans" or they "want something fixed, developer isn't listening". If you let them know it's on your list, even if you haven't fixed it, it shows you know about it and are working on it. Players just want communication. Communication builds a strong community.

I think this could sell really well once you are done with it if that is your plan and keep actively communicating to players. Already told a couple friends about the concept and they were intrigued and interested in playing once it's completed.