Commit eeb6343d authored by gick's avatar gick
Browse files

z

parents
# Created by .ignore support plugin (hsz.mobi)
### Node template
# Logs
logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
# Runtime data
pids
*.pid
*.seed
*.pid.lock
# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov
# Coverage directory used by tools like istanbul
coverage
# nyc test coverage
.nyc_output
# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
.grunt
# Bower dependency directory (https://bower.io/)
bower_components
# node-waf configuration
.lock-wscript
# Compiled binary addons (https://nodejs.org/api/addons.html)
build/Release
# Dependency directories
node_modules/
jspm_packages/
# TypeScript v1 declaration files
typings/
# Optional npm cache directory
.npm
# Optional eslint cache
.eslintcache
# Optional REPL history
.node_repl_history
# Output of 'npm pack'
*.tgz
# Yarn Integrity file
.yarn-integrity
# dotenv environment variables file
.env
# parcel-bundler cache (https://parceljs.org/)
.cache
# next.js build output
.next
# nuxt.js build output
.nuxt
# Nuxt generate
dist
# vuepress build output
.vuepress/dist
# Serverless directories
.serverless
# IDE / Editor
.idea
.editorconfig
# Service worker
sw.*
# Mac OSX
.DS_Store
# Vim swap files
*.swp
# albiziapp-info
> My exceptional Nuxt.js project
## Build Setup
``` bash
# install dependencies
$ npm run install
# serve with hot reload at localhost:3000
$ npm run dev
# build for production and launch server
$ npm run build
$ npm run start
# generate static project
$ npm run generate
```
For detailed explanation on how things work, check out [Nuxt.js docs](https://nuxtjs.org).
# ASSETS
**This directory is not required, you can delete it if you don't want to use it.**
This directory contains your un-compiled assets such as LESS, SASS, or JavaScript.
More information about the usage of this directory in [the documentation](https://nuxtjs.org/guide/assets#webpacked).
<template>
<div class="VueToNuxtLogo">
<div class="Triangle Triangle--two" />
<div class="Triangle Triangle--one" />
<div class="Triangle Triangle--three" />
<div class="Triangle Triangle--four" />
</div>
</template>
<style>
.VueToNuxtLogo {
display: inline-block;
animation: turn 2s linear forwards 1s;
transform: rotateX(180deg);
position: relative;
overflow: hidden;
height: 180px;
width: 245px;
}
.Triangle {
position: absolute;
top: 0;
left: 0;
width: 0;
height: 0;
}
.Triangle--one {
border-left: 105px solid transparent;
border-right: 105px solid transparent;
border-bottom: 180px solid #41b883;
}
.Triangle--two {
top: 30px;
left: 35px;
animation: goright 0.5s linear forwards 3.5s;
border-left: 87.5px solid transparent;
border-right: 87.5px solid transparent;
border-bottom: 150px solid #3b8070;
}
.Triangle--three {
top: 60px;
left: 35px;
animation: goright 0.5s linear forwards 3.5s;
border-left: 70px solid transparent;
border-right: 70px solid transparent;
border-bottom: 120px solid #35495e;
}
.Triangle--four {
top: 120px;
left: 70px;
animation: godown 0.5s linear forwards 3s;
border-left: 35px solid transparent;
border-right: 35px solid transparent;
border-bottom: 60px solid #fff;
}
@keyframes turn {
100% {
transform: rotateX(0deg);
}
}
@keyframes godown {
100% {
top: 180px;
}
}
@keyframes goright {
100% {
left: 70px;
}
}
</style>
# COMPONENTS
**This directory is not required, you can delete it if you don't want to use it.**
The components directory contains your Vue.js Components.
_Nuxt.js doesn't supercharge these components._
# LAYOUTS
**This directory is not required, you can delete it if you don't want to use it.**
This directory contains your Application Layouts.
More information about the usage of this directory in [the documentation](https://nuxtjs.org/guide/views#layouts).
<template>
<div>
<div>
<b-navbar toggleable="lg" type="dark" variant="dark">
<b-navbar-brand href="#">Albiziapp</b-navbar-brand>
<b-navbar-toggle target="nav-collapse"></b-navbar-toggle>
<b-collapse id="nav-collapse" is-nav>
<b-navbar-nav>
<b-nav-item to="/usecases">Use cases</b-nav-item>
<b-nav-item href="/technology">Features</b-nav-item>
</b-navbar-nav>
<!-- Right aligned nav items -->
</b-collapse>
</b-navbar>
</div>
<nuxt />
</div>
</template>
# MIDDLEWARE
**This directory is not required, you can delete it if you don't want to use it.**
This directory contains your application middleware.
Middleware let you define custom functions that can be run before rendering either a page or a group of pages.
More information about the usage of this directory in [the documentation](https://nuxtjs.org/guide/routing#middleware).
export default {
mode: 'universal',
/*
** Headers of the page
*/
head: {
title: process.env.npm_package_name || '',
meta: [
{ charset: 'utf-8' },
{ name: 'viewport', content: 'width=device-width, initial-scale=1' },
{ hid: 'description', name: 'description', content: process.env.npm_package_description || '' }
],
link: [
{ rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' }
]
},
/*
** Customize the progress-bar color
*/
loading: { color: '#fff' },
/*
** Global CSS
*/
css: [
],
/*
** Plugins to load before mounting the App
*/
plugins: [
],
/*
** Nuxt.js dev-modules
*/
devModules: [
],
/*
** Nuxt.js modules
*/
modules: [
// Doc: https://bootstrap-vue.js.org/docs/
'bootstrap-vue/nuxt',
],
/*
** Build configuration
*/
build: {
/*
** You can extend webpack config here
*/
extend (config, ctx) {
}
}
}
This diff is collapsed.
{
"name": "albiziapp-info",
"version": "1.0.0",
"description": "My exceptional Nuxt.js project",
"author": "gick",
"private": true,
"scripts": {
"dev": "nuxt",
"build": "nuxt build",
"start": "nuxt start",
"generate": "nuxt generate"
},
"dependencies": {
"nuxt": "^2.0.0",
"bootstrap-vue": "^2.0.0-rc.11",
"bootstrap": "^4.1.3"
},
"devDependencies": {}
}
# PAGES
This directory contains your Application Views and Routes.
The framework reads all the `*.vue` files inside this directory and creates the router of your application.
More information about the usage of this directory in [the documentation](https://nuxtjs.org/guide/routing).
<template>
<b-container fluid>
<div>
<b-jumbotron style="padding:20px;" header="Albiziapp" lead="Tree mapping made easy and fun">
<p>Part of the REVERIES project</p>
</b-jumbotron>
</div>
<section class="mt-2 custom">
<b-card border-variant="light" title="Location based activities" img-src="/map.png" img-alt="Image" img-left>
<b-card-text>
Albiziapp is conceived for outdoor activities. User position is updated as he moves. The map shows other users records and is updated dynamically.
</b-card-text>
</b-card>
<b-card title="Gamification" img-src="/score.png" img-alt="Image" img-left>
<b-card-text>
Various gamification mechanism. Fully customable score, badge and rank system.
</b-card-text>
</b-card>
<b-card title="Learning through reference images and informations" img-src="/arboretum.png" img-alt="Image" img-left>
<b-card-text>
Information about usage and habitat, as well as reference images for all species.
</b-card-text>
</b-card>
<b-card title="More than 200 normalized species" img-src="/record.png" img-alt="Image" img-left>
<b-card-text>
Recording is assisted through a curated species list, including genus and common name.
</b-card-text>
</b-card>
</section>
</b-container>
</template>
<style>
.custom .card img{
height:300px!important;
width:auto!important;
margin:auto;
}
</style>
<script>
export default {
};
</script>
\ No newline at end of file
<template>
<b-container fluid>
<b-row>
<b-col cols="3">
<b-navbar sticky class="flex-column">
<b-nav pills class="flex-column">
<b-nav-item href="#web">Full web</b-nav-item>
<b-nav-item href="#plant">Plant recognition</b-nav-item>
<b-nav-item href="#item-3">Notifications</b-nav-item>
</b-nav>
</b-navbar>
</b-col>
<b-col cols="9">
<section id="content" class="mt-2 custom">
<h2>Features</h2>
<h4 id="web">Full web and PWA</h4>
<p>
Existing tree mapping applications are, to our best knowledge, only <strong>native applications</strong>.
This means that they require the user to install an application on his smartphone. This creates various
issues : device compatibility (e.g application needs a specific Android version), trust issue (e.g user
can be reluctant to install an application), complex update process...
</p>
<p>
To overcome these issues, Albiziapp is only based on fully standard web technologies. Practically, it means
that it <strong>is accessed through a browser</strong>, without installation required and it runs on any mobile
device.
</p>
<p>
In case the user wish it, Albiziapp support PWA installation. Practically, the user can add Albiziapp to
his desktop and enjoy a fullscreen experience.
</p>
<h4 id="plant">Plant recognition</h4>
<p>
Albiziapp integrate a plant recognition feature. The user can upload a leaf photo to obtain the most likely
species of the leaf. This feature is based on Folia, an application built by the <b-link href="https://liris.cnrs.fr/en/news/liris-diffuse-un-premier-prototype-reconnaissance-feuilles-sur-lappstore">LIRIS</b-link>
</p>
<b-card
border-variant="light"
title="Folia"
img-src="/folia.png"
img-alt="Image"
img-left
>
<b-card-text>
An example of using Folia, the plant recognition feature.
</b-card-text>
</b-card>
</section>
</b-col> </b-row>
</b-container>
</template>
<style>
.custom .card img {
height: 400px !important;
width: auto !important;
margin: auto;
}
</style>
<script>
export default {};
</script>
\ No newline at end of file
<template>
<b-container fluid>
<b-row>
<b-col cols="3">
<b-navbar sticky class="flex-column">
<b-nav pills class="flex-column">
<b-nav-item href="#tour">Botanic Tour</b-nav-item>
<b-nav-item href="#citizen">Citizen science</b-nav-item>
<b-nav-item href="#class">Botanic class</b-nav-item>
</b-nav>
</b-navbar>
</b-col>
<b-col cols="9">
<section id="content" class="mt-2 custom">
<h2>Use cases</h2>
<h4 id="tour">Botanic tour</h4>
<p>
Botanic tour are a way to promote
<strong>biodiversity heritage</strong> in a given area.
Such area can be natural parc, cities, botanic garden, campus... Botanic tour also permits
to acquire botanical knowledge in an easier context than a botanic class.
</p>
<p>
In Albiziapp, botanic tours can be defined through
<strong>custom missions</strong>.
These missions are described through a simple format describing a serie of activities
that the user should perform.
</p>
<b-card
border-variant="light"
title="Example of missions"
img-src="/mission.png"
img-alt="Image"
img-left
>
<b-card-text>
This is an example of mission consisting of a serie of activities.
The current activitie is to perform three new records with distinct genus.
A progress bar indicate the user progression in the current activitie.
</b-card-text>
<b-card-text>When the activitie is completed, the user will acquire new score points and a badge.</b-card-text>
</b-card>
<h4 id="citizen">Citizen science</h4>
TO BE COMPLETED
<h4 id="class">Botanic class</h4>
TO BE COMPLETED
</section>
</b-col> </b-row>
</b-container>
</template>
<style>
.custom .card img {
height: 400px !important;
width: auto !important;
margin: auto;
}
</style>
<script>
export default {};
</script>
\ No newline at end of file
# PLUGINS
**This directory is not required, you can delete it if you don't want to use it.**
This directory contains Javascript plugins that you want to run before mounting the root Vue.js application.
More information about the usage of this directory in [the documentation](https://nuxtjs.org/guide/plugins).
# STATIC
**This directory is not required, you can delete it if you don't want to use it.**
This directory contains your static files.
Each file inside this directory is mapped to `/`.
Thus you'd want to delete this README.md before deploying to production.
Example: `/static/robots.txt` is mapped as `/robots.txt`.
More information about the usage of this directory in [the documentation](https://nuxtjs.org/guide/assets#static).
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment