gsoc-2014

[GSoC Snippet] 07/08/2014

Aug 7, 2014 • Maciej (Developer Website)

Tags: news developers-page ruby jekyll

Share:

[doc] written 2 wiki articles about getting-started:
https://github.com/timvideos/getting-started/wiki/How-to-fork-and-run-own-getting-started%3F
https://github.com/timvideos/getting-started/wiki/From-change-to-generated-website---how-does-it-work%3F
[code] created repositories for jekyll plugins written by me:
https://github.com/pinoss/jekyll-github-plugins
https://github.com/pinoss/jekyll-iframe-generator
https://github.com/pinoss/jekyll-json-generator
https://github.com/pinoss/jekyll-category-tag-page-generator
https://github.com/pinoss/jekyll-opml-generator
https://github.com/pinoss/jekyll-page-url-tag
Now I need to write tests for all plugins.

What is next/my plans to the end of GSoC 2014? [STATUS]
1. Work with feedbook (add Google+ integration). 
- Currently there are no gems for pushing to Google+ streams, so I need to figure out something.
2. Deploy getting-started repository to code.timvideos.us
- Done.
3. Integrate planet with getting-started.
- Now it is time for discussion about that.
4. Extract my written Jekyll plugins into GitHub projects and share code with the others (and add some tests of course).
- Done, I need to write tests and more README files about my plugins.
5. Small CSS/HTML fixes and enhancements.
- Done.
6. Add Diagram to my GitHub Issues Filter.
- Done.
7. Add acceptance/integration tests for planet and getting-started website.
8. Investigate about planet generation (something does not work properly, website is not being updated every 1 hour, but once a day).
- Done.

9. Write documentation about getting-started generation process.
- Done.

Originally posted on pino IT / ruby / developer