Consider re-writing the title for each submission, since we’re no longer looking for SEO optimization.

• [x] Email to list
• [x] Share in newsletter
• [x] SEO Keywords
• [x] Title has CTR potential, but not click-bait
• [x] Linking
  • [x] External links work
  • [x] Inbound links from existing articles
  • [x] Outbound links to existing articles
  • [x] Link to courses / products
  • [x] User generated content links
    • [x] StackOverflow
    • [x] DEV.to comments
    • [x] Quora questions
    • [x] Github issues
    • [x] Medium
  • [x] Suggest links to existing articles on other websites
• [x] Sharing
  • [x] Reddit
  • [x] HackerNews
  • [x] Discord/Slack groups (not in any right now)
  • [x] Schedule Twitter posts for next 3 months
  • [x] Schedule Tweets for every tech/person mentioned along with a link
  • [x] VueJS developers (DM Anthony)
  • [ ] Pony Foo
• [x] Crosspost (2+ weeks later)
  • [x] DEV.to
  • [x] HackerNoon (import directly)
• [x] Atomizing
  • [ ] Tips
  • [ ] Pitch a variation of the post as a guest post in exchange for backlink
  • [ ] Twitter thread with link to article
  • [ ] Shortened version on Reddit
  • [ ] Publish video version on YouTube
  • [ ] Video snippets
    • [ ] YouTube shorts
    • [ ] Twitter
    • [ ] Newsletter

Feedback from Austin:

• The premise that it’s “immediately obvious” what’s reactive when using ref is actually the main point of divide → if it’s obvious to you then you like ref, if it’s not then you prefer reactive
  • Assumes the reader is already familiar with ref
  • Other objects can have a value property, so you can’t always assume this is true
• Not needing value in the template contradicts the original premise
• Watcher → is this an advantage of ref, or just a justification?
• Reactivity transform looks cool
• “only refs can be reassigned” → feels like a false statement since you’re assigning the value and not the object
• Destructuring argument is the best one so far → but this can be solved with toRefs