balanced / balanced-dashboard Goto Github PK

If you look at sites like Authorize.net or RapidSSL you see badges like these:

http://www.dmvcheatsheets.com/assets/misc/rapidssl_ssl_certificate-b35840528d8922a9f456056e134775ca.gif

and http://www.authorize.net/solutions/merchantsolutions/onlinemerchantaccount/seal/

you guys only have this - http://www.quora.com/Balanced/I-am-in-the-process-of-adding-Balanced-to-my-site-and-want-to-use-the-Balanced-logo-Is-that-allowed

Which displays nothing to the user conveying security or trust. I actually, personally, have no idea what type of SSL or security is in effect when I use balanced.js for PCI compliance and know from experience that a series of "seals" or icons that we can display on our sites that say things like "secure" or "128-bit encrypted" or "verified" etc etc make a big difference to people. Can you please provide badges like that for those of us using balanced.js?

Get the basic site up and running so that we can concentrate on building content and not building widgets for the site. Requires a style guide to enumerate all the different components of the site.

Ensure that it's easy to setup and run the balanced-dashboard.

• Documentation explains how to get started
• Ensure all commands, scripts etc work
• Contributing guide

Migrated from balanced/balanced-api#50

Displays invoices and the transactions that comprise the invoice. Originally shown in #2

The current Balanced dashboard and JS library use Jasmine for testing.

We should definitely do this for our new dashboard and figure out how to enforce test coverage.

It's not practical to migrate the whole dashboard at once. How can we re-use the existing dashboard while we work on building out the new dashboard and maintain an existing level of functionality?

Zendesk do this by using iframes to serve old content within the framework of their new dashboard. This looks like a good strategy.

How will authentication work?

Several choices for now:

1. Set the API key straight in the user's cookies and send this directly to the API. This would require a temporary API key to be created per-session and expired when their login expires.
2. Proxy requests via a sever which translates the user's login credentials into a API key

Used to show unlinked transactions, works similarly to the existing transaction page within the old dashboard. Originally shown in #2

INDEX, SHOW + DELETE

URL /marketplaces/M123/cards|bank_accounts/

• ensure that deleting still works
• ensure that transactions are browseable
• can index bank accounts
• can index cards

Required to make migration possible / easy

Dedicated pages

• Marketplace settings #38
• Invoices - index + show #39
• Logs - index + show #40
• bank accounts / cards - index + show #41
• accounts - index + show + create #42
• transactions #43
  • debits - index + show
  • credits - index + show
  • holds - index + show
  • refunds - index + show
• search index + show #44

Misc pages

These are not dedicated pages / do not fit into the current dashboard look and feel. Let's figure them out:

• pay a seller #168
• withdraw funds #140
• add funds #140
• add a new marketplace #69
• KYC - this can remain separate from the dashboard
• add an account #172
• add a card #169 - done from account
• add a bank account #170 - done from account

Migrated from balanced/balanced-api#257

static HTML for pages

See the style guide for how it should look.

• Basic template
• Search box
• Page content

In particular:

• New dashboard mocks
• New search mocks

Close issues on balanced-api once done and leave a message letting everyone know where they can find the new hotness.

INDEX + SHOW

URL /marketplaces/M123/logs/OHM123

• pasting a search guid OHM123... into the search box should automatically redirect to the log entry
• our log entries tend to be really long so we should handle scrolling correctly.

