4 ms·
It's actually a good* guide, but the wording of the title seems to me to imply that this is a simple process. It's dizzying complex. * by "good", I mean the fo
by lucideer 9y ago
It's actually a good* guide, but the wording of the title seems to me to imply that this is a simple process. It's dizzying complex.
* by "good", I mean the following:
- prose is engaging
- very comprehensive, no hidden steps missed
- covers a lot of things that while not strictly necessary, will make an experienced git user's website updating workflow much easier in the long run
- covers some small details that are new to me that look nice
It's very much complexity up front in exchange for automated ease later though.
- buro9 9y agoI agree. From the outset it is version controlled, CDN'd, available over HTTPS, and would withstand being linked from the front page of HN just fine. It's not just a static site, it's one that is easy to grow and modify, and that can withstand a lot of traffic immediately with no investment in infrastructure for the author. (evidenced by the fact that it is withstanding a HN front page set of traffic)
- Semiapies 9y agoYes, comparing this to throwing up a barebones page at www.somewhere.edu/~username/index.html is apples and oranges.
- KirinDave 9y agoHmm, I found lots of proofreading material.