Hi
user
Admin Login:
Username:
Password:
Name:
Search-First Writing for Developers
--client
pyconau
--show
pycon_au_2016
--room Room_105 11305 --force
Next: 1 Integrating 2 factor authentication into your project
show more...
Marks
Author(s):
Heidi Waterhouse
Location
Room 105
Date
aug Fri 12
Days Raw Files
Start
11:50
First Raw Start
error-in-template
Duration
0:40:00
Offset
None
End
12:30
Last Raw End
Chapters
Total cuts_time
None min.
https://2016.pycon-au.org/schedule/47/view_talk
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
SearchFirst_Writing_for_Developers.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
If people can't use your software, you have already failed as a developer. This talk digs in to how optimizing for search and using the existing technical assistance forums can put your product ahead of the pack. Technical writing, in all its variations, is a type of interface with your product. It incorporates everything from an error message to an implementation guide. How can you as a developer make deploying, using, and promoting your product as painless as possible? Make it searchable. Make finding the answer to a problem so trivially easy that your user barely even remembers they had a problem. No one wants to be using software. They want to be data mining or manipulating beautiful photos or targeting advertising. Making them think about the software diverts them from what they want to be accomplishing. Use these documentation techniques to get them in and out and on their way. (my secret is: I'm always angry when I have to read help)
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review