aelve/guide
1
1
Fork 0
mirror of https://github.com/aelve/guide.git synced 2024-12-23 21:02:13 +03:00
Code Issues Projects Releases Wiki Activity
A workspace for research teams
344 Commits 18 Branches 0 Tags 5.2 MiB
Haskell 68%
Vue 14.7%
JavaScript 8.6%
TypeScript 5.8%
CSS 2.2%
Other 0.5%
e1a6245afc
Go to file
Artyom e1a6245afc Allow hiding ecosystem/pros/cons
2016-05-22 14:43:46 +03:00
favicon Add a favicon 2016-05-10 23:44:20 +03:00
scripts [test] List files manually 2016-04-11 13:14:34 +03:00
src Allow hiding ecosystem/pros/cons 2016-05-22 14:43:46 +03:00
static Make trait-controls more mobile-friendly 2016-05-14 01:27:02 +03:00
.gitignore Use config instead of environment variables 2016-03-22 01:17:53 +03:00
.travis.yml [Travis] Test loading the official database 2016-04-08 18:33:33 +03:00
CHANGELOG.md Create the project 2016-02-02 12:36:07 +03:00
guide.cabal Don't allow new megaparsec 2016-05-21 16:55:56 +03:00
INSTALL.md Add archive to .gitignore 2016-05-21 16:53:40 +03:00
LICENSE Create the project 2016-02-02 12:36:07 +03:00
README.md Write more about contributing 2016-05-21 21:40:07 +03:00
Setup.hs Create the project 2016-02-02 12:36:07 +03:00

README.md

Aelve Guide

Build status BSD3 license

The beta version is running at guide.aelve.com. The most complete section yet is the one about lenses.

Installation instructions and the explanation of config variables (in config.json) are here: INSTALL.md. Don't be afraid to install it locally – it's very easy! You don't need to set up any databases or anything like that, and you can get a full copy of the data from the site by simply cloning it from Github.

Contributing

If you want to contribute but don't know where to start, grep the source for [very-easy] and [easy], or look at the “your first pull request” and “your second pull request” labels (the TODOs scattered around the code are more about small local tasks, while issues on the issue tracker are more broad). I'm very interested in having more people contribute to this project, so I'm willing to spend a couple of days explaining to you how to fix something, even if I could fix the issue by myself in an hour. So, if you want to experience the thrill of Fixing An Issue in an Open Source Project, write me!