On Page 1, under "Follow us on GitHub", have a one line description of each repository.

On the Setting up your development extension...

First get the current code by cloning it from Github: git clone --recursive https://github.com/privly/privly-firefox.git

That git clone line should be in a "code block" style. I'm not sure how to do that in Drupal at this point.

On the first page, include this language:

If you see something wrong with this documentation or want something added, please submit an issue here: https://github.com/privly/privly-organization" In the title of the issue include the text "How to get started guide: <title of your issue>. For example, "How to get started guide: Add introductory video."

Steal documentation from this: http://openhatch.readthedocs.org/en/latest/getting_started/handling_contributions.html.

Add the documentation (or at least link to it) from the privly.org How to Get Started guide.

On privly.org, the pages:

• Roadmap
• How to Get Started

Both contain links to 'View' and also 'Revisions'. These link should be removed on each page, and the option for adding this feature should be checked on all pages and disabled.

Actions

• Remove 'View' and 'Revisions' link from Roadmap and How to Get Started
• Verify option is not enabled on other pages

Firefox Extension Development Installation section, remove "option 2".

I sent a blog post with a summary to the attendees. I'll publish it once all the commits are merged and deployed.

At the beginning of the guide, I feel like it'd be a good idea to include a prerequisite knowledge section and include links to good tutorials on those things.

Beginning Knowledge

1. Privly's primarily language is Javascript. Our example content server is written in Ruby on Rails.
2. Know what Privly is:
3. Watch this (it's okay if you don't get this yet):
4. Learn how to use IRC:
5. Learn how to use Git:

On Page 1, in case people don't know what Privly is, include videos.

Non-technical video: https://vimeo.com/83073455
Technical teaser trailer: https://vimeo.com/83258935

On the second step, say "open chrome preferences". On a mac, this is on the menu bar - Chrome -> preferences.

On http://privly.org, the 'Known Issues' page only shows up when users are on 'Submit a Bug'. This page should be removed. Users of privly.org have little concern or need to view the current issues of the software.

• https://www.privly.org/content/known-issues

The documentation feels hidden and tucked away from developers: It is a wiki on a non-descript repo.

Documentation should be promoted to it's own site or become a section of Priv.ly. Further documentation should be tailored to the specific audiences of:

• Users - Everyday humans.
• Advocates - People interested in the big picture.
• Developers - Current or future contributors.

We should add "Wouldn't just block Privly links?" to the FAQ. I think it's a question that comes up a lot, and it has just come up again.

Here's my start at an answer:
" (i.e. Facebook) could potentially block the links. However, we hope they realize that it is not in their best interest. With Privly available, more people would use the website than ever before. We have people waiting to use Facebook until Privly is available; they refuse to use it without Privly. It would increase traffic to their site. Furthermore, we don't control "likes" or other uses of the sites - only status updates. "

FAQ is located here: http://www.privly.org/faq

profile information for Windows is out of date potentially and also references older versions of windows that are not supported by microsoft.

On the left side of every page on privly.org is a 'Feedback' link which opens a contact form. This link should be removed as contact info is already listed in the sidebar of every page.

• Remove 'Feedback' Link/Module

When opening Privly site priv.ly/ many browsers give "Insecure / Untrusted connection warning". I guess some issue with certificate configuration on the Privly's side.

Firefox 37.0.1 on Linux Mint 17.1

Chrome 42.0 on CM 12 (Lollipop 5.0.2)

Firefox 37.0.2 on CM 12 (Lollipop 5.0.2)

@smcgregor, please look into the issue

For example on the first page there's a tiny link to "IRC>", but the book contents is above it. Is there a way to make the the "next page" link about the outline. That would seem to make more sense.

