scottydocs

<div style="font-family: sans-serif;">
<? var data = valid(); ?>
<form id="form" name="form">
<? if(Object.prototype.toString.call(data) === '[object Array]') { ?>
<? for (var i = 0; i < data.length; i++) { ?>
<? for (var j = 0; j < data[i].length; j++) { ?>
<input type="checkbox" id="ch<?= '' + i + j ?>" name="ch<?= '' + i + j ?>" value="<?= data[i][j] ?>"><?= data[i][j] ?><br>
<? } ?>
<? } ?>
<? } else { ?>

scottydocs

<div style="font-family: sans-serif;">
<? var data = valid(); ?>
<form id="form" name="form">
<? if(Object.prototype.toString.call(data) === '[object Array]') { ?>
<? for (var i = 0; i < data.length; i++) { ?>
<? for (var j = 0; j < data[i].length; j++) { ?>
<input type="checkbox" id="ch<?= '' + i + j ?>" name="ch<?= '' + i + j ?>" value="<?= data[i][j] ?>"><?= data[i][j] ?><br>
<? } ?>
<? } ?>
<? } else { ?>

scottydocs

101 to 404s: How to write great error messages

Resources from my error messages talk at Write the Docs conference on 16th September 2019.

• 💾 Slides
• 📹 Recording
• 🌍 Conference link

Description of my talk:

"Error messages are such a small and innocuous part of documentation that they sometimes don't always receive the care and attention that they deserve. Even the shortest error message can evoke far stronger, negative emotions in your end users than the majority of your documentation. If you get your error messaging wrong, it can not only lead to poor user experience and customer frustration but also low product satisfaction, and in worst cases, ridicule on social media."

scottydocs

[
  {
    "trends": [
      {
        "name": "#LoveYourPetDay",
        "url": "http://twitter.com/search?q=%23LoveYourPetDay",
        "promoted_content": null,
        "query": "%23LoveYourPetDay",
        "tweet_volume": null
      },

scottydocs

{
   LIMIT=$1
   P=$PWD

   echo "Moving $LIMIT directories up from $P"

   for ((i=1; i <= LIMIT; i++))
   do
       P=$P/..
   done

scottydocs

scottydocs

Is GraphQL really self-documenting?

Resources from my GraphQL documentation talk at API the Docs conference on 9th November 2018.

• 💾 Slides
• 📹 Recording
• 🌍 Conference link.

Description of my talk:

"Developers are raving about how GraphQL is “self-documenting” and how it doesn’t need docs but I disagree. I want to debunk the self-documenting myth, talk about why naming is so important in GraphQL and explain why technical writers still have a key role to play in its documentation."