Removed unneeded references to guides.

Author: peakpg

Gemfile

@@ -7,8 +7,6 @@ gem "mysql"
 
 # Gem Environments
 group :development do
-# gem 'ruby-debug19'
- gem 'RedCloth' # For guides
  gem 'yard'
  gem 'bluecloth' # For YARD
 end

README.markdown

@@ -31,7 +31,7 @@ BrowserCMS can create websites that can work in any browser, depending on how de
 The next releases will be aimed at tightening up the admin for both Safari and IE7+. We will not be supporting the admin UI for IE6, or other browsers not explicitly listed above.
 
 ## Getting Started
-Before you can use BrowserCMS, you will need to install the gem. See the Getting Started guide at http://guides.browsercms.org/getting_started.html, or packaged with this source code (under doc/guides/html/getting_started.html)
+Before you can use BrowserCMS, you will need to install the gem. See the [Getting Started](https://github.com/browsermedia/browsercms/wiki/Getting-Started) guide.
 
 ## License
 BrowserCMS is released under a LGPL license, and is copyright 1998-2011 BrowserMedia. The complete copyright can be found in COPYRIGHT.txt, and copy of the license can be found in LICENSE.txt.
@@ -40,9 +40,9 @@ BrowserCMS is released under a LGPL license, and is copyright 1998-2011 BrowserM
 ## Documentation
 The user documentation and guides for this version of the application can be found at:
 
-1. http://guides.browsercms.org/index.html - User guides and manuals that cover the features and general functionality of the project. (Found locally at doc/guides/html/index.html)
-2. http://api.browsercms.org/index.html - The RDoc API documenation (locally at doc/app/index.html)
-3. http://wiki.github.com/browsermedia/browsercms - The project wiki
+1. [Guides and Wiki](http://wiki.github.com/browsermedia/browsercms)
+2. [API Docs](http://rubydoc.info/gems/browsercms/)
+
 
 ## Working on the core project source
 If you want to experiment with the source code, the BrowserCMS project can bootstrap itself as a web application. This allows developers who want to contribute to the project to easily alter and test changes. To run the application itself, do the following:

doc/release_notes.txt

@@ -1,5 +1,12 @@
-v3.3.0.beta
-=====
+v3.3.0
+======
+
+* New commandline syntax described here: https://github.com/browsermedia/browsercms/wiki/Getting-Started
+* Removed guides from core project in favor of moving to Github's wiki
+* Updated API docs so YARD is being used, and hosted at http://rubydoc.info/gems/browsercms/
+
+ v3.3.0.beta
+===========
 
 The long awaited Rails 3 release. We have completely reworked BrowserCMS to work with Rails 3 and Ruby 1.9.2. This release is a 'beta', so that folks can start testing against it. This is especially important for module authors, as any modules need to be upgraded to work with Rails 3 as well. Our next steps will be to collect feedback for a final 3.3.0 release/release candidate. If we can get most of the 'core' modules (News, Blog, etc) updated and working, that will likely mean a final 3.3.0 release.
 

lib/tasks/cms.rake

@@ -22,37 +22,8 @@ namespace :test do
  end
 end
 
-# When Jeweler builds the gem, make sure the guides are also rebuilt.
-#task :build => ['cms:guides']
 
 namespace :cms do
- 
- desc "Generate guides for the CMS"
- task :guides do
- require 'rubygems'
-
- gem "actionpack", '>= 2.3'
- require "action_controller"
- require "action_view"
-
- gem 'RedCloth', '>= 4.1.1'
- require 'redcloth'
-
- $: << File.join(File.dirname(__FILE__), '../../doc/guides')
-
- module CmsGuides
- autoload :Generator, "cms_guides/generator"
- autoload :Indexer, "cms_guides/indexer"
- autoload :Helpers, "cms_guides/helpers"
- autoload :TextileExtensions, "cms_guides/textile_extensions"
- autoload :Levenshtein, "cms_guides/levenshtein"
- end
-
- RedCloth.send(:include, CmsGuides::TextileExtensions)
-
- CmsGuides::Generator.new.generate
-
- end
 
  desc "Rebuild the browsercms gem locally and install it, Useful for testing releases."
  task :gem => ["browsercms.gemspec", :build, :install]

todo_list.txt

@@ -1,13 +1,11 @@
 Start with:
 
- Guides don't build. (Look @ Rails 3)
 
 Open Issues
 ===========
 * SQLite3 #<ActiveRecord::StatementInvalid: Could not find table 'file_blocks'> warnings
 * Mysql2 throws exceptions during generators (similar reason to previous)
 * rake db:install - Get warnings about db already existing (with SQLite3)
-* Can we/should we convert the guides to Github wiki pages? Might be less work to maintain, along with more flexibility. Keep old URLs/redirect them.
 
 Gems to Publish (once its live)
 ============