> When do you start a file with "< ?php"

> Always use tailwind in examples?  

> Use active voice.

> Use second-person singular ("You")

> Sometimes you can introduce a concept with first-person plural ("We") and switch to "You" when giving step-by-step instructions

> Always include import statements 

> Be consistant, but switch it up (tone, filler transition text, using colons)

> Optimize for skimming (don't show "wrong" example first unless you have visual aid. People aint reading the words: this is wrong up-front)


[[Referencing file names in a sentance]]
[[Casing rules]]


* Start with H2's, H1 will be the title of the page
* Have good syntax highlighting, use Torchlight
* Have good typography, use "prose" from tailwind
* Write code examples first, then structure, then links and inlines, THEN paragraphs
* Repeat yourself
    * Write for a user to enter in anywhere and have context.
* Concept of "beginning to end"
    * Using "We" at beginning and transitioning to "You"
    * Using more full code examples at the beginning




Blocks:
* line break
* tips
* warnings
* "go here to learn more"
* check out the screencast here
* Footer with more links

### Order by:
* Order from "generic" to "specific" (broad/niche)
* Order from happy path to edge cases (or commonness of needs/usage)
* Need for previous knowledge (one section might rely on another earlier section)

## Group by:
* Type of thing:
    * ex. `wire:loading.class` is extremely popular. `wire:loading.attr` is not, however it should be placed immediately after `.class` because it's so popular


