Commit eedb45d7 authored by Mayel's avatar Mayel

layout

parent 7314cc9a
......@@ -27,10 +27,10 @@ params:
image: logos/moodlenet-logo.png
# Customizable navbar. For a dropdown, add a "sublinks" list.
navbar:
- title: Principles
url: "#section1"
- title: Timeline
url: "#section2"
- title: Principles
url: "#section1"
- title: Blog
url: http://blog.moodle.net
- title: Participate
......@@ -79,31 +79,31 @@ params:
text: We started by researching our options and came up with a high-level goal for a platform that will be of immediate use to educators. This involved talking to a lot of educators and technologists, and looking to other platforms and services for inspiration.
# Icon (from /images/illustrations/icons/___.svg)
icon: brainstorming
status: primary
status: default
- title: Plan
text: We then focused on planning how to achieve our high-level goal, deciding on the functionality it should have. We ran a design sprint to ensure we had a coherent plan focused on developing a Minimum Viable Product (MVP). We also hired Mayel, our Technical Architect to ensure that we make the correct technical decisions.
icon: flow-chart
status: primary
status: default
- title: Develop
text: In this phase we developed prototypes and worked with Outlandish on the front-end development. We hired Alex, a backend developer, who built out the crucial plumbing using Elixir.
icon: computer
status: primary
status: default
- title: Iterate
text: This phase was about iterating existing designs and approaches so we could be laser-focused on producing something of value to educators. We onboarded Ivan as our designer and front-end developer, and brought together the front-end and backend development work. We did some early testing around the sign-up process, and re-imagined it to ensure there's no blockers for testing.
icon: tweaking
status: primary
status: default
- title: Test
text: We launched the first version of MoodleNet to a group of alpha testers in January 2019. We recruited 100 users to test the platform, to rapidly iterate the platform based on their feedback. We'll then give them invites to share with friends and colleagues, meaning we grow organically and sustainably. In addition, we will be working on testing federation so that MoodleNet instances can communicate with one another. This will involve setting up a HQ-run API-as-a-service, which also needs testing.
text: We launched the first version of MoodleNet to a group of alpha testers in January 2019. We recruited 100 users to test the platform, to rapidly iterate the platform based on their feedback. We'll then give them invites to share with friends and colleagues, meaning we grow organically and sustainably. In addition, we will be working on testing federation so that MoodleNet instances can communicate with one another. This will also involve setting up an HQ-run API-as-a-service to power search, which also needs testing.
icon: scientist
status: link
status: secondary
- title: Launch
text: Once we've tested both the value proposition and federation, we'll double-down on fixing bugs and responding to user needs before opening registrations. During this quarter we aim to develop a plugin to allow users to send collections from MoodleNet to courses in Moodle Core.
icon: startup
status: info
status: default
section3:
title: Get involved in the MoodleNet project
# subtitle: To rule them all
image: screenshot.jpg
image: screenshot.png
buttonText: Sign up to test
buttonLink: https://docs.moodle.org/dev/MoodleNet/Testing
# section4:
......
<!DOCTYPE html>
<html lang="{{ .Site.LanguageCode }}">
<head>
{{ partial "meta.html" . }}
<title>{{ block "title" . }}{{ .Site.Title }}{{ end }}</title>
{{ partial "css.html" . }}
</head>
<body>
<!-- Preloader -->
<div id="preloader">
<div id="status"></div>
</div>
{{ block "main" . }}
{{ if .Site.Params.hero }}
{{ partial "hero.html" . }}
{{ end }}
{{ if .Site.Params.section2 }}
{{ partial "section2.html" . }}
{{ end }}
{{ if .Site.Params.section1 }}
{{ partial "section1.html" . }}
{{ end }}
{{ if .Site.Params.section3 }}
{{ partial "section3.html" . }}
{{ end }}
{{ if .Site.Params.section4 }}
{{ partial "section4.html" . }}
{{ end }}
{{ if .Site.Params.section5 }}
{{ partial "section5.html" . }}
{{ end }}
{{ if .Site.Params.footer }}
{{ partial "footer.html" . }}
{{ end }}
<!-- Back To Top Button -->
<div id="backtotop"><a href="#"></a></div>
{{ if .Site.Params.sidebar }}
{{ partial "sidebar.html" . }}
{{ end }}
{{ end }}
{{ partial "javascript.html" . }}
</body>
</html>
......@@ -19,7 +19,7 @@
</p>
</figure>
<div class="media-content mt-50">
<div class="content notification is-default">
<div class="content notification is-{{ .status }}">
<p>
<!-- <span class="tag is-{{ .status }}">
{{ if (eq .status "success") }}
......
......@@ -33,3 +33,8 @@ footer.footer-dark a {
width: 100px;
text-align: center;
}
.notification.is-secondary, .notification.is-secondary span {
background-color: #f98012;
color: #fff !important;
}
\ No newline at end of file
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