SuttaCentral
I wonder if we could so something about this. maybe a banner or something with “recent updates” driven by newly published translations …. Maybe we’ll look at this when the new Bilara is ready.
Definitely it’d be good to get the updated files. Whether they want footnotes or not is up to them. I’m equivocal about it TBH!
Bhante,
Surely the “publication date” in the info could indicate updates. Your SN translations all seem to say “2018”.
Well, we already have a prominent link on the forum, but it currently links to an unused category. In fact, this very post probably belongs there.
I think you meant “to” the forum, as in the “What’s New” button on the main site, right?
Here’s a friendly screenshot for those who may be unaware of or forgot about this button (I too have noticed, forgotten, and remembered it 
):
Right, yes. Better have something automated. We could have a look around and see if there are best practices on this.
Terrific to hear about the annotations. I had a quick look for them but couldn’t see them. How do I get to them?
Hello and welcome to the community!
Regarding the annotations, just hold your cursor over the small blue dots at the end of a line of text and a box with the annotation will appear.
We hope you enjoy and benefit from your interactions on SC!
With kind regards,
Jasudho on behalf of The Moderators
This will happen when the setting is “tooltip on asterisk”. I am not sure what the default setting is. The settings are described here.
Have fun with the annotations! 
I love this. I actually have been using “purpose” ever since a thread I started ( Saṅkappa vs cetanā ) specifically asking what the difference between saṅkappa and cetanā is, specifically this comment explaining what the Venerable saw as the difference between the two: Saṅkappa vs cetanā - #14 by Thaniyo_Bhikkhu
You actually participated in the thread, first pointing out that it’s often used somewhat synonymously with vitakka, and saying you had switched to “thought” for saṅkappa and about how hard it is to map Pali concepts of cognition to English ones. (Which I mention to you because I suspect you would be interested to see an example of how your own thinking has changed over time. I certainly love seeing my own evolution.)
@Pasanna I think you’d be interested in that thread, too. (I can’t imagine I’ve never actually linked it for you, but I also can’t imagine you would remember it because we talk about so many other things.)
Keyboard shortcuts are very helpful too. You can see them in the Views pop-out—white letters in a grey square. I use V and N a lot.
Incidentally, before Ven. Snowbird mentioned the link to the Meta > Updates category, I had been thinking of mentioning changelogs. But in my experience they are typically too verbose for the average user (and sometimes the opposite, where it can be hard to tell what the changes are from the commit subject).
Update posts like this I think can be more helpful, IMO.
For example, in developer changelogs that I edit or publish, I typically hide various commits that are not as important/relevant to a reader (behind a <details> tag), such as in these two releases of a library I help maintain. I categorized the commits as well, so that readers can quickly parse through what is relevant to them.
In another tool I used to maintain, we wrote detailed upgrading and new feature guides that are specifically user-facing (with different user audiences too, such as operators/admins vs developers/users), different from dev changelogs (where the automation also has some filters).
That is to say, typically it requires a human editor/curator to summarize, categorize, detail, and/or reword dev changelogs in order to make them easier and more relevant to read for the average user.
In a sentence, it’s because the audiences of a PR/commit (reviewers) and an application (end users) are different. (the timescales are also different - multiple individual, related PRs could potentially be summarized in a user-facing changelog)
In this specific case, we’re referring to translator notes, but the category has developer notes about main site changes too. Both can have plenty of less user-facing commits like minor spelling & grammar fixes, typo fixes, mark-up fixes, internal documentation updates, refactors, CI changes, etc.
There are tools like changesets that require developers to add a human readable changelog note for every PR if relevant. A similar feature could be added to Bilara if it doesn’t already exist.
But I’m not sure if it’s the best fit per se, given the editing nuances I mentioned above.
Many such tools have gaps in them where a change can be missed or under-documented too as categories, relevance, summaries, etc are all subjective (i.e. a human has to carefully review in any case).
All the subjectivity of the problem create lots of edge cases for automation in my experience.
A “last updated” field somewhere would be more straightforward, but ofc will be unable to convey what changed. It certainly could link to a commit diff on GitHub though.
Some simpler automation could identify categories of changes, e.g. “X translation for Y sutta changed”, or “Z sutta translation was added to legacy texts”, but I am not sure if that would be sufficient.
I agree… from a user perspective, an annotations change log would be overwhelming and of little value. For the (very small) population of people who are really interested in the rationale for various changes, they can simply inquire here on the forum.
The details of changes, last updated and so on is of course all available on Github, and can be queried both for specifics and statistics if desired. There’s probably third-party visualization tools for that kind of thing, look at what areas are being worked on and so on.
I was thinking more of a simple count of newly added texts, listing them per language, and maybe an indication of total number of changes (including revisions).
Thanks so much Bhante! These notes are always very useful for me. SN also has such central teachings, I’m sure I will benefit even more than from the DN and MN notes.
(I usually use the html files offline, since I don’t have internet usually. Does anybody know if I can generate a file for SN? Or just be patient for it to be updated? I’m not very good with this Github.)
It should have been updated by now, let me remind Hongda.
Yeap, it’s there. Thanks, @HongDa
Quick service, haha! THanks. @HongDa
The footnotes are not included in the file, though. 
Only the links to them.
