issues
search
jacopotarantino
/
Lovelace
Styleguide and language-agnostic UI component framework.
6
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
2.0 rearchitecture
#20
jacopotarantino
opened
9 years ago
0
Scrap the coffeescript and just use `standard`
#19
jacopotarantino
closed
9 years ago
1
Feature/styleguide
#18
jacopotarantino
closed
9 years ago
0
Feature/angular example
#17
jacopotarantino
closed
9 years ago
0
Lovelace should autogenerate a styleguide.
#16
jacopotarantino
closed
9 years ago
1
Example client app should consume real bower dependency.
#15
jacopotarantino
opened
9 years ago
1
Needs full example node and client apps.
#14
jacopotarantino
closed
9 years ago
1
Needs functioning CLI implementation
#13
jacopotarantino
opened
9 years ago
0
.coffee files should have full inline documentation
#12
jacopotarantino
opened
9 years ago
0
GET THE GODDAMN TEST COVERAGE UP TO 100%
#11
jacopotarantino
opened
9 years ago
1
Documentation task should generate full, browsable site.
#10
jacopotarantino
opened
9 years ago
1
Needs example project for each supported framework
#9
jacopotarantino
opened
9 years ago
0
Needs functioning PHP integration
#8
jacopotarantino
opened
9 years ago
0
Styles, scripts and markup should all be compressed/minified/uglified
#7
jacopotarantino
closed
9 years ago
3
Should client API pull from remote server by default?
#6
jacopotarantino
opened
9 years ago
0
Needs functioning ruby integration
#5
jacopotarantino
closed
9 years ago
2
Needs functioning client-side integration.
#4
jacopotarantino
closed
9 years ago
3
How can other projects use Lovelace without dirtying the repo?
#3
jacopotarantino
opened
9 years ago
3
All server-side abstractions should really just be wrappers for one abstraction layer
#2
jacopotarantino
opened
9 years ago
0
Node API should be async
#1
jacopotarantino
opened
9 years ago
1