A tiny, lightweight, self-contained, RESTful document store
some web service to retrieve and persist your application data.
a web server to serve the source code and the static assets of your web application.
NodeJS is probably one of the easiest backend to setup for prototyping SPAs. It is very easy to create a simple web server in Node and to implement a simple RESTAPI using Express or a similar framework, but you still need to install node and write some code to wire up your backend.
I wanted something even more lazy then that. I wanted a fully self-contained program able to:
Serve static files
Act as a simple JSON document store
Provide a simple RESTAPI to work with
(bonus!) provide a way to pack web apps for easy distribution
A simple command-line application to generate self-contained HTML documents
Did you ever have to write a document, but didn’t want to (or couldn’t) use MS Word or another WYSIWYG word processor? Yep, I agree: that’s what Markdown is for.
Luckily, there are a lot of editors that support Markdown out there (I just installed MacDown myself), and they work great, most of the time. Unfortunately though, they often:
Generate HTMLfragments instead of full documents
Don’t include a proper stylesheet
Generate more than one file
The last one on the list in particular, is true for all of them: the stylesheet may be embedded in the document, but if you want to use images, they are managed as separate files; and the same thing happens if you want to use custom fonts. That’s how HTML works, after all… right? Nope.
Or why I am still going to use Nanoc for the foreseeable future
Every so often I wonder whether I should ditch my current blogging platform and try something new and shiny that just came out. Luckily, normally I come back to the same conclusion: I don’t need to change anything, I just need to find the time and the will to write about something.
This time is no different, but I thought I’d write a roundup of platforms, services, and tools that you can use for blogging or managing your personal sites. Note that this roundup is by no means exhaustive (like most roundups) — it’s just a quick overview of the pros and cons of a few systems that I’ve been researching on lately. Maybe it will be useful to someone.
Simply all the books your Documentation Team needs
I’ve been working in Technical Communications for nearly seven years now, first and foremost Technical Writer and more recently as Documentation Manager. In other words, my work revolves around manuals and online helps, authoring tools and guidelines, documentation standards and… you get the picture.
And yet, although I write articles and develop documentation tools in my free time as well, I rarely write about my job on this site. But when I was offered the opportunity to read and review Best Practices for Technical Writers and Editors, I just couldn’t resist.