docs: making updates to Editor Guide

[CBID2]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

This PR makes a couple of updates in the Editor Guide. I noticed that when scheduling a post to be published the next day, the message, "This URL is public but secret, so share at your own discretion". After raising this issue to @michael-tharrington and learning that posts will only appear in feeds and on a user's profile when they are published on the day they are scheduled. Through another conversation, Michael pointed out that the bullet point about the Markdown editor needs to be updated since Dev.to now has two editors. By making these adjustments, users would gain a better understanding of how to edit and publish their posts.

Related Tickets & Documents

Not applicable

• Related Issue #
• Closes #

QA Instructions, Screenshots, Recordings

UI accessibility checklist

If your PR includes UI changes, please utilize this checklist:

• Semantic HTML implemented?
• Keyboard operability supported?
• Checked with axe DevTools and addressed Critical and Serious issues?
• Color contrast tested?

For more info, check out the
Forem Accessibility Docs.

Added/updated tests?

We encourage you to keep the code coverage percentage at 80% and above.

• Yes
• No, and this is why: please replace this line with details on why tests
  have not been included
• I need help with writing tests

[optional] Are there any post deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Thank you for opening this PR! We appreciate you!

For all pull requests coming from third-party forks we will need to
review the PR before we can process it through our CI pipelines.

A Forem Team member will review this contribution and get back to
you as soon as possible!

[github-actions]

Uffizzi Preview deployment-38927 was deleted.

[michael-tharrington]

I think this is right, though I asked @CBID2 (Chrissy) to add a period. And also, is there any way I can see what this message is going to look like once it appears on DEV?

[michael-tharrington]

@CBID2, I know we chatted about this a good bit over Discord, but here's what I'm thinking, let's make this change to the Things to Know section instead.

And actually, we have the opportunity to make 2 changes!

Here's what I'm thinking (changes in bold):

• We use a markdown editor that uses Jekyll front matter.
• Most of the time, you can write inline HTML directly into your posts.
• We support native Liquid tags and created some fun custom ones, too! Trying embedding a Tweet or GitHub issue in your post, using the complete URL: {% embed https://... %}.
• Links to unpublished posts (drafts or scheduled posts) are shareable for feedback/review. These posts have a notice which reads "This URL is public but secret, so share at your own discretion." They are not visible in feeds or on your profile until published.
• When you're ready to publish, set the published variable to true or click publish depending on the editor version, you're using.

[CBID2]

Hi @lightalloy! :) The updates have been made, and now my PR is ready to be merged! :)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

see 3 files with indirect coverage changes

📢 Thoughts on this report? Let us know!.

[benhalpern]

Looks good to me, thanks for the contribution @CBID2!

@michael-tharrington we can verify this in production via the Uffizzi link in the PR — will show us just what it looks like.

[CBID2]

Woohoo! 😊 Thanks @benhalpern

[michael-tharrington]

Nice @benhalpern! Thanks for merging.

I think I just need a little demo on where to go to see the Uffizzi link. But I trust this is in good shape. @CBID2 talked about the plans for this one at length in Discord... btw, nice work Chrissy! 🙌