This week I didn't really work on defining my final project idea. I've been sick for a few days, so just tried to keep up by doing the assignment for the week and building the documentation structure...
I'm pretty familiar with some of the tools used like version control, markdown, terminal etc. So that helped but haven't used them all together in this way. So I had some fun customizing and browsing around.
I'm a somewhat familiar with some of the tools used like a bit of github, markdown, terminal, and other tools for version control like Mercurial. So that helped but haven't used them all together in this way. So I had some fun customizing and browsing around.
## Research
This week's research mainly consisted of learning these tools using the tutorials provided and some google. It was nice, I'm liking this way of documenting!
This week's research mainly consisted of learning these tools using the tutorials provided and some google. It was nice, I'm liking this way of documenting! I've decided on a way to organize my files and am looking forward to building this documentation in the next few months. Documenting is something I like doing, because it helps me keep the new skills and insights I've gained fresh and *actually* usable. As in: being able to redo things I did in the past. That said, I can get a bit wordy doing it, trying to get all the details in, but it's coming from a good place ;)
> "Inspirational block quote here! I'll have to get back to you on that one, but nice to know how to do it - LB"
> "Consider the possibility of an honest mess" - Co-Star astrology app
## Useful links
...
...
@@ -20,12 +20,12 @@ This week's research mainly consisted of learning these tools using the tutorial
Tried to rush it and left the default email in by accident. Whoops!
Deleted the key and generated a new one with the terminal commands provided here and popped it into the settings in Gitlab
[Generating an SSH key] (https://gitlab.fabcloud.org/help/ssh/README#generating-a-new-ssh-key-pair)
[Generating an SSH key] (https://gitlab.fabcloud.org/help/ssh/README#generating-a-new-ssh-key-pair)*
Also Fiore's tutorial has been very helpful here:
-[Fiore's tutorial](https://vimeo.com/253336757)
\**I notice I'm becoming one of those people who writes documentation but doesn't explain the steps that already feel "normal" to me. Hmmm. I'll have a think to think what I think about that.
\**I notice I'm becoming one of those people who writes documentation but doesn't explain the steps that already feel "normal" to me. Hmmm. I'll have a think to think what I think about that.*
## Customizing text, fonts, colors in the mkdoc
...
...
@@ -66,7 +66,7 @@ theme:
```
And this is the result! Kaleidoscopic, isn't it...
"so kaleidoscopic!"
*screenshot of the page you are looking at*
## Working offline
...
...
@@ -74,14 +74,14 @@ And this is the result! Kaleidoscopic, isn't it...
Since I'm working on a book project where I'll be using some of these tools as well, I also tried cloning my repository into the GitHub Desktop app using the URL provided in the back-end of the project using the SSH dropdown.
"screenshot of dashboard"
*screenshot of dashboard*
It's pretty straightforward, you go find the files locally and them edit them with an editor. And it tells you whether you have any commits that need pulling (when changes were made somewhere else) or pushing (when you make changes locally but haven't updated the master repository yet). Nice and easy! I also loved learning Mercurial on the command line though (forever grateful @Zaerc) I'm used to Brackets from back when I did Fabacademy. [Oh sweet memories from 2015](https://fabacademy.org/archives/2015/eu/students/bogers.loes/finalproject.html)
But for another project I'll be using MacDown, which gives a nice simultaneous preview! Pretty nice too. Let's see which one I'll end up using.
"screenshot of Macdown editor"
*screenshot of Macdown editor*
This is an example blog for the Fabricademy Course.
You can edit it on [Gitlab](http://gitlab.fabcloud.org). The software used turns simple text files
written in [Markdown](https://en.wikipedia.org/wiki/Markdown) format, into the site you are navigating.
Each time you change a page using the Gitlab interface the site is rebuilt and all the changes published
in few minutes.
If this is your site, go on and edit this page clicking the Gitlab link on the upper right, changing the text below and deleting this.
No worries, you can't break anything, all the changes you make are saved under [Version Control](https://en.wikipedia.org/wiki/Version_control) using [GIT](https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control). This means that you have all the different versions of your page saved and available all the time in the Gitlab interface.
This my documentation blog for the Fabricademy Course of 2019. I'm participating from Amsterdam with Fab Lab Waag as my local lab.
## About me
Hi! I am Emma Brewer. I am an art director & graphic designer based in New York City working on branding, visual identities, editorial design and web design.
