Updates from Wisconsin congressmen relating to incarceration can be posted daily for organizations to see what’s happening in Madison.

https://insideoutnetwork.net/login.

We might get access to this system. Michael from MSOE is reviewing.

Is this up anywhere? Even as a unreleased dev-only beta or something? Or does it just have to be run locally?

--
Beta deployment is at https://reentry.netlify.app/ but hosting on AWS is still not done

As any user, I would like to click on a button on the navigation bar that says "calendar" so that I can navigate to the Calendar page.

Add links of homepage to footer and remove the home page and replace it with landing page

Todo:

• create privacy policy component and terms
• create conditions component
• create ./privacypolicy route
• create ./termsandconditions route
• ask a contributor @paul-rinaldi to use TermsFeed and return that information to you (this will be added when sprint 2 starts)
• add links to privacy policy and terms and conditions links to footer component

Wireframe - in progress

We need to create a strong roadmap for the platform that's clear to understand and explain to potential volunteers and stakeholders.

Subtasks

• Select how we'll show the roadmap - there are 3 projects of WDP but this site is just the reentry one so github milestones and project views suffice?
• Update each week

Basics: https://docs.google.com/document/d/1_yIYFfVlitTIoirTfl1YvqljbmEDpA7xBaQLgvrTBVo/edit

Likely needs to be completed after:

• Rules-Based Authentication: (#29)

User Story:

• As a service provider, when I click on an empty slot in the day view of the Calendar on the Calendar Page, I would like to view a modal pop up so that I can add an event to the Calendar.

May involve:

• Material UI Modal: https://material-ui.com/components/modal/
• Adding an on click event

Related but can be done concurrently:

• Create modal to create an event for the calendar: #25

Landing Page needs to SHOW visually and DESCRIBE briefly:

• The purpose of the project
• What we offer to the public
• What we offer to the service providers (link to Login/Sign Up

Elements this might include

• Appbar with Title
• Photos / Video
• Parallax (eventually)

Components to Frontend:
TODO: Draft UI
TODO: Code UI

UI will be shown to Reentry Council for feedback

#www.insideoutnetwork.net
This solution has lots of features and lots of inputs for those features.

##Todo:

• Demo this website solution (html + js + bootstrap)
• Record its features for Service Providers (SP) and Post Incarcerated Individuals (PII) (ask owners)
• Evaluate / Discuss integration into our platform, identify redundancies, improve on weaknesses, how might we use this tool out of the box? how might we make this tool even more useful? (decide if we want to recode it in react since componentizing might help)

Registration and LogIn for Service Providers to contact other service providers

Questions:
How did you first feel when opening the website?
Were you able to find what you needed?
What should be changed about the website if anything?
...TBD
Could use typeform if that can work with react...

When the window viewport is reduced horizontally, the homepage becomes scrollable. And then the login button on the appbar begins crawling down the page. This is not wanted.

Found by @paul-rinaldi .

TODO: Alter CSS / use Material UI Button correctly.

• Project name: Your project’s name is the first thing people will see upon scrolling down to your README, and is included upon creation of your README file.
• Description: A description of your project follows. A good description is clear, short, and to the point. Describe the importance of your project, and what it does.
• Table of Contents: Optionally, include a table of contents in order to allow other people to quickly navigate especially long or detailed READMEs.
• Installation: Installation is the next section in an effective README. Tell other users how to install your project locally. Optionally, include a gif to make the process even more clear for other people.
• Usage: The next section is usage, in which you instruct other people on how to use your project after they’ve installed it. This would also be a good place to include screenshots of your project in action.
• Contributing: Larger projects often have sections on contributing to their project, in which contribution instructions are outlined. Sometimes, this is a separate file. If you have specific contribution preferences, explain them so that other developers know how to best contribute to your work. To learn more about how to help others contribute, check out the guide for setting guidelines for repository contributors.
• Credits: Include a section for credits in order to highlight and link to the authors of your project.
• License: Finally, include a section for the license of your project. For more information on choosing a license, check out GitHub’s licensing guide!

Todo:

1. Store events for a calendar in AWS -- This was actually once completed by @kaftand and @paul-rinaldi on a separate AWS account than what we now use
2. Store login information for users - cognito (<- amplify)
3. Store "services providers" (searchable by tag, name - RDS(more expensive), Aurora(more managed, less flexible) - compare -- SET UP THIS with Amazon RDS

RDS should comply with http://docs.openreferral.org/en/latest/hsds/ ... need to look into
Currently, we have fields:

1. ID (will need to be generated)
2. Label (Name, string)
3. Type (boolean - NonProfit(0) or ForProfit(1))
4. Program and Services (Names, Array of Strings)
5. Description (Multiple lines of text, String)
6. Tags (Multiple names, Array of Strings)
7. Address (Address, String)
8. Phone (Phone, String because of country codes or should we use number?)
9. Fax (Fax, String or number?)
10. Email (Email, String)
11. Website (URL, String)

Subtasks:
Formulate Ask or do it by myself
Fix website deployment on AWS or just temporarily on firebase w/e

Restrict the Calendar Component on the Calendar Page to take up approximately 80% of the width and 80% of the height so that there are margins of space between the calendar above and below the calendar component.

Add google maps Map inside the Box on the ServicesPage below the Service name
Add a config file in source control with fake api keys discussed here

Mockup

Guide if needed:
https://itnext.io/google-maps-react-makes-adding-google-maps-api-to-a-react-app-a-breeze-effb7b89e54

If this is not fixed, please fix and briefly explain in comment the fix. Otherwise, please briefly describe the reason it is fixed if it is fixed.

https://github.com/codeformilwaukee/DECARCERATION-PLATFORM/network/alert/web-app/yarn.lock/lodash.template/closed

Page holds directory of services that is easy for a user to understand and gives them plenty of information about specific services near them and for them.

Expected
Route to another page

Instead
Website not responding

Steps to reproduce

1. npm start
2. open browser at localhost:3000
3. ctrl+shift+i (enable console logging, i.e. DOM Inspector)
4. click Events on the navigation (at the top of the screen)
5. click any other Link on the navigation bar (at the top of the screen)

JS Warning Produced from DOM Inspector
(Maximum update depth exceeded. This can happen when a component calls setState inside useEffect, but useEffect either doesn't have a dependency array, or one of the dependencies changes on every render.)

• Wireframe - In progress
• Learning what to include from this article.

Mockup: https://balsamiq.cloud/s14elzc/ph76r2x

As any user, when I open the Calendar Page, I would like to view up-to-date events so that I can be informed on what events are happening now and in the future.

Execute an API call to our AWS API Gateway to retrieve an array of events.
Regenerate the calendar with the array of events.

Eventually, for the full website, to keep costs lower, we would like to use a CDN or KAFKA pipeline from Google Cloud or Amazon MSK so that our up to date events are cached and our AWS API isn't getting hit every refresh of the page.

As a Service Provider, I would like to click on an empty space in the calendar on the day view of the calendar, a modal opens.

This modal will allow the Service Provider to:
Add a title (required)
Set the date (required)
Set the time (required)
Set if it repeats (required, default=does not repeat)
Add a description (required)
Add a location
Add an attachment

Links to Include

• Home (/home)
• Events (/calendar)
• Data & Advocacy (/data)
• About (/about)

https://docs.amplify.aws/start/getting-started/setup/q/integration/react#initialize-a-new-backend

Add AWS Amplify and alter sign in page to use was amplify / cognito react components or just their api

Organize different events and meetings between organizations all on one online calendar. All organizations can post events with a brief description of what will happen.

Goals:

• A service provider should be able to add events to the Calendar.
• A user, not logged in, should not be able to add events to the calendar.

This may involve:

• AWS
• if statements on the calendar page (or on the link to the calendar page)
• API calls to AWS for authentication

Useful tips:

• We might want to add a roles.js to the constants folder.

Roles:

• Public (not logged in)
• Service Provider (logged in)

Note to keep in mind but don't need to implement for this card.

• Eventually (Admin (logged in - can do edit, delete, add directly on calendar))

Set REACT_APP_GOOGLE_MAPS_API_KEY to be used as an environment variable in the deployment workflow

Still unclear:
How to do this with netlify
How to do this with AWS
Is github actions needed? Is netlify needed to do what is required instead? Is it somewhat in between?

Edit: vercel may offer what we need, was should be able, vault may be needed

As a service provider, I would like to set an event to repeat on certain days, weekly, monthly, or yearly on the shared calendar so that I don't have to always make a new event on the wdp website.

Modal:
#34

May need to use:
Moment.js
AWS Dynamo DB

Verify if it's fixed or fix it if not (briefly describe fix).

https://github.com/codeformilwaukee/DECARCERATION-PLATFORM/network/alert/web-app/yarn.lock/set-value/open

As a user when I click on an event, I would like to see sufficient details of the event so that I can decide if I want to go.

• UI: a modal, side panel modal, dialog, etc. could all work
• Data: Can get data somehow from the event object that is selected; i.e. the event that has the onClick associated with it (retrieving an event's data https://jquense.github.io/react-big-calendar/examples/index.html

Event details:

• Title,
• Date,
• Start Time,
• End Time,
• Description

Content management portal that allows multiple users to post and aggregate content.

Searcheable list of service providers (@paul-rinaldi has the data on the providers)
Need to draft UI and create backend

Individuals interested in getting involved with an organization can find a directory of organizations that we partner with and their contact information.

User Story:

• As any user, when the calendar is loaded, the current date's day should be highlighted in some way, so that I can see what is happening today.

We need a good plan to make sure developers are participating and planning against the backlog.

Some ideas:

1. Create development roadmap. (visual would be helpful)
2. Have incentives tied to releases
3. Establish coding times (Code and Brews, Hack-n-tell, etc)
4. Utilize CfM Hack nights for recruitments business and demos
5. Clearly outline needs list

We would love to hear any ideas and thoughts that you have.

We have MU, UWM, Marquette all willing to participate along with Render and Ekmor to help deliver services to get this project to market. @romkedehaan will be working on the overall plan to pitch for funding and get the orgs to create MOUs to solidify how they will work together.

Draft document will be completed 2nd week of Jan.

Verify if it's fixed or fix it if not (briefly describe fix).

https://github.com/codeformilwaukee/DECARCERATION-PLATFORM/network/alert/web-app/yarn.lock/mixin-deep/open

ref=https://211wisconsin.communityos.org/guided-search - 211 Madison Basic Needs Search
ref=https://www.mkehometostay.org/ - Home to Stay

Add links to the home page to the above websites

Site members will be able to share new datasets, lists, or other
repositories with each other on this specialized page.

User Story:

• As a service provider, when I click submit on the event modal, I would like the event to be added to the events on the calendar so that others can see it!

When the submit button is clicked or form is submitted (not sure which is best to add the onclick to), execute an API (post?) call with the new event to the AWS API gateway.