We have a Twitter account that doesn't put out a lot of content. It would be nice to grab a random, approved tweet from the previous week and tweet it out.

Maybe we should have it setup with an environment variable where we can specify the timeframe in days past to pull from. Then we could adjust the timer to fire every X days and just update that environment variable for the correct timespan.

Page exists, but we aren't loading pending gramercies or doing anything with them.

The jumbotron on the home page displays a static quote. We should modify this to randomly choose one of the quotes in the attached file.

quotes.txt

I'm open to suggestions, but my initial thoughts are:

• Need a section that describes what will appear if the person had gramercies.
• I'd like to have a section that lists organizations the user can get involved in to help others. Those could include:
  • Boys/Girls Clubs (https://www.bgca.org/)
  • TEALS (https://www.microsoft.com/en-us/teals/volunteers)
  • Feel free to suggest others.

When logging out of the live awesum.io site, I am redirected to localhost:8080 rather than back to the main page or a confirmation page.

Saw this behavior in Chrome 79.0.3945.88, Windows 10 1909.

Both functions (SaveGramercy doesn't currently exist) should require the 'awesum-moderator' role.

On mobile the front page is showing the 3 cards side by side. In my opinion the should use full screen width to be more readable.

The other day you mentioned your preferred standards around when it came to using directives, from what I gather it was

• Usings to be placed at the top of the file, before the namespace declaration
• System usings to be placed at the top of the usings section
• Any 3rd party or Framework usings to be shown next
• lastly, any internal references / usings places
• All of the above 3 categories are seperated by a blank line, for example

using System;
using System.Collections.Generic;

using Microsoft.Azure.WebJobs;
using Microsoft.Extensions.Logging;

using AwesumIO.Core.Common;
using AwesumIO.Core.Business;

namespace AwesumIO.Functions
{
    ...
    // code
    ...
}

I believe we can achieve consistency by using something like an editorconfig to ensure these guidelines are met - do you have any others from the top of your head you can think of, if you want to take this approach, EG

• trailing commas on object initialisation
• spaces between keywords and brackets (EG if(x == y) { } vs if (x == y) { }`
• We could make it so when rules are violated, the build fails, rather than warns, or vice versa

There's loads of options - just thought I'd raise an issue, and I might even take a stab at it over the weekend :)

Currently, there is no way to tell if your grammercies are modded out. It would be nice to see the ones you have sent and their moderation state.

Right now we are coupled to the data from production (i.e. twitter) which most other developers will not have access to. I would suggest we redesign the data with a pattern that would allow us to inject mock data.

When there are no #awesum notes to show, display a positive note/quote rather than the "We haven't picked up a tweet mentioning you with the #awesum hashtag yet." message.

On the example below, you can't tell which gramercy belongs to which recipient. A moderator may want to approve for one recipient and reject for another.

The icon used for the app needs to be updated at Twitter.

When logging into awesum.io with Twitter, users are asked to hand over what looks to be almost full control of their accounts:

To my eye, nothing other than the three "See" permissions should be needed, and even then all three "See" ones probably aren't needed either.

When the carousel starts rolling the section below changes size depending the size of the carousel.

When a user logs in, the carousel of bootstrap cards showing their gramercies doesn't rotate by default. Clicking "next" or "previous" will trigger the rotation.