(migrated from balanced/balanced-api#176)

Sparked from balanced/balanced-api#158 (specific comment here)

use case:
I want to know quickly when a credit I sent out has failed. Currently I have to click on each credit to determine it's state.

proposals:

1. Add a state column in the transactions list view. This will expose the state of a transaction (i.e. failed, pending, succeeded, etc)
2. Each row on the transaction's list will be a different color. Green to indicate success, neutral to indicate pending, and red to indicate failed

We could do one or the other.

We're using LESS for writing our CSS. But which framework should we use?

The current Balanced dashboard uses Bootstrap but the base version has lots of typographic spacing that isn't conducive to our layouts. We always have to do things like ul { padding: 0; margin: 0;} and Bootstrap is pretty verbose e.g.

    <header>
        <div class="navbar navbar-fixed-top">
            <div class="navbar-inner">
                <div class="container">
                ...
                </div>
            </div>
        </div>
    </header>

Hmmmm. Why not just

    <header>
        <ul>
             ... 
        </ul>
    </header>

What is the best way to replace configuration variables into the html files as part of the build process so we can switch analytics accounts etc?

Currently it should include:

• Icons for left hand nav

As a general rule going forward let's make the icons evenly spaced (per line) with each group of icons take up a line (different sizes, different line) the way twitter does it.

Currently our javascript libraries are built using a Makefile that we found on the internet that uses the uglify-js NPM package to build our JS files. We implemented that a year ago, what's the best way to combine and minify these days?

• Webhooks test functionality moved to #190
• User management moved to #28
• Test data

Displays logs of API calls

(migrated from balanced/balanced-api#203)

Currently you must pass an API key around to give another user access to a marketplace.

Ideally the dashboard would have a screen where you could assign a new user access to the marketplace by referencing their email address.

Bonus points if you could grant them read-only access or access to a subset of data.

INDEX, SHOW + PUT

URL /marketplaces/MP123/invoices/IN123

Check

• Can still update funding instruments
• Can view transactions related to invoice

It would be very handy if we had a visual ideal of all the pages in the new dashboard, how they relate to each other, and what actions can be taken on each page.

What's this repo all about anyway?

• About / Purpose
• Contributing
• Bugs / Feature requests

We need a style guide so we can begin building the basic css layout.

Basic less / css for site including variables that allow us to easily tweak the basic look and feel.

See the style guide for how it should look.

Currently the paths to images are hardcoded in the .less files.

This will not work with caching if we overwrite the file name. It would be better if they were tagged with a unique name as part of the build process

Migrated from balanced/balanced-api#255

One refactoring we were talking about today was about the authentication/login versions. I did some research on this while riding the BART home and it looks like it would make sense to use Ember Auth (https://github.com/heartsentwined/ember-auth) for authentication. Seems like it would handle the login request for us, we'd just have to have an API endpoint to get information on the logged in user and their marketplaces. That would remove a lot of the weirdness relating to logins/auth from our code as well as giving us more functionality out of the box to prompt for logins at appropriate times.

Seems like it should work for our use case and if we wanted to switch to OAuth at some point, it seems like it's supported. Only major risk I can see is if it's going to make testing difficult, but there has to be a way to mock out the Auth data provider.

Get travis-ci to enforce

• code coverage (90%)
• code quality (lint)

for all js.

Is there anything similar for less / css linting?

This file would have a row for each day that had a debit. This would make reconciling bank deposits a bit faster as we could just directly upload the file.

Displays recent activity in a browsable format. Originally shown in #2

INDEX + SHOW

URL /marketplaces/MP123/accounts/AC123

• can still edit account
• can add / delete funding instruments
• can view transactions

Implement all routes as seen on the new site map (#16) and also all routes that are defined on the existing dashboard so that we can click/browse through all the pages.

Included in this task would be adding an empty template file that can be filled in at a later date.

This is a pre-requisite for embedding iframes into the site.

INDEX + SHOW + PUT

URL /marketplaces/MP123/debits|credits|refunds|holds/XXXX

• ensure we can update existing transaction info
• can capture holds
• can refund debits

It adds a level of polish to a site in 2013 for it to be responsive, even if the site is complemented by native mobile apps. I rarely have my browser full screen.

Previously reported on balanced/balanced-api#238, we must ensure that this is enhancement is done on the new dashboard.

For each new page that has been spec'd out:

• List non-obvious endpoints that can be hit to get relevant information
• Note any potential performance or security requirements

Migrated from balanced/balanced-api#140

Per chat in #balanced on 10/2. Here is the scenario:

I am trying to setup a merchant account from a form I have on my website. I have created a bank account using balanced.js and am sending over the rest of the info to create a merchant account. However, my user ends up missing some info or needs to clarify something, and I am told to redirect to the balanced website to the Balanced Registration Form. I pass in my tokenized bank_account_uri, but nothing happens.

Because the user has already entered in their bank information, they should be able to have that part of the form either filled out / setup so they do not need to double enter it. That way I know that the bank account is already associated with that user's merchant account.

I was deploying as I went through a tunnel on the train and lost connectivity.

Because the index.html file is uploaded first it could reference the new css and js files before the files are uploaded.

We should ensure that the index.html that references the files is uploaded after all dependencies.

• Modals
• Popups
• Buttons

See the style guide for how these should look.

Nati:

"Put a save button so that people can click on save after they edit their settings or any info. I had to figure out that edit was save too." - known bug

Via IRC:

"Also very hard to register to your service. My friend had to tell me that "Go LIve" meant register. I think you would get more clients signed up if you had a register or sign up button somewhere so its more intuitive for people to sign up ;)"

SHOW + UPDATE

URL /marketplaces/MP123

check:

• webhooks management works
• edit marketplace functionality works
• adding and verifying bank accounts / cards works

This is the new way to view transactions. It utilises the on_behalf_of field to link debits and credits.

INDEX

URL /marketplaces/MP123/search?q=query+terms+other