.git hidden dir). It all greatly depends on what they're really able / willing to do, and how much work you want to do. Another person on Freenode was talking about writing a custom plugin to auto-commit on after_build_all. That discussion brought #655. Lots of options here.
https://www.getlektor.com/docs/deployment/rsync/
@Paulef_twitter The arguments passed to rsync basically set. They start as -rclzv, and have other things appended to account for speciying targets, credentials, and such. So it isn't easy to specify -a for instance.
As for the credentials, an example you can mostly see is getlektor.com itself. It has lektor deploy production in the .travis.yml file, and the target specified in the project file. The bit you don't see is that in travis-ci.org we also have the environment variable LEKTOR_DEPLOY_KEY set, which is automatically looked for and used. Like https://www.getlektor.com/docs/deployment/rsync/#credentials says though, there's a few ways of getting a key recognized. Hope that helps!
@Paulef_twitter I agree. I just made lektor/lektor-website#277 for some improvements about this. Please comment on it if you nail down some specific instructions to help inform a better explanation.
About the link thing, markdown doesn't have any fanciness for that, but you can actually just put html inside markdown. So, a cheap way of doing this is to just craft that link manually as html, inside content that is otherwise normal markdown.
That's been a minor annoyance of mine for a while too. Someone should make a plugin that detects links that are external and make them all have target=_blank.
blog/foo/contents.lr with _hidden: yes and in blog.html referring to that object. I tried {% set myfoo = this.children.include_hidden(true).filter(F._model == 'foo').first() %} but this does not work. If I omit the _hidden in the contents that part does work, but with an (understandable) TemplateNotFound error for foo.html.
