613ecf8c9a
* Consistent headings and paragraph styles for entire app * Search adopted for mobile * Category item adapted for mobile * Consistent category header icon sizes and paddings, relatively rest of category page * Hide logo when search input displayed on mobile * removed excess css rule * font size and line height changed * Badge adjusted for new font size * Lists margins added * Footer padding and margins adapted for mobile * Markdown editor correct focus on open * Markdown editor autofocus now optionabe * Typo fix * Markdown editor component more props and styling * Markdown editor border stylings * Conflict dialog refactor and adapting for mobiles * Typo fix * Categories page restyled and adapted for mobiles * Categories page group titles allow break words * Removed excess comparison |
||
|---|---|---|
| back | ||
| docker | ||
| favicon | ||
| front | ||
| scripts | ||
| .gitignore | ||
| .hlint.yaml | ||
| .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.
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.