Rename and re-title tasks 11..16. Add tasks list

[OleksiyRudenko]

Refers to #90, #97

• Renamed files containing tasks Nos.11 through 16
• Listed tasks in tasks/README.md

@viktor-yakubiv please, review

[viktor-yakubiv]

Looks good to me. Please fix a little bug, I explained in the comment, and merge.

BTW, I am working on Contents proposal too and relinking of tasks 0-10.

[viktor-yakubiv]

Markdown reference links require reference keys that looks like following:

Somewhere in the file we show [link][ref]

<!-- somewhere else in the file -->
[ref]: http://www.example.com

This approach allows us to have less text when we typing, or reference links when finished the paragraph. Also, it's really useful when you want to use the same link few times per page.

Just copy first 8 ref-links from the README's footer.

[viktor-yakubiv]

My idea of tasks/README.md was to split tasks to categories like HTML, CSS, JavaScript, Application Design & Optimization, Pizza Application; and shortly explain each task and category.

On another side, create contents.md and explain course plan there.

I followed that way in #104. Now we have 2 similar files because we intersected in ideas. Which one do you suggest to follow?

[viktor-yakubiv]

Awesome!

[OleksiyRudenko]

@viktor-yakubiv

My idea of tasks/README.md was to split tasks to categories like HTML, CSS, JavaScript, Application Design & Optimization, Pizza Application; and shortly explain each task and category.

On another side, create contents.md and explain course plan there.

I followed that way in #104. Now we have 2 similar files because we intersected in ideas. Which one do you suggest to follow?

Let's keep both for now.

Let contents.md be main one. It is also available via a link from main README.md.

tasks/README.md is more technical, it offers easier navigation within tasks/ and also contains technical notes and describes detached tasks.