This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

The primary purpose of the website is to get people information about what CFG does and how to join up. We need a prominent join us button on almost every page.
The current component is not great. Both the style/look of the button and the layout on mobile and desktop need to be reworked

Implementation

Round out the edges, make smaller and consider placing in the header.

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

On mobile, the hamburger is on the right side. It needs to be moved the left side. This also requires centering or right aligning the logo.

Implementation

• Move the hamburger to the left side of the menu bar
• Center or right align the logo
• See Bulma Docs for help styling/aligning navbar items.

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

Add eslint/prettier to auto lint and fix issues.

Implementation

• Add eslint/prettier
• Add linting to .vscode
• Set up precommit hook

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

See the Figma to get an idea of our CfGSO styles. Primarily I am concerned with colors but feel free to override any other variables you think are necessary.

https://www.figma.com/file/cmQXMXN6FPnOYTtUeB7Bmo/Website-Mockups?node-id=3%3A10

Implementation

Bulma Reference:

• https://bulma.io/documentation/customize/
• https://bulma.io/documentation/customize/variables/

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

Add Join Us page based on Figma mockups

https://www.figma.com/file/cmQXMXN6FPnOYTtUeB7Bmo/Website-Mockups?node-id=71%3A82

Implementation

• Create a new page component in the pages directory. (See index.js) for guidance
• Add the join us page to the menu

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

Add Resources page based on Figma mockups

https://www.figma.com/file/cmQXMXN6FPnOYTtUeB7Bmo/Website-Mockups?node-id=71%3A45

Implementation

• Create a new page component in the pages directory. (See index.js) for guidance
• Add the Resources page to the menu

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

When viewing the site on mobile the footer pushes up into the view. Move the footer further down so that it does not take up so much of the screen when viewing the site on mobile.

Implementation

Implementation is left up to the developer

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

Currently the hero image on the home and about page covers the full width and height of the screen on desktop. The image needs to be smaller so that users can still see page content without scrolling

Implementation

Implementation is left up to the developer. Ideally the implementation should be reusable between the home and about page

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

This page should generally contain a list of our projects with description and a link to either Github or more information. Format is up to the coder. See Tim for more specifics as needed.

Implementation

Re-entry resources hub:
Providing information relevant and valuable to residents reentering communities after a period of incarceration. Project initiated by 


GoVote GSO:
Creating a web application that the local public can use to easily view voter registration information about their polling places and logistics of election day. 
Link to Github (currently web app is only live through the Github.io?)
https://github.com/codeforgso/GoVote/
Govote.org
Dev site: http://govotegso-dev-1.us-east-1.elasticbeanstalk.com/

Community Indicators Project    
A collaborative initiative led by the Community Foundation of Greater Greensboro to unite local actors in collecting and making available data about public issues. 
Link to CFGG info page

Expungement and Record Clearance
For NDoCH 2019, we journey mapped the expungement process in Guilford County. 
Link to journey map Google Doc

LoE Dashboard
Creating a user friendly method for browsing Local Ordinance Enforcemend cases in Greensboro
https://github.com/codeforgso/LOE_dashboard

GitHub Workshop
An intro to Git and GitHub workshop that Code for Greensboro that was created and lead by Code for Greensboro members
Links
Slides: https://codeforgso.github.io/github-workshop/#/
Slides repo: https://github.com/codeforgso/github-workshop
Website repo: https://github.com/codeforgso/github-workshop-site/
Website: https://codeforgso.github.io/github-workshop-site/

Description

We need to decide on a tech stack for the website. My top two choices are Gatsby.js and Next.js.
Both of these can be used as static site generators and are based on React. I'll be evaluating both and make a secession soon. I'll be prioritizing developer UX and ensuring that the project is easy for newer devs to work on.

This is a:

• bug
• enhancement
• feature-discussion

running npm install command creates uncommitted files in package-lock.json due to changes in the versions of the node modues.

BUG

Expected Behavior

npm install Should not create uncommitted changes in package-lock.json

Current Behavior

npm install is creating uncommitted changes in package-lock.json

Possible Solution

Add package-lock.json to .gitignore

Steps to Reproduce (for bugs)

1. fork repo
   2.run "npm install"
   3.run "git status"

Your Environment

macOS mojave

• Version used:
• Environment name and version (e.g. Chrome 39, node.js 5.4):
• Operating System and version (desktop or mobile):
• Link to your project:

Enhancement

Description

Implementation

Feature-Discussion

MVP

After discussion on 2019-10-22, we have decided the MVP for the website will be finishing out the styling and content for Home, About, Join, and Our Projects.

This includes the following:

Home

• Replace image with Greensboro specific image
• Make clear that Code for Greensboro is not just for Coders

About

• Replace image with picture from NDOCH
• Change "About" header to "Who we are"
• Add h2 tags and sections for Leadership and Sponsors
• Get sponsor logos

Our Projects

• Adding image for each project
• Add status to each project

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

Create a footer component from the mockups.

See Figma: https://www.figma.com/file/cmQXMXN6FPnOYTtUeB7Bmo/Website-Mockups?node-id=3%3A10

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

On mobile, when you click on the menu bar icon it pushes all other content down. Update the navbar so that it overlays the page content instead of pushing the content down

Implementation

• Implementation is left up to the developer.
• See bulma docs for help

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

Add About Us page based on Figma mockups

https://www.figma.com/file/cmQXMXN6FPnOYTtUeB7Bmo/Website-Mockups?node-id=18%3A293

Implementation

• Create a new page component in the pages directory. (See index.js) for guidance
• Add the About page to the menu

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

We have decided that we do not want a resources page at this time.

Implementation

• Remove the pages/resources.js file
• Remove the link to the resources page form the navbar. (See components/nav.js)

These are additional issues identified to complete the Code for Greensboro V1 site

1. Modify mission statement - Tim provided on Slack #website-dev) 12/17/2019
   "Code for Greensboro's mission is to engage our community and its talent through civic action, open data, and technology"
2. Add social media logos in footer (Meetup, Slack, Facebook(@codeforgreensboro), Twitter(@codeforgso))
3. Need photos for leadership team added to Leadership page
   https://jtrpresents-my.sharepoint.com/personal/jordan_jtrpresents_art/_layouts/15/onedrive.aspx?originalPath=aHR0cHM6Ly9qdHJwcmVzZW50cy1teS5zaGFyZXBvaW50LmNvbS86ZjovZy9wZXJzb25hbC9qb3JkYW5fanRycHJlc2VudHNfYXJ0L0VoYldFZGxjZ3JsQm5Za1JyLU9CN3QwQkRnaEFOMGlaMjRtUFFXMHJxdkRBQWc%5FcnRpbWU9OHV1ZGNFLUQxMGc&id=%2Fpersonal%2Fjordan%5Fjtrpresents%5Fart%2FDocuments%2FTim%20and%20Schaffer%2FLeadership%20Team%20Photos%2FFinal%20edits%2FCode%20for%20GSO%20Leadership%202020
4. Need Bio’s for leadership team (see Slack #website-dev)
5. Add sponsors on "Who We Are" page (see below for link/image)
6. How to host - hosted on Now, need to change DNS in AWS (Schaffer) - Rob should have access to AWS
7. Add Slack for new members icon to Join Us and footer
   https://bit.ly/cfgso-slack

Rob: leadership page
Heather: footer, header mission statement

Link to photos of the leadership team:
https://jtrpresents-my.sharepoint.com/:f:/g/personal/jordan_jtrpresents_art/EhbWEdlcgrlBnYkRr-OB7t0BDghAN0iZ24mPQW0rqvDAAg?e=vwvImz

Sponsor logos:
Allegacy:

HQ Greensboro:
https://hqgreensboro.com/wp-content/uploads/2015/10/download_logo-300x113.png
Need to add IBM

This is a:

• bug
• enhancement
• feature-discussion

Feature-Discussion

Before we can begin developing the site we need wireframes. The wireframes can be built with any tool you'd like. The main focus of the wireframes should be the layout of site. Ideally the wireframes should be designed mobile first.

You can use our old site as reference for the content we have: https://codeforgso.github.io/codeforgreensboro.org

If you are unsure of what tool to use I would recommend Figma. It is free and there is plenty of training available for it.

This is a:

• bug
• enhancement
• feature-discussion

BUG

Expected Behavior

Current Behavior

There is a blockquote inside of a p tag and the browser considers this invalid html.

Possible Solution

Remove the blockquote from within the p tag, but ensure the styling stays the same

Steps to Reproduce (for bugs)

• While running the project locally, navigate to the about page, open your browser's developer tools/console. You should see the following error:

Warning: validateDOMNesting(...): <blockquote> cannot appear as a descendant of <p>.
    in blockquote (at about.js:12)
    in p (at about.js:10)
    in div (at about.js:9)
    in div (at about.js:8)
    in div (at page.js:14)
    in div (at page.js:13)
    in Page (at about.js:6)
    in About (created by App)
    in Container (created by App)
    in App
    in Suspense (created by AppContainer)
    in Container (created by AppContainer)
    in AppContainer

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

This button should be its own element underneath the menu that does not allow content to scroll under it.

Join Us button should be reconfigured so that it is visible once all pages

Current Behavior

As you scroll, the Heading content will overlap and disable the button completely.

This is a:

• bug
• [x ] enhancement
• feature-discussion

BUG

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Your Environment

• Version used:
• Environment name and version (e.g. Chrome 39, node.js 5.4):
• Operating System and version (desktop or mobile):
• Link to your project:

Enhancement

Description

Will make the arrow and "JOIN US" text more centered in their areas of the join button

Implementation

Feature-Discussion

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

On any page you will see that the page title/header is further left than the body content. We should horizontally align the page title with the body content.

Implementation

Implementation is up to the developer, but you will probably want to update the components/page.js

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

Add hero image to about page. See the figma mockups for the photo and an example of the layout.

Implementation

• Copy photo from figma
• Add photo to static directory of project
• Update pages/about.js to display the photo
• Ensure it looks good on mobile and desktop

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

The class names in the styles.scss are inconsistent and messy. We need to update the class names to be consistent and update the components to use the new class names

Implementation

Ideally we should use a naming convention like BEM and document this in our CONTRIBUTING document

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Description

Currently none of them items if the footer are links. Please link these items to the appropriate content

This is a:

• bug
• enhancement
• feature-discussion

Enhancement

Create a menu bar component. That when clicked expands to show a list of links to different pages.

Description

See Figma for more details: https://www.figma.com/file/cmQXMXN6FPnOYTtUeB7Bmo/Website-Mockups?node-id=3%3A10