After some deciding and a bit of work on what I should do with the Tildes Issue Log I've chosen to make a little website for it. So instead of bland GitLab Markdown you now get nice HTML with some...
After some deciding and a bit of work on what I should do with the Tildes Issue Log I've chosen to make a little website for it. So instead of bland GitLab Markdown you now get nice HTML with some CSS sugar on top. Or if you're not into CSS whatsoever, it still reads pretty well in Reader View (apart from the tables, they're always ugly).
So here it is: til.bauke.xyz, the til stands for Tildes Issue Log, as I think tildes-issue-log... would be too long of a URL. (or you can find it like this: bauke.gitlab.io/tildes-issue-log, but that's ugly)
I recommend viewing it on a device that has a high(er) width as it's hard to read the tables otherwise, the rest seems to be fine. There's only a tiny amount of CSS to make it view better on mobile devices, I've tried it and it works fine for now, I'll probably end up adding more to make it better. You can always use Reader View instead.
That's it, enjoy! :)14 votes
It's about to tick over to July here in the CEST timezone so I thought this would be an appropriate time to post. You can find the full post here. For anyone who didn't see my trial post a couple...
It's about to tick over to July here in the CEST timezone so I thought this would be an appropriate time to post. You can find the full post here.
For anyone who didn't see my trial post a couple of days ago I'll post the "About" section to give you a taste.
The Tildes Issue Log is a monthly recurring post about the changes and progression that Tildes has made. Highlighting some of the newest additions and changes, as well as a complete table of every issue opened and closed in that month, along with some interesting statistics so you can get a look into the development process and a quick grasp of anything you may have missed.
I'll also like to take this opportunity to ask how you'd like to see this Issue Log posted. I've thought about some options and don't really know what would be best for the community:
- Stay as is, the post on the GitLab repository created with Markdown.
- Have the full post on Tildes. It'll require some restructuring but no big deal.
- Separate website for the issue log with custom styling and all that, probably hosted on GitLab Pages.
Let me know what you think!
If anything is incorrect or you have anything that you'd like to see changed or added, please open an issue, PM me or comment on the posted topic on Tildes.16 votes
Hi, earlier today I got an idea to create some kind of development blog so people who aren't into software development or don't really know how to interpret the issue tracker could see what...
Hi, earlier today I got an idea to create some kind of development blog so people who aren't into software development or don't really know how to interpret the issue tracker could see what progress has been made so far. I think a monthly recap would be the best as sometimes a week could be quiet.
Anyways, here's the post for May.
Keep in mind that a lot of it is just filler and not really useful to read right now, but that's just because I wanted to get some feedback on this idea first. I would love to do this every month, maybe with help of others who are interested too. But I'd have to know that this is something everyone wanted as it could take some time to write up a nice post.
Let me know what you think! In a reply here, private message or issue in the GitLab repo.
Edit: I just changed the issues list to a table, added the opened date and if possible the closed date. This should make it easier to read.
Edit 2: I've just spent some more time on this and made a proper post, with highlights and interesting statistics for the month of June, available here. However, all of the statistics here and the issue table aren't final as we're not fully through June yet. I thought it would be cool for you guys to see what a better post would look like.25 votes