4deb3f5ab9
* its coming along * links bar * scssify a bunch * metacode image working a bit better * metacode selector in react topic card * riek editing for name field on topic card * riek submit on enter * factor out Title and Links from Topic Card component, but not the listeners * create working Desc editor * styling is much better now * textarea min height for desc * disallow images in topic card markdown * shift enter is linebreak, enter is save * attachments split out, but it's pretty buggy * move listeners into Links.js * slightly wider metacodeTitle * fix positioning on metacode selector * fix metacode selection * move metacode and permissions into subcomponents * fixes * prevent editing on desc/title if not authorized to edit * fix topic card draggability * fix embedly * fix md test * remove the removed link card manually with jquery * fix test syntax * eslint * more eslin * reuse authorizedToEdit * convert metacode sets to a json object for react * add the html in react whoop * fix metacode styling * sort wasn't working * finishing metacode select * readd the above link input border * fix syntax * multiline title editable textarea * more portable metacode selector component * factor out #metacodeOptions into one react component with a callback :D:D:D * render metacodeOptions in right click menu with react * render metacodeOptions in right click menu with react * fix up right click menu's metacode editing * fix topic card title character counter * ignore metamaps secret bundle in ag * simplify Attachments props * factor out embedly card into its own component; it seems to help * link resetter * fix edit icon on title in topic card * move mapCount and synapseCount hover/click logic to react * fix up the showMore control * metacode selection tweaks * tweak links bar spacing in topic card * rubocop * remove TODOs * more badass permissions selector * close permission selector when you click outside * fix overeager metacode selector * more modular attachments component * fix bug in Desc.js * fix right click styling * permission changes are different than edit rights * bad module ref * ensure maxLength on topic titles |
||
|---|---|---|
| .github | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| doc | ||
| frontend | ||
| lib | ||
| log | ||
| public | ||
| realtime | ||
| script | ||
| spec | ||
| .agignore | ||
| .babelrc | ||
| .buildpacks | ||
| .codeclimate.yml | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .example-env | ||
| .gitignore | ||
| .nvmrc | ||
| .rspec | ||
| .rubocop.yml | ||
| .ruby-gemset | ||
| .ruby-version | ||
| .simplecov | ||
| .travis.yml | ||
| config.ru | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| package.json | ||
| Procfile | ||
| Rakefile | ||
| README.md | ||
| Vagrantfile | ||
| webpack.config.js | ||
Metamaps
What is Metamaps?
Metamaps is a free and open-source technology for changemakers, innovators, educators and students. It enables individuals and communities to build and visualize their shared knowledge and unlock their collective intelligence.
You can find a version of this software running at metamaps.cc, where the technology is being tested in an open beta.
Metamaps is developed and maintained by a distributed, nomadic community comprised of technologists, artists and storytellers. You can get in touch by using whichever of these channels you prefer:
How do I learn more?
- Contact: team@metamaps.cc or @metamapps on Twitter
- User Documentation: docs.metamaps.cc
- User Community: hylo.com/c/metamaps
- To see what we're developing, or to weigh in on what you'd like to see developed, see our Metamaps Feedback and Features board on trello
- To follow along with, or contribute,to our design process, see our Metamaps Design board on trello
- To follow along with, or contribute to, our development process, see our Github Issues and Pull Requests
- Request an invite to the open beta here
- To send us a personal message get in touch with us via email, Twitter, or Hylo
- If you would like to report a bug, please check the issues section in our contributing instructions.
- If you would like to get set up as a developer, that's great! Read on for help getting your development environment set up.
Installation
If you are on Mac or Ubuntu you can use the following instructions to quickly get a local copy of metamaps up and running using a Vagrant virtualbox. Don't be intimidated, it's easy!
git clone git@github.com:metamaps/metamaps.git
Now ensure you have VirtualBox and Vagrant installed on your computer
cd metamaps
./bin/configure.sh
This will do all the setup steps to make Metamaps work with a bit of behind the scenes ninja magick.
To start servers which will run metamaps you can then run:
./bin/start
To stop them:
./bin/stop
With your webservers running, open a web browser and go to http://localhost:3000
You can sign in with the default account
email: user@user.com
password: toolsplusconsciousness
OR create a new account at /join, and use access code qwertyui
Start mapping and programming!
We haven't set up instructions for using Vagrant on Windows, but there are instructions for a manual setup here:
Licensing information
This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or(at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
The license can be read here.
Copyright (c) 2017 Connor Turland