Add some initial content to the home-page based on our original proposal

This commit is contained in:
R. Tyler Croy 2014-10-20 18:26:08 -07:00
parent 221ed11958
commit e828e54146
7 changed files with 183 additions and 74 deletions

2
.gitignore vendored
View File

@ -1,2 +1,4 @@
_site/
.sass-cache/
*.sw*
.ruby-*

3
Gemfile Normal file
View File

@ -0,0 +1,3 @@
source 'https://rubygems.org'
gem 'jekyll'

70
Gemfile.lock Normal file
View File

@ -0,0 +1,70 @@
GEM
remote: https://rubygems.org/
specs:
blankslate (2.1.2.4)
celluloid (0.16.0)
timers (~> 4.0.0)
classifier-reborn (2.0.1)
fast-stemmer (~> 1.0)
coffee-script (2.3.0)
coffee-script-source
execjs
coffee-script-source (1.8.0)
colorator (0.1)
execjs (2.2.2)
fast-stemmer (1.0.2)
ffi (1.9.6)
hitimes (1.2.2)
jekyll (2.4.0)
classifier-reborn (~> 2.0)
colorator (~> 0.1)
jekyll-coffeescript (~> 1.0)
jekyll-gist (~> 1.0)
jekyll-paginate (~> 1.0)
jekyll-sass-converter (~> 1.0)
jekyll-watch (~> 1.1)
kramdown (~> 1.3)
liquid (~> 2.6.1)
mercenary (~> 0.3.3)
pygments.rb (~> 0.6.0)
redcarpet (~> 3.1)
safe_yaml (~> 1.0)
toml (~> 0.1.0)
jekyll-coffeescript (1.0.1)
coffee-script (~> 2.2)
jekyll-gist (1.1.0)
jekyll-paginate (1.1.0)
jekyll-sass-converter (1.2.1)
sass (~> 3.2)
jekyll-watch (1.1.1)
listen (~> 2.7)
kramdown (1.4.2)
liquid (2.6.1)
listen (2.7.11)
celluloid (>= 0.15.2)
rb-fsevent (>= 0.9.3)
rb-inotify (>= 0.9)
mercenary (0.3.4)
parslet (1.5.0)
blankslate (~> 2.0)
posix-spawn (0.3.9)
pygments.rb (0.6.0)
posix-spawn (~> 0.3.6)
yajl-ruby (~> 1.1.0)
rb-fsevent (0.9.4)
rb-inotify (0.9.5)
ffi (>= 0.5.0)
redcarpet (3.2.0)
safe_yaml (1.0.4)
sass (3.4.6)
timers (4.0.1)
hitimes
toml (0.1.2)
parslet (~> 1.5.0)
yajl-ruby (1.1.0)
PLATFORMS
ruby
DEPENDENCIES
jekyll

45
_layouts/default.html Normal file
View File

@ -0,0 +1,45 @@
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8'>
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<meta name="description" content="FOSDEM &lt;3 Ruby : The #1 Ruby language devroom at FOSDEM">
<link rel="stylesheet" type="text/css" media="screen" href="stylesheets/stylesheet.css">
<title>FOSDEM &lt;3 Ruby</title>
</head>
<body>
<!-- HEADER -->
<div id="header_wrap" class="outer">
<header class="inner">
<img src="images/ruby-heart.png" align="left" width="100" style="border: 0; box-shadow: 0 0 0;"/>
<a id="forkme_banner" href="https://github.com/fosdem-ruby">View on GitHub</a>
<h1 id="project_title">FOSDEM &lt;3 Ruby</h1>
<h2 id="project_tagline">The #1 Ruby language devroom at FOSDEM</h2>
</header>
</div>
<!-- MAIN CONTENT -->
<div id="main_content_wrap" class="outer">
<section id="main_content" class="inner">
{{content}}
</section>
</div>
<!-- FOOTER -->
<div id="footer_wrap" class="outer">
<footer class="inner">
<p>Published with <a href="http://pages.github.com">GitHub Pages</a></p>
</footer>
</div>
</body>
</html>

BIN
images/ruby-heart.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

View File

