🌐 Website Issue | Track website changes/modification - changelog #828

Closed
opened 2019-04-03 17:44:28 +00:00 by temporarium · 9 comments
temporarium commented 2019-04-03 17:44:28 +00:00 (Migrated from github.com)

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!

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!
ghost commented 2019-04-03 17:47:14 +00:00 (Migrated from github.com)
Changelog: https://github.com/privacytoolsIO/privacytools.io/commits/master Atom feed: https://github.com/privacytoolsIO/privacytools.io/commits/master.atom
temporarium commented 2019-04-03 17:52:19 +00:00 (Migrated from github.com)

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.

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.
ghost commented 2019-04-03 17:59:14 +00:00 (Migrated from github.com)

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.

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.
temporarium commented 2019-04-03 18:30:12 +00:00 (Migrated from github.com)

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 :-)

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 :-)
ghost commented 2019-04-03 18:33:13 +00:00 (Migrated from github.com)

Because you selected "Website Issue" instead of "Feature Suggestion".

Screenshot from 2019-04-03 20-32-52

Because you selected "Website Issue" instead of "Feature Suggestion". ![Screenshot from 2019-04-03 20-32-52](https://user-images.githubusercontent.com/4354706/55503774-aad4f900-564f-11e9-904b-3d2d55eafafe.png)

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/

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/
ghost commented 2019-04-03 19:41:49 +00:00 (Migrated from github.com)

Perhaps every PR that adds or removes something should add something like 2019-04-03: Add Turtl to CHANGELOG.md?

Perhaps every PR that adds or removes something should add something like `2019-04-03: Add Turtl` to CHANGELOG.md?
Mikaela commented 2019-04-04 12:03:05 +00:00 (Migrated from github.com)

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.

> 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.

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.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#828
No description provided.