• create content type: text with reference to page/campaign
• create contextual view block for campaigns
• create contextual view block for pages based on Campaign, page, and team

Currently at admin/structure/redhen_campaign even though the permissions is based on administer redhen. I think we should consider using admin/structure/redhen/campaign and/or add a more granular permission for administer redhen campaign.

In particular Campaign, primary_contact, author, and team. This may make the methods in the entity class redundant. In other cases, the methods have called the metadata setters/getters. Not perfect, but it works.

• welcome message
• username appearing on password reset screen
• theme the user edit screens
• "redhen contact" tab is confusing
• simplify email editing

Type in a list of email addresses and hit send to invite those people to join a Campaign.

• Need to have team-specific invitation or just general campaign
• Include a link that leads to the fundraise now link with auto-population of creation fields
• Hold onto the auto-population through user registration
• Customize the message, but include universal instructions that include the smart link

display widget for numbers.
Allows selection of an entity lookup field on the system and a product type.
Does an EFQ on products of that type, asking if the specified field has a value equal to the entity being displayed. Pulls in these price values and displays "X of X goal raised" and a thermometer.

@levelos sound like a clean solution for this? It's needed in different places around the site.

http://thinkshout.github.io/cafb-dc-campaign/fundraise.html

Needs to allow for creation of "smart links" to the creation that pre-populates lots of the fields, and potentially disables or hides the pre-populated fields.

When I drop content into on of the new main content regions ("content_secondary" or "content_tertiary") and also put something in "Sidebar first", the sidebar content renders, pushing the main content to the left, but the "content_secondary" content then displays over the top of the sidebar content.

As mentioned in another ticket, content_tertiary may be superfluous.

Hey @heypaxton and @unclegcb. I want to make sure we're approaching this distro build keeping an optimal mobile experience in mind. We probably should for most sites, but, hey, lets start here :) @heypaxton, sending your way to start, but lets all chime in. It will probably make sense to break this out into individual tickets for each item we want to implement eventually.

Options for HTML5 form elements

• HTML5 Tools and Elements
• Fences

Image handling

• Picture

Admin theme

• Shiny
• Use of the NavBar

If so, should be they metadata getters and setters so they can be manipulated by Rules, Views, etc?

We have a view here:
admin/structure/views/view/campaign_updates/edit/page_block

This shows updates posted to a campaign, and to the page. Amalgamating these listings is challenging with views, though: contextual filters give you the proper page or campaign, but they don't give you granularity in how you treat them, and the "team" updates can't be filtered this way unless we change our setup. My plan is this:

• Add "Team Context" to the Campaign Update content type and auto-populate it when creating updates.
• Only populate "Campaign Context" for Campaign-wide updates.

probably an entity reference to promo bean, then add a view block loading using context to the campaign & page context.

Overview

https://www.drupal.org/psa-2018-001

• Run security update

• Test locally

• Deploy to test

• QA (PMs or Client where applicable)

• Document any effects, and any steps to correct.

• Deploy to live site.

• Go to each Pantheon Multidev, Security tab, and set Environmental Access to Locked. Use the Username and Password from the Site User and Site Password columns here.

http://thinkshout.github.io/cafb-dc-campaign/team-list.html

It always starts overridden and must be manually set.

The "campaign updates" seem to sit in this extra area:
http://thinkshout.github.io/cafb-dc-campaign/campaign.html

Lets discuss why we need primary contact for campaigns and campaign pages.

• create and export breakpoints
• connect breakpoints with theme breakpoints
• configure image styles for breakpoints

You'll need to create one: content->add block->promo

then place it with Context or the block UI.

• Can people configure their contact data?
• is the UI reasonably intuitive?

redhen_raiser will need a thorough Readme, referencing the tools that Charlotte uses to customize it, and Charlotte will need it's own Readme.

Not clear what this is for. Currently being used in Campaign and Campaign Page controllers. In general, it's best to avoid using procedural functions within classes as it makes testing difficult. Maybe we should move it in the class and consider some type of inheritance between the two?