@ -1,74 +0,0 @@
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8'>
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<meta name="description" content="FOSDEM &lt;3 Ruby : The #1 Ruby language devroom at FOSDEM">
<link rel="stylesheet" type="text/css" media="screen" href="stylesheets/stylesheet.css">
<title>FOSDEM &lt;3 Ruby</title>
</head>
<body>
<!-- HEADER -->
<div id="header_wrap" class="outer">
<header class="inner">
<a id="forkme_banner" href="https://github.com/fosdem-ruby">View on GitHub</a>
<h1 id="project_title">FOSDEM &lt;3 Ruby</h1>
<h2 id="project_tagline">The #1 Ruby language devroom at FOSDEM</h2>
</header>
</div>
<!-- MAIN CONTENT -->
<div id="main_content_wrap" class="outer">
<section id="main_content" class="inner">
<h3>
<a name="welcome-to-github-pages" class="anchor" href="#welcome-to-github-pages"><span class="octicon octicon-link"></span></a>Welcome to GitHub Pages.</h3>
<p>This automatic page generator is the easiest way to create beautiful pages for all of your projects. Author your page content here using GitHub Flavored Markdown, select a template crafted by a designer, and publish. After your page is generated, you can check out the new branch:</p>
<pre><code>$ cd your_repo_root/repo_name
$ git fetch origin
$ git checkout gh-pages
</code></pre>
<p>If you're using the GitHub for Mac, simply sync your repository and you'll see the new branch.</p>
<h3>
<a name="designer-templates" class="anchor" href="#designer-templates"><span class="octicon octicon-link"></span></a>Designer Templates</h3>
<p>We've crafted some handsome templates for you to use. Go ahead and continue to layouts to browse through them. You can easily go back to edit your page before publishing. After publishing your page, you can revisit the page generator and switch to another theme. Your Page content will be preserved if it remained markdown format.</p>
<h3>
<a name="rather-drive-stick" class="anchor" href="#rather-drive-stick"><span class="octicon octicon-link"></span></a>Rather Drive Stick?</h3>
<p>If you prefer to not use the automatic generator, push a branch named <code>gh-pages</code> to your repository to create a page manually. In addition to supporting regular HTML content, GitHub Pages support Jekyll, a simple, blog aware static site generator written by our own Tom Preston-Werner. Jekyll makes it easy to create site-wide headers and footers without having to copy them across every page. It also offers intelligent blog support and other advanced templating features.</p>
<h3>
<a name="authors-and-contributors" class="anchor" href="#authors-and-contributors"><span class="octicon octicon-link"></span></a>Authors and Contributors</h3>
<p>You can <a href="https://github.com/blog/821" class="user-mention">@mention</a> a GitHub username to generate a link to their profile. The resulting <code>&lt;a&gt;</code> element will link to the contributor's GitHub Profile. For example: In 2007, Chris Wanstrath (<a href="https://github.com/defunkt" class="user-mention">@defunkt</a>), PJ Hyett (<a href="https://github.com/pjhyett" class="user-mention">@pjhyett</a>), and Tom Preston-Werner (<a href="https://github.com/mojombo" class="user-mention">@mojombo</a>) founded GitHub.</p>
<h3>
<a name="support-or-contact" class="anchor" href="#support-or-contact"><span class="octicon octicon-link"></span></a>Support or Contact</h3>
<p>Having trouble with Pages? Check out the documentation at <a href="http://help.github.com/pages">http://help.github.com/pages</a> or contact <a href="mailto:support@github.com">support@github.com</a> and well help you sort it out.</p>
</section>
</div>
<!-- FOOTER -->
<div id="footer_wrap" class="outer">
<footer class="inner">
<p>Published with <a href="http://pages.github.com">GitHub Pages</a></p>
</footer>
</div>
</body>
</html>

63
index.md Normal file
View File

@ -0,0 +1,63 @@
---
layout: default
---
The Ruby devroom at [FOSDEM](http://fosdem.org) is a focused developer room
around the Ruby programming language and the open source projects which
implement it. While the Ruby community does have a number of regional
conferences devoted to its use, opportunities for those interested in the "how
it works" of Ruby interpreters and virtual machines are practically
non-existent. The goal of this developer room is to discuss:
* The current state of the Ruby language
* Techniques employed by various VMs and their effectiveness
* Upcoming Ruby language features, and the challenges/benefits that they provide
* Tools and practices used to certify Ruby language conformity and performance
* Costs and Opportunities provided by the multitude of implementations
### Involved projects
* [JRuby](http://jruby.org)
* [Ruby (MRI)](https://www.ruby-lang.org/)
* [RubyTruffle](http://www.chrisseaton.com/rubytruffle/)
* [Rubinius (Ruby on Ruby)](http://rubini.us/)
## Why we're here
While many Ruby developers attend FOSDEM, the Ruby open source community has
generally been underrepresented in the technical content of the event. With the
Ruby devroom not only would the Ruby community become more plugged into the
FOSDEM experience, but FOSDEM would be hosting Ruby-oriented content that is
both unique and very technical. Considering the broad interest in dynamic and
interpreted languages, the Ruby devroom will also provide compelling technical
content interesting to members of the Python, Perl, JavaScript, Smalltalk, LLVM
and Java communities. There is quite some interest in the topic, as the
overcrowded Java dev room if [Charles Oliver
Nutter's](https://github.com/headius) talk on JRuby in the FOSDEM 2014 Free
Java devroom is any indication.
Considering the number of notable Ruby implementations, listed below, there
should be more than enough highly interesting and technical content!
* Ruby (MRI, the original C-based VM)
* JRuby (Ruby on the JVM)
* Rubinius (Ruby on Ruby)
* Topaz (Ruby on RPython, the toolkit that PyPy built)
* RubyTruffle (JRuby using Oracle's Truffle compiler)
* RubyMotion (Ruby on top of Apple's Objective-C/Cocoa foundation)
* Maglev (Ruby on the GemStone Smalltalk VM)
* Opal (A working Ruby to JavaScript transpiler)
## Who we are
* [R. Tyler Croy](https://github.com/rtyler) - JRuby/Jenkins hacker
* [Charles Nutter](https://github.com/headius) - JRuby core hacker
* [Laurent Sansonetti](https://twitter.com/lrz) - RubyMotion (oolchain for iOS/OS X development in Ruby) developer
* [Florian Gilcher](https://twitter.com/Argorak) - Ruby Berlin e.V. (European non-profit) committee member, organizer, hacker