Can users modify their existing subscriptions?

[renzms]

---

KB Article Creation Checklist

• [x] Write initial draft for this KB Article; label this issue draft and either questions or tutorials
• [x] Add required YAML configuration
• [x] Add Tags for this KB Article to the YAML config (see YAML Keys (Explained))
• [x] Edit and finalize draft for publishing (remove draft label, add draft-finalized label)
• [x] Assign Issue to yourself and create Markdown file (remove draft-finalized label, add pending)
• [x] Project Lead: Review and Publish KB Article (remove pending label, add published label)

  Additional TODOs

Additional TODO list items go here.

---

KB Article Published @ comment-mail.com
:page_with_curl: See: Can users modify their existing subscriptions?

:octocat: View Markdown File | :pencil2: Edit Markdown File

---

[renzms]

@raamdev Please check thanks!

[raamdev]

Looks good! The screenshots only show examples of "Add New Subscription" but the question asks about modifying a subscription. Could you also include a screenshot that shows a subscription being modified?

[renzms]

@raamdev

• Updated Screenshots
• Added New titles for images
• Some added details

Please check thanks!

[raamdev]

@renzms Looks a lot better! A bit of feedback:

• Please use red arrows and red boxes—blue arrows and boxes blend in way too much and it's hard to tell if they're part of the screenshot or something you added. The box border thickness could be about half as thick as they are.
• Are you using Snagit for screenshots? Adding a border and a bit of dropshadow makes screenshots so much nicer and makes it so that they don't feel like they bleed into the page (e.g., a white background in the screenshot against a white background of the page makes it hard to see where the screenshot actually ends). With Snagit, this can be accomplished with literally 2 clicks:

• You mention that subscribers can access the My Subscriptions page after subscribing—where else can they access it from? (The footer of any emails they receive.) I recommend mentioning that as well (a screenshot of that is not necessary).
• "Comments/" needs a space after 'Comments'
• "Choosing Post", "Choosing Comment"—these should be headers and not just bold text. I suggest H3.

[renzms]

@raamdev

Changed:

• [x] Please use red arrows and red boxes—blue arrows and boxes blend in way too much and it's hard to tell if they're part of the screenshot or something you added. The box border thickness could be about half as thick as they are.
• [x] Are you using Snagit for screenshots? Adding a border and a bit of dropshadow makes screenshots so much nicer and makes it so that they don't feel like they bleed into the page (e.g., a white background in the screenshot against a white background of the page makes it hard to see where the screenshot actually ends). With Snagit, this can be accomplished with literally 2 clicks:
• [x] You mention that subscribers can access the My Subscriptions page after subscribing—where else can they access it from? (The footer of any emails they receive.) I recommend mentioning that as well (a screenshot of that is not necessary).
• [x] "Comments/" needs a space after 'Comments'
• [x] "Choosing Post", "Choosing Comment"—these should be headers and not just bold text. I suggest H3.
• [x] Updated Screenshots

Ready for check, thanks!

[raamdev]

Looks much better! Please see my notes on the screenshots here: https://github.com/websharks/comment-mail-kb/issues/31#issuecomment-309596113

[renzms]

@raamdev

Updated screens, thanks!

[raamdev]

by accessing their My Comment Subscription Page via the link found at the bottom

Bottom of where?

There they can customize their subscriptions from

Reiterate where "There" is (e.g., "From the My Comment Subscriptions page, they can customize...")

Choosing Post

Those headers above the screenshots are not necessary here, since the screenshots all contain the same headers and since there's no text in between the screenshots. The headers just look redundant.

---

Also, from now on, please add toc-enable: off to the YAML markup at the top. That will disable the Table of Contents generation on the KB Article when it's published. If there aren't multiple headers or if the KB article is really short (e.g., just 1 or 2 headers), then it doesn't make sense to unnecessarily generate a TOC.

[renzms]

@raamdev

Updated with corrections, please check. Thanks! :)