Closed andi3 closed 8 years ago
Backend: I guess PHP will complicate things a bit more than a JVM based backend. So: Spring or Play. Spring is trustworthy and @aalexandrov has used it before; Play looks really cool. Anyway, we will only need the backend later - after we have a website and we have to build the Scala interpreter. I'd go with Play when we need to.
Frontend: +1 bootstrap. Plays great with Jekyll - I use it for a couple of my own websites.
So you plan to create a static website?
I'd make a static one with bootstrap at first. Apart from the interactive Scala shell, everything else can be static. We can simply edit html/MD files and push to a repository, then publish on the web server (or just use github pages). AFAIK Spark, Flink, Scala, etc. use static websites on which everybody can just easily contribute.
What do you think?
Jeah, OK... i never worked with github pages before. But I'm fine with that.
We've built Stratosphere and Flink's websites with Jekyll and bootstrap. If you need a place to start, just check one of the following repositories: Stratosphere: https://github.com/stratosphere/stratosphere.github.io Mine: https://github.com/asteriosk/web Flink: https://github.com/uce/flink-web
You could use mine, for instance. You only need to change (or delete) the main.css and theme.css and update the files to a more recent bootstrap.
Check Jekyll - you'll love it! Then, hosting on github pages under our domain name is very easy.
If you need any help, come by my office!
+1 for Bootstrap with a Bootswatch generated theme, should lower the barrier of entry for new contributors.
I agree with @asteriosk: the website can be static for the first iterations.
For the demo, I guess it would make things easier if we have a Scala-based JVM, so I'm leaning towards Play. @andi3: can you open a separate planning meta-issue for the demo?
First draft for the homepage:
I used the foundation css framework, which is basically the same like bootstrap...
berkshire swash:
cookie:
courgette:
damion:
niconne:
norican:
pacifico:
satisfy:
+1 for cookie
+2 cookie +1 damion
Cheers, Asterios
On 4 Aug 2015 at 10:48:56, Georgi Krastev (notifications@github.com) wrote:
+1 for cookie
— Reply to this email directly or view it on GitHub.
Is the logo going to appear next to it somehow? I think cookie and pacifico would look nice next to the logo.
The website needs another pass before the 0.1.0 release, but I will open another issue for that.
This is the meta-issue tracking the progress on the Emma Website and pointing to sub-issues.
Technologies
We the following choice of technologies.
Backend Frameworks
I am very familiar with the YII framework (PHP), but I also worked at some projects with the Play (JAVA) and spring boot (JAVA) frameworks. Are there any preferences?? I think a java framework would be more suitable for our purpose (invoking the emma plans with java).
YII (PHP)Play (Java/Scala)Spring (Java)Frontend CSS frameworks
Bootstrap / BootswatchMaterial UIPalettes
Fonts
Tasks