leemcalilly

The signup page becomes /join and forces them to choose a membership option

As a user I would like to be able to choose my membership level on initial signup

Acceptance Criteria

• When I click "Join" from the homepage or visit /join, I'm give the option to choose the free or premium plan
• If I choose the free plan I'm taken through the normal signup process
• If I choose the premium plan, I'm taken through the normal signup process but at the end I share my credit card information and select either a monthly or annual billing plan and I am signed up as a premium user when signup is complete.
• Users can pay yearly and get a 10% discount or they can be billed monthly
• Billing automatically recurs either monthly or annually depending on the payment option they choose
• We send out a billing reminder 1 week before a recurring billing occurs
• Signup includes a list of features that each membership level affords the user

leemcalilly

Sections absolutely critical to re-launch

• User profiles and sign up (includes welcome page)
• Events
• Blog
• Partners
• Billing system
• Improved Design with new layout for mobile
• My Homepage
• Knowledge
• Questions (Ask and Answer)

leemcalilly

New Feature Ideas for 3.1 App

• Admin tool for exporting user data
• Private Messaging system
• Ability to follow content
• New admin panel layout with different design so it's clear you're logged in to manage the site
• New marketing layout with better design
• Polls
• Groups
• Notifications system

leemcalilly

Milestones

• Includes All Features Critical to Launching 3.1 App

Milestone Estimations

July 1 - Completed Items

• User profiles and sign up (includes welcome page)
• Events
• Blog
• Partners

leemcalilly

Partners should be able to notify people that they are now a partner to the CFOA and have a partner page.

As part of the partner page creation we should have it that a partner can:

1. Upload a list of email address to send an invite to
2. enter characteristics of users that they would like to notify (i.e. CFO with interest in tax in this geography)

This is just an idea and stream of thought. We would have to flush this out some more. This would be of value in at least three ways:

1. Sponsor value to gain quick visibility
2. Opportunity for referrals of new members

leemcalilly

AchieveNext Membership Model

Basic Member

• Can create and interact with all content
• Cost = free
• Eligible to attend events @ $30 per event

Executive Member

• Free access to events
• Cost = $350 per year or $34.95 monthly; recurring payments

leemcalilly

[AchieveX] (master) $ rake
/Users/lee/.rvm/rubies/ruby-1.9.2-p180/bin/ruby -S bundle exec rspec ./spec/abilities/ability_spec.rb ./spec/controllers/admin/base_controller_spec.rb ./spec/controllers/admin/blog/base_controller_spec.rb ./spec/controllers/admin/blog/comments_controller_spec.rb ./spec/controllers/admin/blog/images_controller_spec.rb ./spec/controllers/admin/blog/posts_controller_spec.rb ./spec/controllers/admin/partner_pages/admins_controller_spec.rb ./spec/controllers/admin/partner_pages_controller_spec.rb ./spec/controllers/autocomplete/blog_tags_controller_spec.rb ./spec/controllers/autocomplete/company_names_controller_spec.rb ./spec/controllers/autocomplete/partner_page_names_controller_spec.rb ./spec/controllers/autocomplete/user_names_controller_spec.rb ./spec/controllers/blog/comments_controller_spec.rb ./spec/controllers/blog/posts_controller_spec.rb ./spec/controllers/events_controller_spec.rb ./spec/controllers/job_titles_controller_spec.rb ./spec/controllers/knowledges_controller_spec.r

leemcalilly

  1) KnowledgesController GET :show rendering should render a different template for each type of knowledge
     Failure/Error: get :show, :id => knowledge.id
     undefined method `model_name' for NilClass:Class
     undefined method `model_name' for NilClass:Class
     # ./app/views/knowledges/_complementary_content.html.erb:4:in `_app_views_knowledges__complementary_content_html_erb__1143638891745883122_2204931120'
     # ./app/views/application/_complementary.html.erb:2:in `_app_views_application__complementary_html_erb__3571900282483915784_2204947540'
     # ./app/views/layouts/application.html.erb:22:in `_app_views_layouts_application_html_erb__3866301438023989637_2166619180'
     # ./spec/controllers/knowledges_controller_spec.rb:90:in `block (5 levels) in <top (required)>'
     # ./spec/controllers/knowledges_controller_spec.rb:88:in `each'
     # ./spec/controllers/knowledges_controller_spec.rb:88:in `block (4 levels) in <top (required)>'

leemcalilly

AchieveNext Staging Demo

July 8 @ 2pm EST

1. Overview of new layout and design approach
2. Explanation of our the new codebase is leaner and is going to be much easier to extend
3. Show the new login process as a new user
4. Demo other features using pre-populated content
5. Review the milestones and features essential to launch
6. Questions & Comments

Reference Materials

leemcalilly

<iframe src="http://player.vimeo.com/video/25762842?title=0&amp;byline=0&amp;portrait=0&amp;color=366c96" width="440" height="248" frameborder="0"></iframe>