The community-catalyst from resilient-labs

Create Profile EJS: Display User Photo/Info and Create form to post event(reference the post model/ user model)

Deadline: 6/14 (Wednesday) EOD 11:59pm

Create home.js to render the landing page (controller)

Have all header social links match on all pages and match ( and make sure they are connected with target _blank

Create posts.js to handle all the posts actions (profile, feed, creating, "going", deleting") (controller)

git branch add branch name here
git checkout add branch name here
git add .
git commit -m "example text: pushing feature [xyz] to [branch name here]"
git push

Create feed EJS: display all user posts from database (title; caption; time; date; going; location)

Note: Slack will have Post Model / Schema

Fix the bug on the post page; the routes

Deadline: Before lunch Jun 15th

This is a test by Zen

To add an item to the backlog on GitHub, you can follow these steps:

Navigate to the repository where you want to add the item to the backlog.

Click on the "Issues" tab near the top of the repository page.

On the Issues page, you'll see a green button labeled "New issue" on the right side. Click on it.

In the new issue form, enter a title for the item. The title should be concise and describe the task or feature you want to add to the backlog.

Provide a detailed description of the item in the comment box. This description should include any relevant information, context, or requirements for the item.

If needed, you can use labels to categorize the item. Labels help in organizing and prioritizing items in the backlog. To add labels, click on the "Labels" button on the right side of the issue form and select the appropriate labels.

Optionally, you can assign the issue to a specific person or team. To do this, click on the "Assignees" button on the right side of the issue form and choose the assignee from the list.

When you're ready, click on the "Submit new issue" button to add the item to the backlog.

Once you've added the item, it will appear in the repository's issue list and can be further discussed, assigned, prioritized, or scheduled for development as needed.