Updated "We Vote" text across the site to be "WeVote".

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing to wevote/WebApp
 
-Thank you for your interest in the We Vote WebApp project. Please let us know if we can help you get started.
+Thank you for your interest in the WeVote WebApp project. Please let us know if we can help you get started.
  (contact info: https://github.com/wevote)
 
 To get started, [sign the Contributor License Agreement](https://www.clahub.com/agreements/wevote/WebApp)

README.md

@@ -1,4 +1,4 @@
-# We Vote WebApp
+# WeVote WebApp
 
 [![Build Status](https://travis-ci.org/wevote/WebApp.svg?branch=develop)](https://travis-ci.org/wevote/WebApp)
 [![Sauce Test Status](https://saucelabs.com/buildstatus/WeVote)](https://saucelabs.com/u/WeVote)
@@ -14,7 +14,7 @@ To join us, please [review our openings here](https://wevote.applytojob.com/appl
 Our current version is here [https://WeVote.US](https://WeVote.US) and we are working on a new version now!
 
 ## Installing WebApp
-Our installation process is built to allow engineers all over America to contribute to We Vote.
+Our installation process is built to allow engineers all over America to contribute to WeVote.
 It may seem complicated, but it allows anyone to be in a position to make suggestions, and get involved.
 
 Installation on MacOs and Linux

docs/WindowsSimplifiedInstall.md

@@ -110,11 +110,11 @@ The install for procedure using WebStorm is the same as what you see here. WebSt
 23. In PyCharm set up your git remotes. 
     1. Navigate to the Git/'Manage Remotes...' dialog  
 
-    The We Vote projects defines upstream and origin differently than most other projects, so we need to manually reverse them here.
+    The WeVote open source project defines upstream and origin differently than most other projects, so we need to manually reverse them here.
     3. Click the edit (pencil) icon, and change the name field for the URL to your copy of the repository from "upstream" to "origin".  (The following picture shows the dialog before you make the Name change.)
 
     ![ScreenShot](images/WindowsGitUpstream.png)
-    5. Then add a remote for your We Vote's public branch by pressing the '+' button on the Git Remotes dialog. In the dialog that appears, set the name field to "upstream", and the URL to "https://github.com/wevote/WebApp.git".  Press OK and the remotes should look like this:  
+    5. Then add a remote for your WeVote's public branch by pressing the '+' button on the Git Remotes dialog. In the dialog that appears, set the name field to "upstream", and the URL to "https://github.com/wevote/WebApp.git".  Press OK and the remotes should look like this:  
 
     ![ScreenShot](images/WindowsManageRemotes.png)
     Press OK to close the dialog.
@@ -207,7 +207,7 @@ The install for procedure using WebStorm is the same as what you see here. WebSt
 30. Install gulp
    In the terminal `npm install -g gulp-cli`
 
-31. Install (the approximately 1600 open source packages, libraries or "node_modules" that We Vote uses as a foundation for our WebApp)
+31. Install (the approximately 1600 open source packages, libraries or "node_modules" that WeVote uses as a foundation for our WebApp)
 
     In the terminal `npm install`
 
@@ -225,7 +225,7 @@ The install for procedure using WebStorm is the same as what you see here. WebSt
 
 32. Make this configuration change, to allow the WebApp to be compiled under Windows. 
 
-    Background: MS-DOS and subsequently Windows chose to end each line in a text file with a carriage-return followed by a line-feed (CRLF), but UNIX, Linux and macOS simply uses a line-feed (LF).  All WeVote source code files use LF when advancing to the next line, so this configuration is necessary to allow files on Windows to be able to be submitted to We Vote's git repositories.
+    Background: MS-DOS and subsequently Windows chose to end each line in a text file with a carriage-return followed by a line-feed (CRLF), but UNIX, Linux and macOS simply uses a line-feed (LF).  All WeVote source code files use LF when advancing to the next line, so this configuration is necessary to allow files on Windows to be able to be submitted to WeVote's git repositories.
 
     **This "fix" is a bit hacky, and you have to be sure not to commit this '.eslintrc' file to Git if you check in changes.**
 
@@ -238,7 +238,7 @@ The install for procedure using WebStorm is the same as what you see here. WebSt
     This configuration line, disables Windows vs Linux "lint" line break checking, and allows you to run the WebApp you compile on your Windows PC.
 
 
-## Run the We Vote WebApp
+## Run the WeVote WebApp
 
 1. In the terminal, type the command `npm run start-win` to start the local webserver.
    ![ScreenShot](images/WindowsSuccessfulRun.png)

docs/contributing/APPROVING_PULL_REQUESTS.md

@@ -2,13 +2,13 @@
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 ## Contents
 
-- [We Vote Process for Approving Pull Requests](#we-vote-process-for-approving-pull-requests)
+- [WeVote Process for Approving Pull Requests](#we-vote-process-for-approving-pull-requests)
 - [Bringing a Pull Request to your Local Machine for Verification](#bringing-a-pull-request-to-your-local-machine-for-verification)
   - [](#)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
-# We Vote Process for Approving Pull Requests
+# WeVote Process for Approving Pull Requests
 We have a team of engineers who can approve pull requests for WebApp (Nick Fiorini, Rob Simpson, Lisa Cho, Dale McGrew). A few notes about our process:
 
 * Give thumbs up before approving to confirm that you followed this verification process.

docs/contributing/CONTRIBUTING_PHILOSOPHY.md

@@ -2,14 +2,14 @@
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 ## Contents
 
-- [We Vote Culture and Philosophy](#we-vote-culture-and-philosophy)
+- [WeVote Culture and Philosophy](#we-vote-culture-and-philosophy)
   - [](#)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
-# We Vote Culture and Philosophy
+# WeVote Culture and Philosophy
 
-Why do we spend our weekends and evenings working on We Vote?
+Why do we spend our weekends and evenings working on WeVote?
 
 ---
 

docs/contributing/CONTRIBUTING_STANDARDS.md

@@ -66,7 +66,7 @@ Examples of names we avoid:
 There is no perfect code style.  If you have worked at a few different companies or on a few different open source projects, you
 will have used a few different styles.
 
-As of December 2018, the We Vote WebApp src directory contained 1073 files, that have been created and edited by dozens of volunteer
+As of December 2018, the WeVote WebApp src directory contained 1073 files, that have been created and edited by dozens of volunteer
 software engineers.  And we had dozens of different code styles in different files.
 
 Inconsistently formatted code is less reliable code, so we decided to (mostly) put aside the 
@@ -87,7 +87,7 @@ The list might be quite long, so you may want to redirect it into a file that yo
 
 # Code Craftsmanship
 
-We value Software Craftsmanship for the We Vote project since it makes working on the We Vote code base …
+We value Software Craftsmanship for the WeVote project since it makes working on the WeVote code base …
 * Fun since the product is composed of clean self documenting components that 
   * Do not repeat themselves -- each functional block has a component, or collection of components that can be widely used, or is completely unique.
   * Are easy to rearrange on panels and pages, with less (or no) modifying of the components themselves for new uses or new UI approaches..
@@ -126,7 +126,7 @@ We value Software Craftsmanship for the We Vote project since it makes working o
 
 ## Reporting bugs as member of the engineering team
 
-* We use Jira to track issues with the We Vote website and mobile Apps, thanks to [Atlassian, the makers of Jira](https://www.atlassian.com/software/views/open-source-license-request#/), and their support for open source projects.
+* We use Jira to track issues with the WeVote website and mobile Apps, thanks to [Atlassian, the makers of Jira](https://www.atlassian.com/software/views/open-source-license-request#/), and their support for open source projects.
 * If you're actively working on an issue, please mark it as "Fix in Progress" and assign the issue to yourself.
     * Please only "take" one issue at a time, unless you speak to the Engineering Manager first.
 * Please keep the team updated on the work you are doing by attending our weekly stand-up meeting, or post a note in the #coding Slack channel.

docs/contributing/CREATING_PULL_REQUEST.md

@@ -166,7 +166,7 @@ We follow [SemVer](http://semver.org/) for our releases. Please read if you plan
 ## I Have Submitted a Pull Request, Now What?
 Sometimes pull requests can take a day or two to be approved. How do you keep working? TODO discuss this.
 
-While your pull request is being considered by the We Vote admins:
+While your pull request is being considered by the WeVote admins:
 Any new changes unrelated to this one should be on a brand new branch (`git
 checkout -b <your-second-feature-branch>`). Don't forget to check out the develop branch first, otherwise you'll 
 branch off of the current PR branch

docs/contributing/PULL_REQUEST_SETUP.md

@@ -11,10 +11,10 @@
 
 # Before Your First Pull Request
 
-Thank you for your interest in the We Vote WebApp project. Please let us know if we can help you get started.
+Thank you for your interest in the WeVote WebApp project. Please let us know if we can help you get started.
  (contact info: https://github.com/wevote)
 
-This document includes the steps you need to take before your first We Vote pull request. 
+This document includes the steps you need to take before your first WeVote pull request. 
 We recommend reading “[What the Heck is a Pull Request?](PULL_REQUEST_BACKGROUND.md)” before following these steps. 
 
 Please [sign the Contributor License Agreement](https://www.clahub.com/agreements/wevote/WebApp) before getting started.

docs/installing/ENVIRONMENT.md

@@ -77,7 +77,7 @@ Now activate this new virtual environment:
     $ cd /Users/<YOUR NAME HERE>/NodeEnvironments/WebAppEnv/
     $ . bin/activate
 
-**Note** that you will need to do the step above every time before you start local development. Once you have activated this virtual Node environment, it will persist in the current Terminal tab even as you navigate to different folders (e.g., the We Vote WebApp folder). You'll see that each line on the Terminal starts with `(WebAppEnv)` while the virtual environment is in effect. You can read more about nodeenv [here](https://github.com/ekalinin/nodeenv).
+**Note** that you will need to do the step above every time before you start local development. Once you have activated this virtual Node environment, it will persist in the current Terminal tab even as you navigate to different folders (e.g., the WeVote WebApp folder). You'll see that each line on the Terminal starts with `(WebAppEnv)` while the virtual environment is in effect. You can read more about nodeenv [here](https://github.com/ekalinin/nodeenv).
 
 Just to be safe, rebuild node-sass:
 

docs/installing/RUNNING_FIRST_TIME.md

@@ -67,7 +67,7 @@ At this point you will be asked for certificate information, like this:
      Country Name (2 letter code) []:US
      State or Province Name (full name) []:California
      Locality Name (eg, city) []:Oakland
-     Organization Name (eg, company) []:We Vote
+     Organization Name (eg, company) []:WeVote
      Organizational Unit Name (eg, section) []:
      Common Name (eg, fully qualified host name) []:localhost
      Email Address []:
@@ -97,11 +97,11 @@ You should be able to visit WebApp via HTTPS here:
     https://localhost:3000
 
 
-## Using We Vote API server Locally: OPTIONAL
+## Using WeVote API server Locally: OPTIONAL
 
 The default configuration connections to our live API server at: https://api.wevoteusa.org, so this step is optional.
 
-If you would like to install the We Vote API server locally, start by reading the instructions to 
+If you would like to install the WeVote API server locally, start by reading the instructions to 
 [install WeVoteServer](https://github.com/wevote/WeVoteServer/blob/master/README_API_INSTALL.md).
 
 

docs/testing/README_TESTING.md

@@ -20,7 +20,7 @@ Visit this page when you are signed into Browserstack, and they will customize t
 
     curl -u "YOUR-USERNAME:ACCESS-KEY-HERE" -X POST https://api-cloud.browserstack.com/app-automate/upload -F "file=@/path/to/app/file/Application-debug.apk" -F 'data={"custom_id": "MyApp"}'
 
-You can find the latest We Vote APK (for Android) and IPA (for iOS) in [this Google Drive folder](https://drive.google.com/drive/u/0/folders/10tK7oqY7FKWhe0ilHDcli-DWpT9ldTFs).
+You can find the latest WeVote APK (for Android) and IPA (for iOS) in [this Google Drive folder](https://drive.google.com/drive/u/0/folders/10tK7oqY7FKWhe0ilHDcli-DWpT9ldTFs).
 Please download it to your Download folder. For example, to find this path on a Mac:
 
     (WebAppEnv) $ cd ~/Downloads

docs/working/AppleSilicon.md

@@ -6,7 +6,7 @@ Will remove these notes once Big Sur is released, and Apple Silicon (iOS app run
 See Apple [Universal App Quick Start] private forum [662281](https://developer.apple.com/forums/thread/662281?login=true).  Also
 an Apple Beta Feedback Assistant issue, for Big Sur beta 8, has been lodged (FB8755308) titled "No Inspectable Applications" in Safari Debug Menu for targets with "My Mac" -- No response yet from Apple.  
 1. node-sass is tied to macOS versions, so it is not available for Big Sur yet.  Hopefully we will design it out 
-of the "We Vote Web App" this year.  In the meantime, we need to build main.css on an intel Mac, and copy it to the 
+of the "WeVote Web App" this year.  In the meantime, we need to build main.css on an intel Mac, and copy it to the 
 Apple Silicon (ARM64) mac in order to have all the legacy styles work.
 Manual changes have to be made to package.json and webpack.config.js on the ARM64 Mac to remove
 node-sass from the build.

docs/working/PROGRESSIVE_WEB_APP.MD

@@ -12,7 +12,7 @@ is available to the voter when offline.  This caching layer also can speed up th
 caching it locally.
 
 It is possible to cache too much, or not have the cached data expire soon enough, which makes for a bloated load
-of the browser, and could needlessly use up valuable RAM memory on the voter's computer.   We Vote developers woring on
+of the browser, and could needlessly use up valuable RAM memory on the voter's computer.   WeVote developers woring on
 this feature should take a look at all the other service workers that your browser has accumulated over the years (Application tab in
 Chrome Tools, under Application/ServiceWorkers  and then at the bottom via "Service workers from other origins").  If you press
 the "Clear storage" button it will not immediatley clear storage, but will show you how much

docs/working/STYLING.md

@@ -19,7 +19,7 @@ Stylesheet partials are organized by scope (based on the ITCSS model), and compi
 ### A note on using Bootstrap
 This project relies heavily on the Bootstrap framework and related third-party plugins. Bootstrap's core value lies in its solid set of default helpers and styles, but as a third-party framework, it should not be expected to support all styling needs and it should not be customized with overrides (except in rare instances).
 
-Rely on Bootstrap styles and helpers when they can be used without hacks, and create sensible custom (We Vote specific) patterns and helpers instead of trying to extend Bootstrap styles.
+Rely on Bootstrap styles and helpers when they can be used without hacks, and create sensible custom (WeVote specific) patterns and helpers instead of trying to extend Bootstrap styles.
 
 To edit Bootstrap defaults, set variable values in `_bootstrap-variables.scss` and only use selector strings to override Bootstrap declarations as a **last resort**.
 

package.json

@@ -1,7 +1,7 @@
 {
   "name": "wevoteusa",
   "version": "1.0.0",
-  "description": "We Vote front end application",
+  "description": "WeVote front end application",
   "main": "index.jsx",
   "keywords": [],
   "author": "",

src/index.html

@@ -1,15 +1,15 @@
 <!DOCTYPE html>
 <!--
-    index.html for We Vote Ballot
+    index.html for WeVote Ballot
 -->
 <html lang="en">
   <head>
 <!--    <title><%= htmlWebpackPlugin.options.title %></title>-->
     <meta
       name="description"
-      content="We Vote helps you vote your values, with help from your friends and other people you trust. Through our nonpartisan, open source platform, we'll help you become a better voter, up and down the ballot."
+      content="WeVote helps you vote your values, with help from your friends and other people you trust. Through our nonpartisan, open source platform, we'll help you become a better voter, up and down the ballot."
     />
-    <title>We Vote</title>
+    <title>WeVote</title>
     <meta http-equiv="Cache-Control" content="public" />
     <meta http-equiv="Pragma" content="no-cache" />
     <meta http-equiv="Expires" content="0" />
@@ -18,7 +18,7 @@
     <meta charset="utf-8">
     <meta property="og:url"           content="https://WeVote.US" />
     <meta property="og:type"          content="website" />
-    <meta property="og:title"         content="We Vote Sample Ballot" />
+    <meta property="og:title"         content="WeVote Sample Ballot" />
     <meta property="og:description"   content="View your ballot. Learn from friends. Share your vision." />
     <meta property="og:image"         content="https://WeVote.US/img/global/logos/we-vote-logo-wordmark-vertical-color-on-white-256x256.png" />
     <base href="/">

src/js/actions/FacebookActions.js

@@ -29,7 +29,7 @@ export default {
   },
 
   disconnectFromFacebook () {
-    // Removing connection between We Vote and Facebook
+    // Removing connection between WeVote and Facebook
     FacebookSignedInData.clearFacebookSignedInData();
     Dispatcher.dispatch({
       type: FacebookConstants.FACEBOOK_SIGN_IN_DISCONNECT,
@@ -43,7 +43,7 @@ export default {
   // },
 
   // Sept 2017, We now use the Facebook "games" api "invitable_friends" data on the fly from the webapp for the "Choose Friends" feature.
-  // We use the more limited "friends" api call from the server to find Facebook profiles of friends already using We Vote.
+  // We use the more limited "friends" api call from the server to find Facebook profiles of friends already using WeVote.
   facebookFriendsAction () {
     Dispatcher.loadEndpoint('facebookFriendsAction', {});
     FriendActions.friendListSuggested();

src/js/actions/VoterSessionActions.js

@@ -32,7 +32,7 @@ export default {
     hostname = hostname || '';
     console.log('VoterSessionActions setVoterDeviceIdCookie hostname:', hostname);
     if (hostname && stringContains('wevote.us', hostname)) {
-      // If hanging off We Vote subdomain, store the cookie with top level domain
+      // If hanging off WeVote subdomain, store the cookie with top level domain
       Cookies.set('voter_device_id', id, { expires: 10000, path: '/', domain: 'wevote.us' });
     } else {
       Cookies.set('voter_device_id', id, { expires: 10000, path: '/' });

src/js/common/ReadMeReCommonDirectory.txt

@@ -1,7 +1,7 @@
 July 14, 2021:
 
-The files in the common directory must be exactly the same in both the We Vote WebApp repository
-and the We Vote Campaigns project.
+The files in the common directory must be exactly the same in both the WeVote WebApp repository
+and the WeVote Campaigns project.
 
 In this way we will only fix a bug once, or make an added feature once, at the cost of having to test twice.
 

src/js/common/components/CampaignShare/shareButtonCommon.jsx

@@ -100,7 +100,7 @@ export function cordovaSocialSharingByEmail (subject, body, handleClose = null)
     /* eslint-disable key-spacing */
     console.log('before open cordova.plugins.email.open ', subject);
     cordova.plugins.email.open({
-      from:         'We Vote',          // sending email account (iOS only)
+      from:         'WeVote',          // sending email account (iOS only)
       to:           '',                 // email addresses for TO field
       cc:           [],                 // email addresses for CC field
       bcc:          [],                 // email addresses for BCC field