Sitemap.xml rake task

100%

Sitemap.xml rake task

✓ Published0🌍 Public

Last edited Mar 23, 2009

Created on Mar 23, 2009

This example shows a Ruby rake task that programmatically generates a sitemap.xml file for a website. It first assembles a list of page URLs from static routes, database categories, and photos, then builds a valid XML document using the Nokogiri library’s XML builder. The code iterates over all Category and Photo records via ActiveRecord-style queries, constructs full URLs with a hardcoded domain, and writes the resulting XML to the public directory. It demonstrates a common pattern for dynamic sitemap generation in a Merb environment, with the final output counting the number of URLs saved.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 77879

This example demonstrates a Flickr photo management system built with Ruby on Merb, using the Flickr API to fetch, validate, and update photo metadata. It shows a batch workflow that first retrieves photos by category tags, then verifies their existence and tags on Flickr, and finally updates stored attributes like title, description, and image sizes. The code relies on Flickr’s `flickr_photo` objects and the Merb ORM for database persistence, with tasks chained via Rake. The visualization highlights the procedural data-sync logic, emphasizing error handling and association management between photos and categories.

DDylanFM

62% match

Loading thumbnail…

Gist f72a3553521c158f0eb0dccbe774455e

This example demonstrates a web scraper that extracts detailed trail information from a hiking website. It shows how structured data can be programmatically retrieved from HTML pages, specifically pulling out features, overview, and description sections. The code uses the Nokogiri library to parse the document and XPath queries to locate the relevant heading elements. After extracting each section, it cleans the text by removing newlines and excess whitespace. The scraper returns a hash containing the three descriptive fields, making the data readily accessible for further processing or visualization.

WWill Carter

57% match

Loading thumbnail…

Gist 5ea363dfe112d08281a8c89a3f31bcff

This example scrapes trail data from a website, extracting features, overview, and description sections into a structured hash. It uses Nokogiri to parse the HTML and XPath queries to locate the relevant headings and their adjacent content, cleaning the text by removing line breaks. The code demonstrates a straightforward scraping pattern for capturing semantic sections, though it does not include visualization logic or rendering libraries. The data source is a single trail page URL, and the output is a formatted description ready for further processing or display.

WWill Carter

56% match

Loading thumbnail…

Gist 360936

This example demonstrates a Tumblr API client in Ruby, showing how to fetch and model blog posts through a `Post` class that wraps raw post data in a `Hashie::Mash`. The code reveals the workflow of querying the Tumblr API via HTTParty, with support for pagination, post-type filtering, and direct lookup by ID. The visualization highlights the library’s role as an interface layer, not a rendering tool, as it contains no charting or drawing logic—instead, it focuses on data retrieval and object mapping. The example is purely code-based, with no visual output, emphasizing the API’s data-access patterns rather than graphical representation.

DDylanFM

53% match

Loading thumbnail…

Gist da1dc31d6c595b04c7e7b351290d7266

This example shows an unfinished Ruby scraper class, `HikingProject::Scraper`, which is intended to fetch trail data from an API and scrape full trail details, but currently contains only empty method stubs. The code defines two methods: `get_trails_from_api` to retrieve a list of trails and `scrape_full_detail` to populate features, overview, and description for a specific trail. No visualization or rendering logic is present; the gist merely outlines the data-collection layer without any concrete libraries, APIs, or data sources implemented. The rendering approach is absent, as the file does not yet perform any actual scraping or data processing.

WWill Carter

53% match

Loading thumbnail…

Gist 86435

This example demonstrates a command-line tool for capturing full-page screenshots of websites using MacRuby and WebKit. It shows a configurable web capture system that loads a URL, optionally resizes the viewport, waits for a specified delay, and saves the rendered page as a PNG. The code relies on the WebKit framework’s WebView and frame load delegation, alongside NSBitmapImageRep to rasterize the view’s content. Users specify options like width, height, output filename, and delay via Ruby’s OptionParser.

CCaged

52% match

Loading thumbnail…

Gist 28617

This example uses a Ruby script to capture full-page screenshots of websites by automating a hidden WebView. It first loads a given URL, waits for the page to finish rendering, then saves the rendered content as a PNG file. The code leverages MacRuby’s WebKit framework, specifically `WebView` and `NSBitmapImageRep`, to render and capture the page. It supports optional width, height, delay, and output filename parameters, with a default width of 1024 pixels and a fallback to ruby-lang.org if no URL is provided.

CCaged

51% match

Loading thumbnail…

{$title}

This example demonstrates a minimal XQuery web application for the Corpus Baudelaire project, serving static XHTML pages and dynamic poem routes. It shows how RESTXQ annotations declare endpoints for the root path, an about page, a credits page, and a parameterized poem URL, with each route returning a simple HTML document via a shared display function. The code relies on the RESTXQ API for request routing and the XQuery standard library for string concatenation and element construction, though it renders no actual data visualization.

CCliffordAnderson

51% match