I will work on adding a navigation bar to the website. It will have links to log in/sign up or log out. It will be static and appear on every page.

Design a basic format for the social-wiki.
Pages contain paragraphs, with up/downvotes.
Paragraphs should be displayed in order of 'upvotes' from most to least.

Ideas:
-Provide some sort of homepage where you can navigate topics (pages) and search for topics you want to learn about.
-Provide a 'search' bar at the top of pages to filter results.
-Provide hierarchical comment system that one can access by clicking a 'show comments' button where users can have a conversation about a particular paragraph (think reddit).

We bumped it up for the demo but now need to get it back on track.

Sorry, my mistake. I should have never gave a thumbs up to #3. It should use rails user functionality so that things are actually done securely.

@ZachDFK

as of now (march 9th, 3pm), heroku app is down or not deployed. Or the link given in milestone 1 was incorrect.

Once Users are created, the following should be implemented:
-Ability to create topics
-Ability to contribute to a topic with a paragraph
-Ability to up/down vote paragraphs.
-Ability to 'follow' a users posts. Adding a 'news feed' of people's posts you follow.

Idea:
-Be able to create your own 'notes' on a particular topic by 'favouriting' paragraphs and pinning/adding them to 'notes'. Also, this can enable multiple different paragraphs from different topics in the same 'notes' page (would be good for subjects studied in school where there are multiple topics covered).

what have I done this week ?
what will I do next week ?
what is holding me back ? (optional)

what have I done this week ?
what will I do next week ?
what is holding me back ? (optional)

After making a scaffold for, I attempted to make a connection to view user index
routes.rb have been set to

...
resources :users 
get 'users' => 'users#index'
...

after running command:

bundle exec rails server&

the following was outputted:

=> Booting WEBrick
=> Rails 4.2.5.1 application starting in development on http://localhost:3000
=> Run rails server -h for more startup options
=> Ctrl-C to shutdown server
[2016-03-03 16:38:42] INFO WEBrick 1.3.1
[2016-03-03 16:38:42] INFO ruby 2.3.0 (2015-12-25) [x86_64-linux]
[2016-03-03 16:38:42] INFO WEBrick::HTTPServer#start: pid=2613 port=3000

when trying to connect to http://127.0.0.1:3000/users

Firefox gives a problem loading error saying connection is reset

what have I done this week ?
what will I do next week ?
what is holding me back ? (optional)

We forgot to do this.

"The Zero-Feature Release milestone consists of a skeletal implementation of your web app. This initial
implementation should have a proper version control repo, integrated with Circle CI, and be up and
running in production on Heroku (or elsewhere publicly reachable), with at least a static home page"

Social-wiki app needs to have users so we can implemented following features:

-social network following other users/posts
-voting system
-customizing views, paragraph.
-tracking trust value for posters.
-contributing to pages
-users can create posts

New Features to add:

• Upvote/Downvote system.
• Pinning posts
• Subject page
• User profile page / profile management
• Pass word recovery
• Header for login/signup to show up on all pages.

• what have I done this week ?
• what will I do next week ?
• what is holding me back ? (optional)

what have I done this week ?
what will I do next week ?
what is holding me back ? (optional)

One team member should submit to CULearn a short text with your team members and
topic, and a link to the github repo for your project.

Topic: Social Wiki
Group Members: Charles Wright (@GoodOlChuck), Kevin Cox (@kevincox), Matthew Crooke (@matthewcrooke1), and Zacharie Gauthier (@ZachDFK).
GitHub Repo: https://github.com/kevincox/social-wiki.git

• Fixed Log-in-page merging issues. group discussion of next step and features.
• Implement the features posted on issues earlier last week
• other school work slowing things down, log-in-page merge causes a bottleneck for others to finish their work.

Trying to deference current_user fails.