-
-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A general issue for update to the new interactive site #42
Comments
This sounds fantastic! It would be really great if we could coordinate with the jupyter team to have the notebooks render on our site so users don't have to click a link to nbviewer to view the notebook, then go back to our site to vote on it. |
That would be nice --- perhaps as a second step. As a first step we can force those links to nbviewer to open in a new tab. Not as good but still a passable solution. |
Some Possible Projects that might be useful:
|
I missed the start of this thread, so this is probably underway. Starting with notebooks links is a good idea. That's what reddit does and it works very well. |
Haven't had a chance to carefully read this, but it may be of interest: https://github.com/airbnb/knowledge-repo |
@albop @DrDrij @mmcky @cc7768 @spencerlyon2 @oyamad
Hi all, this is a place where we can record our thoughts as we start to design the new interactive notebook site.
At present a rough model is stackexchange. For example:
http://math.stackexchange.com/
The plan: Next to each notebook is a count of views and upvotes / downvotes. It's possible to comment on a notebook. Notebooks are submitted as a link to a file that the users can update (for example, a URL from GitHub or Nbviewer). This is important so that they themselves can update it, rather than emailing us to do it.
Anyone can submit a notebook -- the free market decides their value.
Notebooks are tagged by the person who submits them and readers can filter by these tags (micro, macro, etc.) as well as by recent, most popular, etc.
@albop and @mmcky both emphasized reusing existing code for the notebook site if possible. For example, is the engine behind stackexchange open source?
@DrDrij Has agreed to do most of the hard work in putting the site together. We have a meeting on the 14th Oct to write down a battle plan. All input is appreciated.
The text was updated successfully, but these errors were encountered: