privly / privly.github.io Goto Github PK

When visiting the download page it will detect which browser the user has and highlight the appropriate column for download.

The download page and the front page should be combined and present information targeted at users. Developer information should be presented in the "develop" page.

@spectralsun Time for some of those sweet sweet glyph icons :). The root page needs graphics or glyphs for each of the text blocks on the bottom. It is currently too text heavy.

pages/develop.md needs to be updated for the Jetpack version of the firefox extension. The instructions needing to be updated appear on approximately line 202.

Since this is jetpack related it might fall on the shoulders of @hitesh96db .

• Page should stop after 'How does it work?' section.
• Move the "Organization" information from the about page to privly.org.
• Move the contributors to the "who are we" page.

I think "donate" should be a button somewhere instead of a small link on the bottom of the page. Perhaps upper right?

In particular, the "About" page does not contain a prominently displayed download link so users have to hunt for it after they are convinced they want the extension.

The Drupal style guide has been changing over the years and I think it is time to look at adopting a new one. I have been looking for something that is close to our current coding conventions, but is succinct. I think a good solution may be the following (in order of precedence):

JavaScript

• Don't use tabs for whitespace
• jQuery's rules https://contribute.jquery.org/style-guide/js/
• AirBnB's rules https://github.com/airbnb/javascript

JavaScript Linter

• JSHint http://jshint.com/
• JSLint http://jslint.com/

HTML and CSS

We have never had a formal HTML and CSS style guide, so I am proposing we adopt the following and update CSS over the course of time.

• @mdo's style guide http://codeguide.co/

The "Find a Host" button emphasizes federating hosting, but at this time there are not many content servers so it would be better to de-emphasize this page from the joining process.

The testing infrastructure is rather complicated and has several layers that are testable and configurable. I need to create a getting started guide for these systems that goes well beyond what is on the wiki.

See also: privly/privly-applications#30

There should be a single page guide similar to Twitter Bootstrap that gives all the development information. This should not be on privly.org since the org site is changing to being a blog+org info without being directly tied to the Priv.ly project.

The content can be ported from privly.org, and I have already started working on this.

how to make the nav

The donate page currently says nothing about our 501 (c) 3 status. We should add it.

Link to this story: https://www.privly.org/content/privly-gains-non-profit-status

Code Climate is now providing their team level service to the Privly Foundation for free and we should thank them.

https://codeclimate.com/

On the front page, link to the How to Get Started guide on privly.org (probably wait until how to get started guide is better - maybe by Feb 11 '14). Here's the link: https://www.privly.org/content/how-get-started

https://privlyalpha.org/apps/Message/show?privlyApp=Message&privlyInject1=true&random_token=11a6748755&privlyDataURL=https%3A%2F%2Fprivlyalpha.org%2Fposts%2F4784.json%3Frandom_token%3D11a6748755#privlyLinkKey=UORNT0OzCQPUoVPhCUK4fHAdbg1x6MzcF4CvLMh%2F0%2BQ%3D