MOKUJI—collection of
notes by Zac Fukuda

Introducing 目次 (Mokuji)

001
Sep 2, 2015

This web magazine, 目次(:mokuji), is nothing, but where I practice my coding skill and where I use to store my knowledge. About three years ago I started to learn how to code. Whatever I made a fast progress or not, since then, I believe I learned the basics to develop web applications. As what I do gets more complicated, my brain started feeling stressed out and it's causing confusion of knowledge. Then I came to realize that it is time to re-organize my knowledge. And world-wide-web is a perfect place to do that.

目次 = a table of contents

How I come up with name of this web magazine, 目次(:mokuji), might deserved to be noted. I don’t know how you found this magazine, but I assume you are probably a designer, a developer, or someone who works in IT industry, so you know what the index pages mean. A common filename for such a page is index.html if you’re not redirecting, routing, or configuring. Personally, I’ve been feeling awkward about this and I’m going to explain why. World Wide Web has a history of that its purpose of the early development was to exchange documents on scientific research, which means websites are replacement to books. When you open the book, you find the index section at the end of the book. You never find it around beginning, instead you find the table of contents describing what kind of information it provide at which page. So I thought home pages should be more like table of contents. In short, it should be called so. 目次(:mokuji) is a Japanese word for the table of contents and I thought this fit best for my magazine. As it indicates, this home page functions like table of contents. The logo on the header indicates not just a title of this site, but also what it is about.

Open Source

I’m currently freelancing and sometimes I wonder if I could have a place to test my code. Despite of the fact that there are many local server environment choices out there, such as Vagran, or Docker, with my enthusiasm, I want to know whether my code works on the remote. Additionally, there could be someone who find my test codes useful. That is one of reason I decided to put my knowledge on the web. Util by now, I haven’t open-sourced any my codes. Since I am a freelance and I work by myself most of time, I never had a chance to share my codes with my fellows. In this magazine, I’ll try to open-source as much as possible.