Following up on this. Reinstalled Pythonista— figured the errors I was seeing might be an indication of some other issues with my set up. All's working fine now. ;)

@johnridesabike interesting. Jinja2 is indeed in my site-packages folder and not in either of my Standard Libraries. I'll see what I can do to upgrade...

Later: Okay. Stumped. Tried to update my Jinja2 via pip (stash). Response was that I have the most recent update. Edited jinja2/environment.py (as pointed out by ccc) but got another error:

File "/private/var/mobile/Containers/Shared/AppGroup/AF1E5A27-A567-45C1-A998-655B7A0E2B63/Pythonista3/Documents/site-packages/jinja2/environment.py", line 600
    except TemplateSyntaxError, e:
                              ^
SyntaxError: invalid syntax

Fixing the jinja2 errors one by one seems like it could be an exhaustive process, and I'm sure there's a more sensible way to get things up and running— sounds like there's a problem with my install of jinja2. Anyone have any further suggestions?

This sounds both really useful AND inspiring. I look forward to seeing what it's capable of.

Got this error when trying to run WordRoom.py

Traceback (most recent call last):
  File "/private/var/mobile/Containers/Shared/AppGroup/AF1E5A27-A567-45C1-A998-655B7A0E2B63/Pythonista3/Documents/projects/from GitHub/WordRoom-master/WordRoom.py", line 10, in <module>
    from jinja2 import Environment, FileSystemLoader
  File "/private/var/mobile/Containers/Shared/AppGroup/AF1E5A27-A567-45C1-A998-655B7A0E2B63/Pythonista3/Documents/site-packages/jinja2/__init__.py", line 37, in <module>
    from jinja2.environment import Environment, Template
  File "/private/var/mobile/Containers/Shared/AppGroup/AF1E5A27-A567-45C1-A998-655B7A0E2B63/Pythonista3/Documents/site-packages/jinja2/environment.py", line 575
    info.external_attr = 0755 << 16L
                            ^
SyntaxError: invalid token

Any suggestions?

+1 for the Taskpaper app recommendation. If you're happy with Taskpaper mode in Editorial and looking for something to work with the same files on your Mac, it's a no-brainer.

That said, one of the (many) reasons I love Editorial is that it allows you to build your own solutions. You can implement your own basic support for simple Github style tasks in a workflow with three action steps:

1: extend selection (select the entire line)
2: find "[ ]" and replace with "[x]"
3: replace selected text (with input)

Assign an approriate shortcut, then run this on any Github style task you want to mark done. You could, in theory, use this kind of thing to manage your tasks in a way that respects both conventions. Say, prefix your tasks with "- [ ]", then configure your "mark done" workflow to add both a "[x]" and a "@done" tag, though that would actually mean a little more work at the Mac end for comparable functionality.

Point is, even if the functionality you want isn't already baked in, with a little DIY, Editorial's a beautifully extensible app that allows for a lot of flexibility in setting things up in a way that makes sense for you.

Sorry to hear about the sync issues. Did you see any greyed out files appearing in the file list? Have you tried to delete and reinstall?

As far as a selective sync goes: you can select a root folder in Dropbox to link to Editorial. This means you'll have access to files in folders and subfolders contained within that root.

Hm. You may have sorted this by now, but it sounds like you've got an old version of that workflow? I just ran my regular back up with this one: and all seems well...

How are you exporting? If you're using a workflow, which one? There may well be a reference to some CSS in it somewhere that you can adjust...

FYI - if you haven't already found it, you can add or adjust preview templates by swiping left on the screen to preview, then tapping on the "Preview" title at the top of the page.

In Settings-->Editor-->General, make sure "Folding" is enabled (I can't remember if it's switched on by default).

In Taskpaper mode, Editorial recognises lines that end with a colon (:) as headings. In Markdown mode, lines that begin with hashes (#) are headings as per canonical Markdown. Taskpaper folding respects indent levels.

Folding can also be implemented via workflows, which allows you to set things up in a way that suits you, and to control folding irrespective of syntax mode. See the following examples:

http://www.editorial-workflows.com/workflow/5830937191383040/_eD31MsIIzo

http://www.editorial-workflows.com/workflow/5808136921284608/5vSeu1APl5w

http://www.editorial-workflows.com/workflow/5876841533407232/ruJGzB9j9aQ

http://www.editorial-workflows.com/workflow/5871227071627264/MnOqmin2fvk

@CascadeHush If we're talking about templating blocks of functionality from within workflows, then yes, presets work nicely— something I only discovered myself recently. In order to set a whole sequence of workflow steps as a preset, I've sometimes used "if" blocks as wrappers/containers. Put the steps you want to keep as a reusable block in an "if" block, set that as your preset, then unpack them in your new workflow when needed.

Almost forgot: "sub-workflow" might also be helpful in this context?