Commit ec1c575a authored by Mayel's avatar Mayel

archive link

parent 63edc639
......@@ -73,35 +73,35 @@ params:
- title: Connected
icon: connected
text: Bringing educators together from around the world, MoodleNet exists to create new connections and strengthen existing ones.
section2:
title: Timeline of MoodleNet's development
# subtitle: And we know it
features:
- title: Conceive
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: 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: 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: 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: 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 also involve setting up an HQ-run API-as-a-service to power search, which also needs testing.
icon: scientist
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: default
# section2:
# title: Timeline of MoodleNet's development
# # subtitle: And we know it
# features:
# - title: Conceive
# 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: 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: 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: 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: 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 also involve setting up an HQ-run API-as-a-service to power search, which also needs testing.
# icon: scientist
# 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: default
section3:
title: Get involved in the MoodleNet project
# subtitle: To rule them all
......
......@@ -4,6 +4,20 @@
{{- $quickLinks := index $footer "quicklinks" }}
{{- $socialMedia := index $footer "socialmedia" }}
{{- $bulmaLogo := index $footer "bulmalogo" }}
<div class="container" style="text-align: center;">
<div class="message is-dark is-medium" style="max-width: 500px; display: inline-block;">
<div class="message-header">
<p>The old moodle.net website has been archived</p>
<button class="delete" aria-label="delete"></button>
</div>
<div class="message-body">
Visit <a href="https://archive.moodle.net" target="_blank">archive.moodle.net</a> for courses and content previously shared on moodle.net
</div>
</div>
</div>
<footer class="footer footer-dark">
<div class="container">
<div class="columns">
......
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