I think there should be some facility to flag your messages topic wise. For e.g. I have a doubt about topic "x". Since we are discussing all the topics in the same chat window its difficult for me to go through all the messages once again and look for my topic of interest.

But if we have flags, I can simply click on the flag "x" and there it is!! I will be able to find all the information.

xinglunxu.md has <h1>-tags, please use # for that

As part of the fifth assignment, we are supposed to log onto NationBell to explore and see that our community is synced. However, the instructions specifying this are fairly vague.

On the nation side, you can log in as admin/password and check that the sync worked. Click on "Manager" once again.

Mainly, other than specifying nation side, there is no indication of where to go in order to log in nation side (vi.ole.org). It was only because I was browsing the group chat at the right time that I recognized where to go. The change I am proposing is fairly simple, just add (vi.ole.org) in brackets.

Also, I felt that the explanation of NationBell vs LocalBell wasn't really covered completely. I noticed that Emily had posted what seemed to be a much clearer explanation in chat and wanted to bring up the idea of including it or an edited version of it in the intro to the assignment.

So we have three levels: local, community, and nation. We need to make sure they are always synced and on the same page, otherwise you'll have merge conflicts and essentially run the risk of messing up the code pretty good. We use communities in places without internet because they are local. Whereas nations are connected to the internet and it allows a connection process between us (with internet) and those on communities (without internet). Communities are either run on RPis or laptops but are intranet, not internet connected and to sync the communities with the nations, we connect to internet so that information is sent in both directions.

I have submitted a fix for the first issue but thought there should be a discussion before addressing the second one.

The vagrant.md file suggests vboxmanage --version to make sure you have the correct installation.

vagrant --version will work from any directory, but vboxmanage can only be accessed if the command is run from the specific directory containing the executable.

My suggestion is that we include a line that makes it clear you have to run the command from the directory with the executable.

I know I was stuck here for a while because I'm a bit of a stickler for perfectionist

As part of Assignment 2, we have to follow the instructions on the GitHub and Markdown page. One of those instructions is to create our own markdown page introducing ourselves. While the instructions on how to do this is clear, what is not specifically mentioned is that this is an opportunity for us to experiment with markdown. As such, many initial pages were created very simple, and then edited to have more markdown elements after feedback from the gitter chat. So, I thought it would be a good idea to add a line to encourage experimentation and the usage of various markdown elements in the process of creating an introductory page. It could be something like this:

Feel free to experiment with Markdown and use various Markdown elements when creating your page. After all, this is an opportunity to familiarize yourself with the language.

I found some misspelled words in nation.md and bellapps.md as shown in the Attached file
nation.docx
bellapps.docx

On paragrapgh '4', as highlighted in the attached file must be rewritten as username.github.io.
typo errors.docx

Under the beLL-Apps tab, the link to see a user interface for CrowdDB "http://127.0.0.1:5985/apps/_design/bell/MyApp/index.html." doesn't work for Mozilla Firefox.

with 25a08f7 favicon.ico got added,
it works in firefox but not in chrome

I think it would be helpful to have another subsection of the wiki for troubleshooting.
It would be something akin to an FAQ for common problems people have run into, and problems that have discussed in the chat. This way everyone can have a place to view a compilation of past errors, and perhaps help with their own troubleshooting.

For each section on team.md, a small description is helpful.

On the third paragraph under "Git Repositories", the word "repositories" is spelled with 2 i's instead of one

I'm having problems with checking the vboxmanage version on the Command Prompt. I get the following message.
"vboxmanage is not recognized as an internal or external command..."

http://open-learning-exchange.github.io/ll_CC/#!pages/bughunt.md

more spacing between lines would be the text much more readable

In GitHub and Markdown repository, capitalization is missing and i found some typos in some of the paragraphs as shown in attached files
GitHubMarkdown-1.docx
GitHubMarkdown-2.docx

When clicking on links, a new tab should open.

https://jsfiddle.net/MadLittleMods/5u9h14Lc/ is an example how to add into any webpage. It would be awesome to get this working on our MDwiki instead of the link in the navigation bar ...

We are asked to follow open-learning-exchange in the welcome page of the Markdown wiki but github does not allow us to follow organization. We need to remove that.

Pretty obvious and possibly convenient, but maybe we can add a simple link next to the "chat" tab that can direct us to the official site of Open Learning Exchange, just for those of us who are curious to know more about the company.

Many of the links on firststeps.md don't link to the right page. For example, the link to the "GitHub and Markdown page" leads to http://open-learning-exchange.github.io/ll_CC/#!pages/pages/githubandmarkdown.md instead of http://open-learning-exchange.github.io/ll_CC/#!pages/githubandmarkdown.md.

Adding sign in option which will direct you to this link http://127.0.0.1:5985/apps/_design/bell/MyApp/index.html

On Team page, member Karen T is missing from list of members. Tested to see if the member site is active, and it is, but there is no link to the page. Right now to view page, other team members would have to type the url into their browser address bar.

Clicking anything on this screen just reloads the same screen in another window, seems like clicking on something like a course should give you details on that item.

On nation.md, I'd like to add more specific instructions on what to do after you finish the survey, as the specific buttons to push could be a source of confusion.

For vagrant.md, I think it might be helpful to put a note saying that it is necessary to vagrant up each time you want to run the local community BeLL.

Since anyone logged in as an admin on the Nation BeLL can see all of the information for each community user under the "Members" tab, it would be helpful to put a warning on nation.md not to use a password for the dummy user that you wouldn't want others to see.

