Results for article-title

Leap language parser

A terminal feed reader with a fancy ui

Grabs page & article titles from lists of URLs contained in files passed in as arguments

The gem scrapes HTML of a URL to return the title and cover image which most likey represents the article. It also returns an array of tags.

chomchom extracts article's title, published_date, author, and fulltext. It also detects videos and audio for classifying the media type of a given page

This gem is to output the title and URL of the article that exists above Yahoo news at the current date and time.

Clever_title is a simple attempt to capitalise title's correctly. This includes keeping prepositions, articles or conjunctions lower case and keeping acronyms uppercase.

This gem generates a sane hyfen-separated text to serve as URL address to a page, based on a given string. It is ideal to generate a URL based on a title of a blog post or article, thus the name of the gem.

PageStructuredData gives Rails applications a small page object and view partial for rendering page titles, basic meta tags, Open Graph tags, Twitter card tags, breadcrumb JSON-LD, article and forum post JSON-LD, Person, Organization, and WebSite JSON-LD, and public interaction statistics.

{<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.

= dm-is-published This plugin makes it very easy to add different states to your models, like 'draft' vs 'live'. By default it also adds validations of the field value. Originally inspired by the Rails plugin +acts_as_publishable+ by &lt;b&gt;fr.ivolo.us&lt;/b&gt;. == Installation # Add GitHub to your RubyGems sources $ gem sources -a http://gems.github.com $ (sudo)? gem install kematzy-dm-is-published &lt;b&gt;NB! Depends upon the whole DataMapper suite being installed, and has ONLY been tested with DM 0.10.0 (next branch).&lt;/b&gt; == Getting Started First of all, for a better understanding of this gem, make sure you study the '&lt;tt&gt;dm-is-published/spec/integration/published_spec.rb&lt;/tt&gt;' file. ---- Require +dm-is-published+ in your app. require 'dm-core' # must be required first require 'dm-is-published' Lets say we have an Article class, and each Article can have a current state, ie: whether it's Live, Draft or an Obituary awaiting the death of someone famous (real or rumored) class Article include DataMapper::Resource property :id, Serial property :title, String ...&lt;snip&gt; is :published end Once you have your Article model we can create our Articles just as normal Article.create(:title =&gt; 'Example 1') The instance of &lt;tt&gt;Article.get(1)&lt;/tt&gt; now has the following things for free: * a &lt;tt&gt;:publish_status&lt;/tt&gt; attribute with the value &lt;tt&gt;'live'&lt;/tt&gt;. Default choices are &lt;tt&gt;[ :live, :draft, :hidden ]&lt;/tt&gt;. * &lt;tt&gt;:is_live?, :is_draft? or :is_hidden?&lt;/tt&gt; methods that returns true/false based upon the state. * &lt;tt&gt;:save_as_live&lt;/tt&gt;, &lt;tt&gt;:save_as_draft&lt;/tt&gt; or &lt;tt&gt;:save_as_hidden&lt;/tt&gt; converts the instance to the state and saves it. * &lt;tt&gt;:publishable?&lt;/tt&gt; method that returns true for models where &lt;tt&gt;is :published &lt;/tt&gt; has been declared, but &lt;b&gt;false&lt;/b&gt; for those where it has not been declared. The Article class also gets a bit of new functionality: Article.all(:draft) =&gt; finds all Articles with :publish_status = :draft Article.all(:draft, :author =&gt; @author_joe ) =&gt; finds all Articles with :publish_status = :draft and author == Joe Todo Need to write more documentation here.. == Usage Scenarios In a Blog/Publishing scenario you could use it like this: class Article ...&lt;snip&gt;... is :published :live, :draft, :hidden end Whereas in another scenario - like in a MenuItem model for a Restaurant - you could use it like this: class MenuItem ...&lt;snip&gt;... is :published :on, :off # the item is either on the menu or not end == RTFM As I said above, for a better understanding of this gem/plugin, make sure you study the '&lt;tt&gt;dm-is-published/spec/integration/published_spec.rb&lt;/tt&gt;' file. == Errors / Bugs If something is not behaving intuitively, it is a bug, and should be reported. Report it here: http://github.com/kematzy/dm-is-published/issues == Credits Copyright (c) 2009-07-11 [kematzy gmail com] Loosely based on the ActsAsPublishable plugin by [http://fr.ivolo.us/posts/acts-as-publishable] == Licence Released under the MIT license.

No description provided.

No description provided.