Results for blogs-example

A bootstrap example blog theme for Jekyll.

Jekyll Archive Generator creates a set of archive pages for a Jekyll website. Oddly, Jekyll doesn't include a date-based archive for posts out of the box. For example, if you have a permalink structure like `blog/2014/01/01/title, URL hacking won't work because going to `blog/2014` will return 404 Page Not Found. Jekyll Archive Generator fixes that by generating all the necessary archive pages for each part your blog URL structure.

Example implementation to test my experiment on live unit testing. Make sure to check the blog post here : http://zisismaras.me/general/2015/05/01/exploring-live-unit-tests.html and the github repo.

A Jekyll filter to truncate HTML to a specified number of words. The Liquid truncatewords filter can't operate on HTML because it isn't aware of tags. But Jekyll blog posts usually contain HTML, so this makes it difficult to, for example, use the first 50 words of a blog post as the preview. jekyll_html_truncatewords solves that problem. It works the same as truncatewords, but it is aware of HTML tags so it counts words correctly within HTML and won't break HTML.

{<img src="https://secure.travis-ci.org/socialcast/socialcast-shoulda-ext.png?branch=master" alt="Build Status" />}[http://travis-ci.org/socialcast/socialcast-shoulda-ext] = Socialcast Shoulda Extensions Adds new matchers and functionality to the shoulda test library = Installation In your Gemfile: group :test do gem 'socialcast_shoulda_ext', :git => 'git@github.com:socialcast/socialcast-shoulda-ext.git', :require => 'shoulda_ext' end If you want to include the trigger_callbacks matcher, also add the following to your test helper: ShouldaExt::Matchers::TriggerCallbackMatcher.attach_active_record_callback_hooks! = Matchers == RecordCountChangeMatcher Test if the count for a model has changed, and by how much. Requires the context_with_matcher_before_hooks patch, which is included by default. Provides the following matcher methods: - create_record(klass_or_symbol) Alias for change_record_count.for(klass_or_symbol).by(1) - create_records(klass_or_symbol, amount) Alias for change_record_count.for(klass_or_symbol).by(amount) - destroy_record(klass_or_symbol) Alias for change_record_count.for(klass_or_symbol).by(-1) - destroy_records(klass_or_symbol, amount) Alias for change_record_count.for(klass_or_symbol).by(-amount) - change_record_count Tests the difference in record count before and after the current setup/subject block Can be used with the follow methods: - for(klass_or_symbol) Provides the class which the test is being performed on. Can be a constant or a symbol - by(amount) Provides an expected difference for the number of records for the specified class. Excluding this number will allow the matcher to check for any difference Examples: context "creating a blog article" do context "with good parameters" do setup do post :create, :blog => {:title => 'my blog post', :body => 'Ipsum lorem...'} end should create_record :blog end context "without a body" do setup do post :create, :blog => {:title => 'my blog post' } end should_not create_record Blog end end == RespondWithJson Check if the controller's response is json Examples: context ":index.json" do setup do get :index, :format => 'json' end # Just check to see that the response was json should respond_with_json # Evaluate the hash produced by the json yourself should respond_with_json { |json| json.first['blog']['title'] == 'blog post 1'} # Provide an exact match should respond_with_json.exactly(['blog' => {'id' => 1, 'title' => 'blog post 1'}]) # Provide an exact match with a block should response_with_json.exactly{ |json| JSON.parse(Blog.all.to_json)} end context ":index.html" do setup do get :index end # or the negation should_not respond_with_json end == TriggerCallbackMatcher Test if create, update, destroy, or save callbacks were triggered. Requires running ShouldaExt::Matchers::TriggerCallbackMatcher.attach_active_record_callback_hooks! in your test suite in order to work properly. Examples: context "doing nothing to a record" do subject { Blog.new :title => 'blog title' } should_not trigger_callbacks end context "creating a record" do subject { Blog.create! :title => 'blog title' } should trigger_callbacks.for :create should_not trigger_callbacks.for :update, :destroy end = Integrations Currently only integrates with test/unit. RSpec support to come. = Shoulda Extensions == ContextWithMatcherBeforeHooks Adds the ability to define a 'before' method on any method which will be run before each context's setup/subject block. Used by RecordCountChangeMatcher to record the number of records before the tested operation takes place.

Library for building websites from a tree of Textile files. Cut your Textile into a nice website! Makas generates websites from a tree of Textile files. It does not try to deduce any meaning from the structure of that tree (i.e. where files are in the directory hierarchy), but can generate a blog from a directory of files named a certain way, if enabled. See doc/examples/singe-blog.rb for how that can be done. Multiple blogs, RSS feed generation and copying over static files are supported.

Basic tool which provides feature of generating tokens which can be used in url for identifying resource(uniquely of uniquely within a scope) instead of :id. Just add another field which starts with _bu_ of one or many existing fields to make it all happen. Example: For a blog post, if you have a 'title' field and want to beautify and use it instead of :id add another field like '_bu_title' and now modify routes and application to refer and fetch resource from '_bu_title' field.

Rethoth is a simple to understand, run and maintain Ruby blogging engine. Rethoth is written in Ruby and is based on the Ramaze web framework and the Sequel database toolkit. Rethoth is a modern port, to 2017, of the original Thoth created by @ryangrove. Rethoth demonstrates how to easily build a useful MVC-style app in Ruby without having to deal directly with meta-programming and DSL magic. Rethoth is an example of how to build a web application in Ruby without the need to learn Rails and ActiveRecord. Rethoth is ideal for newcomers to Ruby who have experience with other web frameworks and want to quickly appreciate the language and become productive with it.

Mainly the product of messing around, this gem comprises Ruby code for a few useful &quot;Amazon Hacks&quot; -- common techniques for manipulating Amazon product URLs and Images. This is mainly useful if you find yourself creating a site where you might link to Amazon product pages and display images for them. Examples of this might include: * Social consumption sites like {All Consuming}[http://www.allconsuming.net/] * Blogs or tumbleblogs with book/music/etc. reviews * Normalizing Amazon links or create associate IDs This GEM is NOT related to using the Amazon Web Services and there is already an excellent gem for that if you need more heavy-duty use of the Amazon website (this gem does not even communicate with Amazon at all). Also, note this gem is meant in the spirit of fun hackery. You can use it to create interesting images from Amazon on demand, but if you are going to use it on a serious website, please consider caching and attributing that image to Amazon (I also have no idea what the official legal policy for using Amazon's book images is). And of course, do not even consider using this for fraud. It is possible to generate &quot;20% off&quot; or &quot;Look Inside!&quot; badges on Amazon images, but this gem does not support that since I can not think of any reason why outside sites would use that. == FEATURES/PROBLEMS:

Germinate is a tool for writing about code. With Germinate, the source code IS the article. For example, given the following source code: # #!/usr/bin/env ruby # :BRACKET_CODE: &lt;pre&gt;, &lt;/pre&gt; # :PROCESS: ruby, "ruby %f" # :SAMPLE: hello def hello(who) puts "Hello, #{who}" end hello("World") # :TEXT: # Check out my amazing program! Here's the hello method: # :INSERT: @hello:/def/../end/ # And here's the output: # :INSERT: @hello|ruby When we run the &lt;tt&gt;germ format&lt;/tt&gt; command the following output is generated: Check out my amazing program! Here's the hello method: &lt;pre&gt; def hello(who) puts "Hello, #{who}" end &lt;/pre&gt; And here's the output: &lt;pre&gt; Hello, World &lt;/pre&gt; To get a better idea of how this works, please take a look at link:examples/basic.rb, or run: germ generate &gt; basic.rb To generate an example article to play with. Germinate is particularly useful for writing articles, such as blog posts, which contain code excerpts. Instead of forcing you to keep a source code file and an article document in sync throughout the editing process, the Germinate motto is "The source code IS the article". Specially marked comment sections in your code file become the article text. Wherever you need to reference the source code in the article, use insertion directives to tell Germinate what parts of the code to excerpt. An advanced selector syntax enables you to be very specific about which lines of code you want to insert. If you also want to show the output of your code, Germinate has you covered. Special "process" directives enable you to define arbitrary commands which can be run on your code. The output of the command then becomes the excerpt text. You can define an arbitrary number of processes and have different excerpts showing the same code as processed by different commands. You can even string processes together into pipelines. Development of Germinate is graciously sponsored by Devver, purveyor of fine cloud-based services to busy Ruby developers. If you like this tool please check them out at http://devver.net.

Germinate is a tool for writing about code. With Germinate, the source code IS the article. For example, given the following source code: # #!/usr/bin/env ruby # :BRACKET_CODE: &lt;pre&gt;, &lt;/pre&gt; # :PROCESS: ruby, &quot;ruby %f&quot; # :SAMPLE: hello def hello(who) puts &quot;Hello, #{who}&quot; end hello(&quot;World&quot;) # :TEXT: # Check out my amazing program! Here's the hello method: # :INSERT: @hello:/def/../end/ # And here's the output: # :INSERT: @hello|ruby When we run the &lt;tt&gt;germ format&lt;/tt&gt; command the following output is generated: Check out my amazing program! Here's the hello method: &lt;pre&gt; def hello(who) puts &quot;Hello, #{who}&quot; end &lt;/pre&gt; And here's the output: &lt;pre&gt; Hello, World &lt;/pre&gt; To get a better idea of how this works, please take a look at link:examples/basic.rb, or run: germ generate &gt; basic.rb To generate an example article to play with. Germinate is particularly useful for writing articles, such as blog posts, which contain code excerpts. Instead of forcing you to keep a source code file and an article document in sync throughout the editing process, the Germinate motto is &quot;The source code IS the article&quot;. Specially marked comment sections in your code file become the article text. Wherever you need to reference the source code in the article, use insertion directives to tell Germinate what parts of the code to excerpt. An advanced selector syntax enables you to be very specific about which lines of code you want to insert. If you also want to show the output of your code, Germinate has you covered. Special &quot;process&quot; directives enable you to define arbitrary commands which can be run on your code. The output of the command then becomes the excerpt text. You can define an arbitrary number of processes and have different excerpts showing the same code as processed by different commands. You can even string processes together into pipelines. Development of Germinate is graciously sponsored by Devver, purveyor of fine cloud-based services to busy Ruby developers. If you like this tool please check them out at http://devver.net.

Diff and patch tables

No description provided.

No description provided.

No description provided.

No description provided.