In the PGP wiki page, it says Mozilla Persona will be used for identification. I took a look at their webpage and it is mentioned that persona services will be shut down from November 2016.
Are there any open source alternatives to Mozilla Persona available? (LastPass and Okta provide similar services but they aren't open source)

Should we provide more detail on how to connect to IRC, or is it okay?

Potential new text:

If you've never used IRC before, we recommend either using the web IRC client (link) or check out this IRC tutorial to get started <link - http://www.irchelp.org/irchelp/irctutorial.html>
When you're in your IRC client, you can join us a #privly.

/connect irc.freenode.net
/nick
/join #privly

Say hi! We'd love to welcome you.

I am interested in working for Privly!

This should only be a link to email [email protected], and exist on priv.ly instead of the organization site.
From here issues can be triaged and transferred to their respective repositories. Most users will not know the distinction between privly-chrome, privly-firefox and privly-applications.

• Remove 'Submit a Bug' page from Privly.org
• Add 'Submit a Bug' link to footer of Priv.ly

We can not directly drive users to create a github issue because requires them to have a github account.

The 'How it Works' page of privly.org consists of a single link to https://priv.ly/pages/about. This page should be removed as it relates to the application stack not the organization.

• Remove the 'How it Works' page from Privly.org

it would make sense to have windows github setup help.

Add this language. "We are listing these repos, just so you have an understanding of the architecture of our project and can poke around. Don't worry about cloning the git repos yet, as that is described in Setting Up Your Development Extension and Setting Up Your Content Server."

The biography for Leslie Hawthorn is currently out of date. It should be replaced with the biography on the wiki: https://github.com/privly/privly-organization/wiki/Privly-System-and-Organization-Overview.

We should include a link to resources about Git.

webchat iframe embedded client
using your own irc client (GUI or text)

On setting up your development environment page...

"If you don't need to work with the latest and greatest version of the extension, download it from Mozilla's store and skip these steps. There are two options for working with development versions of the Firefox extension."

Should we allow this? Should we just encourage people to do the git thing.

Change wording on the first step on this page: https://www.privly.org/content/setting-your-development-extension to say "Get the source code from GitHub - link to source code - download zip file."

Include anchor tags on "Setting up Development Extension" so you can have a link at the top to each section. "Firefox" should have an anchor tag and "Chrome" should have an anchor tag.

...this is probably true for other pages, too.

Include text saying that they don't need a user account to do any of these actions.

I have tried to change the logo, but have been unsuccessful. I used the documentation here: http://www.inmotionhosting.com/support/edu/drupal-7/customize-theme/upload-custom-logo and it did not work. I tried clearing the cache through the administrative interface and it still did not solve the issue. I found that Drupal Gardens had an issue with this, which may have been persistent to this page.

At this point, I'm blocked. Not sure what else to try.

This is the logo I'd like to use on the privly.org page:

Steal stuff from here (make sure to link it): https://developer.mozilla.org/en-US/Add-ons/Setting_up_extension_development_environment?redirectlocale=en-US&redirectslug=Setting_up_extension_development_environment

After doing the stuff in the screenshots, go back to the terminal, and go to your profile directory. There should be a folder with lettersNumbers.dev.

Include screenshots.

Future work: consider creating a video for this.

The 'Give Privly a Try' link should put users directly in front of the download page. As this is currently being redone to be the front page of Priv.ly, it should be change to redirect there.

This can be summarized in points:

• Remove 'Priv.ly' link from site nav.
• Rename 'Give Privly a Try' to 'Share Privately'
• Move 'Share Privately' to end of site nav list.

My suggestions for changes:

1. White background
2. Prettier font
3. More/better spacing?

Blog posts and the 'How to Get Started' page have comments enabled. Though there have been a few comments made across the site, many are spam. Therfore comments should be disabled entirely on privly.org, as keeping up with spam is losing battle.

• Disable comments on all pages of privly.org

We need to update/remove G+ and Diaspora presences.

In addition, it would be beneficial to compile a list of all of our media presences.

www.privly.org's CSS leaves some of the headings not very readable. See: http://www.privly.org/content/setting-your-development-extension