🌐 Website Issue | Track website changes/modification - changelog #828
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#828
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The privacytools.io site is very practical.
However, I found it much easier to follow when it was all one page, as I had a website tracker checking for changes/modifications and could see right away what was added/removed, etc.
Now, it's all-over-the-place.
Please consider some kind of change-log feature on your website.
Please also consider adding RSS.
Thanks!
Changelog: https://github.com/privacytoolsIO/privacytools.io/commits/master
Atom feed: https://github.com/privacytoolsIO/privacytools.io/commits/master.atom
Thanks. I'm referring more to the content of the website, not it's design/layout, like "Removed Signal from such-and-such section", "Added Threema", etc.
Perhaps this could be useful? https://github.com/privacytoolsIO/privacytools.io/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Amerged -- merged PRs.
That's how content is added.
Thank you for your suggestions, but it's still too... "under-the-hood".
Anyway, it's not the end of the world. I'm not sure why the issue got tagged as "high priority". It's more of a suggestion :-)
Because you selected "Website Issue" instead of "Feature Suggestion".
This is probably something we can figure out, but I'm not sure what the best way to handle this would be.
@temporarium FWIW, you can still check out https://www.privacytools.io/classic/
Perhaps every PR that adds or removes something should add something like
2019-04-03: Add Turtl
to CHANGELOG.md?I fear this would cause a merge conflicts easily, so it should be something to do after merging a PR.
I think it might be possible to abuse Jekylls blogging capabilties, but it might look ugly in long term.
Seeing as /classic/ exists I think we'll close this issue, because the solution outlined in the OP should still work fine. I don't think there's really a way to implement a changelog without updating it manually every time we merge something, or using GitHub releases, both of which seems unwieldy.