org-capture-templatesinstead. YASnippet looks like it might be more flexible because you can fill in fields in a non-linear order and you can re-evaluate Emacs Lisp expressions as you type. Lots of people do cool things with YASnippet. For example, it's popular for programming because it lets people quickly expand short sequences into longer syntax. Check out this Emacs Rocks episode on YASnippet to get a sense of what it can do. (Note: YASnippet has changed its naming convention slightly, so things like
yas/texthave been replaced with
yas-text.) People have used it for e-mail templates and to fill in metadata for blog posts. I'd like to use YASnippet more. Where can I integrate it into my workflow? Probably wherever checklists and templates make sense. I've been thinking about checklists and templates as a way to improve how I do things. Checklists are good for making sure that you complete tasks more consistently, not missing any important steps. You can work faster when there's a guide, since you don't have to keep thinking of the next step each time. The simple act of checking things off can encourage you to put in more effort, since the list shows you your progress. It also makes it easier to remember to follow up. Templates help you improve the structure of your work. You can make sure you cover all the important parts. If you use similar structures for many things, then people get used to finding information in the same logical places. This doesn't mean that you're stuck with cookie-cutter formats. You can still adapt the format to your needs. I'm particularly interested in using checklists and templates to improve in three areas:
- Programming: I'd like to write with less friction and use best practices like testing
- Helping the Emacs community: Checklists can help me make sure I do all the steps to prepare for and make the most of Emacs Hangouts and Emacs Chats. They might also lower the intimidation factor so that I end up scheduling these more often.
- Writing: I think checklists and templates will help me invest more time into developing thoughts, relationships, and structure.
kanbanpackage for Org Mode. Maybe I'll try both approaches. In any case, checklists will help me remember to think about designs and tests before implementing the code, and maybe I can keep track of deployment notes, lessons learned, and follow-up tasks.
- Reach out to the person who's going to be featured on the Emacs Chat, or at least one other person who's willing to be there for the Emacs Hangout (so that I don't end up talking to myself for the first ten minutes, which is Awkward)
- Figure out what will be discussed (for Emacs Chats)
- Set up a time, considering timezones
- Set up the Google+ event page
- Update the Google Calendar
- Post a notice on Twitter and on my blog (I've been forgetting to do this step)
- On the day of the event
- Do the last-minute push (I've been forgetting to do this as well)
- Create the Google Hangout on Air
- Set it up for Q&A
- Invite the other person in for Emacs Chats, or post the URL for Emacs Hangouts
- Host the video chat
- Remind people where the recording can be found
- Update the Google+ page with the link to the next thing
- Extract the MP3 from the video, change the properties, and upload it to archive.org
- Post a blog post with the embedded video, podcast audio, and quick notes
- Transcribe the video or pay for transcription
- Edit the transcript
- Update the post with the transcript
- Update the Google+ event page with the link to the transcript, post to social networks (I've been forgetting this)
- Update EmacsLife.com, too (yet another thing I've been forgetting)
org-trelloto make a Trello card and assign it to the person who does my transcriptions.
- The template asks you to be explicit about the post's objective and subject.
- It encourages you to add more illustrations, links, and stories.
- It reminds you to take steps that you might otherwise skip, and you might spend several days revising the post.
org-refile-able targets) and displayed the section from my blog post index in another window, I think that would be a pretty neat start. I tend to draft posts within my sharing outline (which I sporadically publish at http://pages.sachachua.com/sharing/). When I'm done, I delete the subtree, sometimes replacing it with a link to the post to help me follow up on it in the future. This means losing that metadata, though. It might be interesting to keep the metadata so that I can review the goals and backstory of a blog post. YASnippet can also help me keep track of the TODOs related to a post as well. For example, I might want to come up with sketches, tweet links, or follow up on ideas. If I use a YASnippet to plan my blog post in the first place, then I can create a TODO (possibly with a link back to the blog post) that I could leave in place or refile to the appropriate location in my regular Org Mode files. I don't think YASnippet dynamic fields persist after the file is saved and reloaded, though. How would that work if I need to change things? Maybe I can use
multiple-cursorsto mark all the matching text in the subtree, or do other clever things with it…