65800eda6a
* Split hackage * WIP * Migrate to newer safecopy-migrate * Fix migrate * Rename description to summary for item * Fix link to templates * Frontend tests fix for pr #249 * Change the path back * WIP. Fix templates * Update back/src/Guide/Api/Types.hs * Remove unnecessary stuff from .gitignore * Revert style changes * Two spaces * _itemDescription has been renamed * Remove the Hackage test * name_on_hackage -> hackage * Fix Hackage param' type * front changes from kind to hackage * Fix tests * Try fix templete * Revert last commit * Comment front test in travis |
||
---|---|---|
back | ||
docker/back | ||
favicon | ||
front | ||
scripts | ||
.gitignore | ||
.travis.yml | ||
INSTALL.md | ||
Makefile | ||
README.md | ||
shell.nix | ||
stack.yaml |
Aelve Guide
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 these issues:
- “your first pull request” – really easy things, with detailed “how to fix it” instructions
- “your second pull request” – less easy things, which assume that you already know where stuff happens in the code
- “not-fleshed-out idea” – discussion issues (“should we have users? what better ways are there to present pros and cons?”) which you can help with even if you don't know Haskell
- “design” – issues about design (which I'm not good at, and so help is wanted)
Testing
You need chromedriver
and selenium-server-standalone
installed (those are the package names on Arch Linux). Then you can do
$ java -jar /usr/share/selenium-server/selenium-server-standalone.jar
$ make back/test
Notes
When you see something like
-- See Note [acid-state]
it means that there's an extensive comment somewhere else in the code, which you can find by grepping for Note [acid-state]
. This convention was stolen from GHC. If you know some plugin for Emacs that would help with jumping to comments (even if those comments would have to be formatted differently), let me know.