Although pranesh-s.md is a part of the repository, it needs to be added to the team member page. This can be done by editing in the line:

[pranesh-s](/ll_CC/#!pages/pranesh-s.md)

in the team.md file. In addition, there are also team members on the page without a .md file attached. They are the following:

[mhalqurashi](/ll_CC/#!pages/mhalqurashi.md)
[ptruong88](/ll_CC/#!pages/ptruong88.md)
[xbxme12345](/ll_CC/#!pages/xbxme12345.md)
[sdronika](/ll_CC/#!pages/sdronika.md)
[mduprez](/ll_CC/#!pages/mduprez.md)
[shorabhd](/ll_CC/#!pages/shorabhd.md)
[SavinSachdev](/ll_CC/#!pages/SavinSachdev.md)

I am not sure what kind of change needs to be made regarding these team members. Finally, one team member links to the wrong .md file.

[alan459](/ll_CC/#!pages/alan459.md) -> should be [alan459](/ll_CC/#!pages/Alan259.md).

I have made changes fixing the first and last issue and have sent a pull request.

We could do a separate tab for answering frequently asked questions such as merge conflicts or not being able to do a pull from the github remote repository. It could be part of the faq tab in markdown wiki or a separate tab altogether

Similar to: open-learning-exchange/BeLL-Apps#49

To me, from me. just a reminder

On First Steps page, titles should be added to each step highlighting the major task in that step.

Some of the markdown code on the wiki is hard to visualize. Is there a way to insert a preview tab?

On BeLL-Apps: Community and Nation page, a note for Windows users should be added to point out that in order for the BeLL app to work, one must make sure that Intel VT-x is enabled.

Links are not working. I get this error: This page can't be displayed.

Next to all of the assignments there is "#" that doesn't do anything.

One of the instructions is as clear as it should be and so I wanted to help point where this occurred. My experience with learning has shown me that individuals succeed when things are as clear as possible. This applies beyond learning, but we'll stick to that since this organization has learning in its name.

This should be "Commit New File" as for users they will be seeing this:

when they scroll down.

Learning anything new is a time when simplicity, clarity, and ease should be greatest to help achieve familiarity.

I noticed that my personal team member page on the website has some extra line breaks that aren't present on the GitHub version. Though this is a bit of a nitpicky issue, I'm not sure what's causing the discrepancy in formatting.

I'm not sure why, but I can't merge my forked repo with the original. It says I'm six commits ahead, but I've already sent a pull request. How do I fix this?

Assignments 3 and 4 ask to follow Dogi, Emily and Open Learning Exchange on GitHub. We could provide direct links to their GitHub accounts. Secondly, you can't follow an organization on GitHub. So that instruction needs to be changed.

In the Markdown wiki, under the Git Repositories tab, at one point the reader is asked to run the command "git fetch upstream". However, under default condition, the upstream points to nothing so this command will not work. I think we should add instructions telling the users to point the upstream to a repository first.

Just wanted to know where to find the _Config.yml file and if we are updated to kramdown - which would allow us to open links in new tabs as mentioned in #108

When loading the mdwiki pages, the tab names are initially 'MDWiki', but changes into 'Your wiki name' immediately after.

It seems rather unclear for a non-windows user where the windows directions end as only "After" is mentioned in the following directions which is rather ambiguous as to whether it's referring to after the previous step in the windows directions or after installing.

The virtual interns need access to the Crowdin link to work on translation. This new tab should be between "Team" and "Chat" and should provide access to Open Learning Exchange's Crowdin.

How about adding one more tab to the Markdown Wiki: http://open-learning-exchange.github.io/ll_CC/#!index.md , that would include all related links we can refer to and any possible reading materials which can help us understand some important concepts. For example, git/vagrant/vbox help page, reading PDFs, any potential technology related to the intern.

http://open-learning-exchange.github.io/ll_CC/#!pages/bellapps.md
Problem:
When I clicked the links for those example resource files, it automatically opened up the file in a new tab, so all i need to do is right click the webpage and click save. I didn't use the 'raw' function at all.
Solution:
adding a small paragraph on the tutorial telling others if clicking the link leads them opening up the file in the new tab, then just need to right click and save is good. 'raw' function will not be needed in this case.
will make a pull request soon

Perhaps we should add a note stating that closing an issue is the same as resolving - had me caught for a while, it may help!

The top level ll_CC directory should be removed (or changed to en_US as this wiki is in English only).

Why can't we add one more tab to the Markdown Wiki: http://open-learning-exchange.github.io/ll_CC/#!index.md , that would be Help/FAQ that may be an assembled list of many questions and their answers that will help the new virtual interns or users when these questions tend to occur. For example: if i ask questions and get answers from you, i can post them in help/faq section that might help others who have similar questions

In the Git Repositories tutorial, we are taught how to clone a repository, and sync up with relevant master/upstream repositories. However, already some people have had to rebase their forked repositories and there aren't any helpful instructions or links on the page about the process. The following two links:

https://git-scm.com/docs/git-rebase
https://git-scm.com/book/en/v2/Git-Branching-Rebasing

are fairly helpful but I was unsure of how to go about adding it into the instructions on the Git Repositories page.

The image in http://open-learning-exchange.github.io/ll_CC/#!pages/gitandrepositories.md is different from the actual page. In the actual page GitHub page, to copy a link, one must click on the green button that says Clone or Download to find and copy the link.