hiltful.blogg.se - Ia writer latex

IA WRITER LATEX HOW TO
IA WRITER LATEX LICENSE
IA WRITER LATEX FREE

It remains a rock-solid, very lightweight and very fast editor with just the right level of minimal Markdown support, and I love it for that. For example, this particular paragraph I’m drafting in Byword - my old standby, an app I’ve been using for over half a decade now. None of them thrill me, because all of them do some things really well… and leave others in a “ugh, not quite there” state. These days I do my writing in a wild hodgepodge of tools.

IA WRITER LATEX FREE

In general, I’m not opposed to paying for good services - actually, very much to the contrary! - but if there is a good service with a freemium model and I fit comfortable in the free tier, I’m happy to use it. (This is the piece here that stings the most in terms of ongoing costs, but Lightroom is fabulous, so I’m just rolling with it at this point.)Īs will become clear in the next section, I have spent a… non-trivial… amount of money on writing applications over the last decade. I get Cronos via my $10/month for Adobe’s Lightroom package, which includes Adobe Fonts.

IA WRITER LATEX LICENSE

I paid a few hundred dollars to perpetually license Sabon (the body text) a few years ago - both for the web and for desktop work. In terms of things I do actually pay for (or have in the past), though: The support for normal CMS interfaces to this kind of setup has grown enormously in the past few years, and it can actually be a really good, very lightweight experience. You need to be willing to do a small amount of semi-technical work you don’t have to build an entire site from scratch like I did. I should clarify, before I go any further: this is not a stack I would recommend to anyone else who’s not a total nerd, though this same basic kind of stack is workable with a much lower degree of effort than I put in. ( Hopefully, I say, because I started this post three months ago!) In a follow-on post I will hopefully write as a follow-up sometime this year, I’ll dig into the technical details of how the site is put together. In this post, I will trace out the details of how I get this site to you.

* I actually write using a(n ever-changing) mix of text editors, currently primarily 1Writer on iOS and Byword and Caret on macOS.

* The content - written entirely in Markdown - lives in Git repositories which I maintain on copies of on all my machines as well as on.

The fonts are licensed from (purchased and self-hosted) and (hosted).

a bunch of custom filters and plugins, also written in TypeScript.

a very light use of SCSS to generate the CSS.

a mix of Nunjucks, JSON, and TypeScript for the templating.

The site is generated with 11ty, with .

* The domain name is registered at Hover.

If you want the super short version, this is it (with the topics covered in this post marked with a *): The answer is: I hadn’t, but as of now I have! On seeing this site relaunch back in November, my friend John Shelton asked if I had anywhere I’d listed out the whole of my setup for hosting this site. Here I get into everything from getting a domain and setting up DNS to how I use Markdown and Git!

IA WRITER LATEX HOW TO

People interested in the nerdy details of how to get a website like this up and running.