adamzev / free-code-camp-philly-showcase Goto Github PK

• Remove the card that says Approve/Reject
• replace it with cards of members (which currently just appear on the member page)
• If there are less than 6 members, show them all and otherwise randomize a selection
• The random selection and order should change with every refresh of the page.

I'd like new users to be able to contribute by just editing one file. If the .js or .json data files are automatically discovered and imported that'd help. Additionally, it'd be helpful if they are automatically displayed.

We need a way of checking if a webpage (whose url we'll have in a json file) is currently up. Because many portfolio projects are on Heroku, it needs to work with Heroku hobby servers (which boot when they receive a request...I don't know if they return a 200 right away).

The cards need to be put in a container and in rows and generally, be styled to more closely match the Featured User's section of the wireframe. A seperate wireframe should be created for the members page. The main difference is the photo of the user or thier avatar should be a small circle:

The wireframe mockup shows various semantic-ui components. We need to bring in the ones we are using. One component has already been added as an example of how to do this but we need several more.

Semantic-UI's site is at https://React.semantic-ui.com and it has a button that gives sample code for bringing in the components which makes this task accessible to people who are just getting started with React.

We have decided to skip creating an admin interface in favor of having users submit new content through GitHub pull requests. This will let everyone practice using GitHub's system and simplify the project. However, the wireframes still show an admin system.

If anyone is interested in doing this, I'll give access to our wireframes on MockFlow

We need to delete the one regarding the admin page and add a wireframe to show how a signed out user would see a user's portfolio. This will be a modification/replacement of the signed in user screen as the system will no longer have anywhere to sign in!

The components should be created based off a json structure that new users can modify. The structure needs to be mocked up and we need to try out using it to create the components.