codelitt / launchpage-rails

Prelaunch MVP landing page (open source alternative to LaunchRock) to get you going quickly so you can focus on your product. Written in Ruby and Rails 4.2 with email collection for two or more user types, social sharing after user signs in, and automailer to new user.

WARNING

This repository has been discontinuated, our current website code is stored on: https://github.com/codelittinc/codelitt-v2

Codelitt

Description

Awesome company website!

Installation

• Create gemset rvm use 2.1.1@codelitt --create

• Install gems bundle install

• Run the server rails server

• Watch stylesheets for changes compass watch

Setup

• Breakpoint: http://breakpoint-sass.com/
  • For easier media queries
• Compass: http://compass-style.org/
  • To modularize our scss using partials.
• Bootstrap: http://getbootstrap.com/
  • Use bootstrap for easier css and responsive design.

Stylesheets

• We are using SASS(SCSS) for stylesheets.
• They are stored in the public/sass folder and compiled to CSS in the public/stylesheets folder.
• The stylesheet folder is not committed in order to keep the repo DRY.

Partials

• We are using partials for each element of the page.
• All partials are called in application.scss.
• The layout.erb then links to the compiled application.css.

Media Queries

Media queries are simple using the breakpoint gem.

Variables

Use the same values as bootstrap for media queries.

  $sm: 768px;
  $md: 992px;
  $lg: 1200px;

Example:

Using breakpoint we can set the height to auto if the page width is bigger than 768px which is our $sm value.

   .codelitt-big {
      margin: -20px 0 0;
      padding: 0;
      width: 100%;
      height: 400px;

      background: $codelitt-dark;

      @include breakpoint($sm) {
        height: auto;
    }

launchpage-rails's Issues

Enhancement: Add pre designed themes to plug and play

Include a list of already available bootstrap themes into the app, and let the user just key in the theme name and deploy.

Unit and integration tests coverage

Rspec + Capybara please

Add post signup surveys to give ability to test market fit

@Lockyy has already built these for some of the startups testing market fit.

Update project to rails 5

Currently the project uses Rails 4, we need to update it to Rails 5.

The "Export to CSV" as coming soon in README.md

What was meant on README.md file in:

When in UserController already have the method to export as CSV?

app/controllers/users_controller.rb

Ideas for: post signup survey and questionaire

What is the best way to gather more information from the possible users, considering that we need it simple and fast for the startup customize.

Maybe add a link after the subscribe for a survey and the startup implement his own way( The cheapest I think is google form)

Project description typo

The project description says "Prelaunch app written in Ruby and Rails 4...". The Gemfile uses Rails 3.2.

[discuss] Sinatra vs. Rails

Rails is pretty heavy for what this needs to do, however, originally I made the call for Rails just because it had most of the things needed. I don't really intend to migrate (mostly time). I just want to open an issue to allow people to discuss because I know there will be some comments on the approach I took.

Pros of sticking with Rails:

• Rails is common environment
• Easy for most people to spin up quickly (original goal of the project)
• It's already in Rails (dev time)
• May be easier for people to extend

Cons of sticking with Rails:

• One could argue that this is overkill
• Bad example of code simplicity.

Create CI and CodeClimante coverage from the main repo

Currently the CI and Codeclimate coverage is configured for @kaiomagalhaes fork. Need to configure it to this repo. And add automatic CI for every Pull request.

https://codeclimate.com/github/kaiomagalhaes/launchpage-rails/coverage

Update to Rails 4

I started work on this on branch rails4

Hasn't been tested or worked on though since then.

Add a "purchase flow" to test if users will click through to buy

The real test for many startups is will people pay for this. We should add a fake purchase flow in which the user would click through to purchase and we just show an error that it is currently not accepting orders but can still track how many people 'intended' to purchase.