- Overview of new layout and design approach
- Explanation of our the new codebase is leaner and is going to be much easier to extend
- Show the new login process as a new user
- Demo other features using pre-populated content
- Review the milestones and features essential to launch
- Questions & Comments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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)>' |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[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 |
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:
- Upload a list of email address to send an invite to
- 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:
- Sponsor value to gain quick visibility
- Opportunity for referrals of new members
As a user I would like to be able to choose my membership level on initial signup
- 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
- Series of survey questions that CFO's take
- can people opt into a this
- would like to have some sort of integration
- data feed into a group
- look into using a 3rd party API for this (maybe google docs)
- groups need to be private and public
- concept of being able to fill out parameters that would be for the notifications that you want; for instance partners would need to be able to send out emails.