This is what I learnt today and my research after the meetup.
- 85% of mobile users expect site to load as at least fast as, or faster than desktop version
- 45% of users leave with taking longer than 3 seconds to load
I'm going to make a single page website.
I know it's little tricky if I use Drupal to build it. I was considering using a module named [Single Page Website](Single Page Website), however it seems it has many dependency and it's not developing currently.
According to a committer of Single Page Site, he has an experience using "Single Page Website", and I thought why he is building "Single Page Site" is he wasn't satisfied with it with some reason. So I decide using "Single Page Site."
Actually it's my first time using Drupal, so let's see what's going on.
When I participated the first meetup of Code for Canada, a question stays in my mind. Which is "How to find the problem itself?" Because the communities which developers/entrepreneurs have and communities that have issues which should be solved by technology can be different, and I think it'll be better to tackle issues worth devoting time. In my opinion, the issue we start with can be from community where is most familiar to us.
As an activity, I've asked Code for Japan questions below.
Code for Japan has several brigades and each brigade does differently, so it's depends on the brigade. Mainly by Ideathon with government employees, or by interviewing local NPOs.
Followed the original flow of "Building and Testing AngularJS", however it doesn't work to me.
So I made my own flow here.
Note: I am not a pro npm user.
AngularJS v.1.4.3
# clean cache of npm
This is a description of https://github.com/wataruoguchi/AngularJS-TDD-example
your-directory
- index.html
Install packages, selenium server, and web driver
This is what I did after following the tutorial
I love Sass. Let's turn it on.
sudo npm install -g gulp-sass
sudo npm install gulp-sass
sudo ionic setup sass
- The project maintainer pushes to their public repository.
- A contributor clones that repository and makes changes.
- The contributor pushes to their own public copy.
- The contributor sends the maintainer an email asking them to pull changes.
- The maintainer adds the contributor’s repo as a remote and merges locally.
- The maintainer pushes merged changes to the main repository.
We are too small team to do this...