Commit 872fb0d4 authored by Mayel's avatar Mayel

Merge branch 'develop'

parents 1861d106 562fe7d7
# All available Hugo versions are listed here: https://gitlab.com/pages/hugo/container_registry
image: registry.gitlab.com/pages/hugo:latest
image: registry.gitlab.com/yaegashi/hugo/hugo_extended:latest
stages:
- build
......
baseURL: ./
baseURL: /
languageCode: en-us
title: MoodleNet
theme: hugo-fresh
......@@ -29,25 +29,31 @@ params:
#maintenance_mode: We're currently fixing a few things behind the scenes.
# Customizable navbar. For a dropdown, add a "sublinks" list.
navbar:
- title: Timeline
url: "#section2"
- title: Principles
url: "#section1"
# - title: Timeline
# url: "#section2"
- title: Blog
url: http://blog.moodle.net
- title: Participate
- title: Wiki
url: https://docs.moodle.org/dev/MoodleNet
- title: Suggestions
url: https://changemap.co/moodle/moodlenet/
- title: Discussion Forum
url: "https://moodle.org/mod/forum/view.php?id=8352"
- title: Source Code
url: https://gitlab.com/moodlenet
- title: Fine Print
sublinks:
- title: Wiki
url: https://docs.moodle.org/dev/MoodleNet
- title: Suggestions
url: https://changemap.co/moodle/moodlenet/
- title: Discussion Forum
url: "https://moodle.org/mod/forum/view.php?id=8352"
- title: Source Code
url: https://gitlab.com/moodlenet
- title: Sign up
url: https://blog.moodle.net/2019/federation-testing-programme/
button: true
- title: User Agreement
url: /terms/users/index.html
- title: Instance Admin Agreement
url: /terms/admins/index.html
- title: Privacy
url: /terms/privacy/index.html
- title: Cookies
url: /terms/cookies/index.html
# - title: Sign up
# url: https://blog.moodle.net/2019/federation-testing-programme/
# button: true
section1:
title: Foundational principles of MoodleNet
# subtitle: with great responsibility
......@@ -62,7 +68,7 @@ params:
text: Secure, standards-based, and GDPR-compliant. MoodleNet communities are moderated by you and your peers, not by a single central organisation.
- title: Private
icon: private
text: Share as little about yourself as you’re comfortable with, and control who sees what you post, thanks to MoodleNet’s granular privacy controls.
text: MoodleNet is developed using a Privacy By Design approach, meaning you can share as much about yourself as you are comfortable with.
tiles2:
- title: Ethical
icon: badge
......@@ -73,35 +79,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
......
---
title: MoodleNet Mothership Terms & Conditions for Instance Administrators
sidebar: false
include_footer: true
---
{{< include_md file="/static/terms/admins.md" >}}
\ No newline at end of file
---
title: MoodleNet Cookies Policy
sidebar: false
include_footer: true
---
{{< include_md file="/static/terms/cookies.md" >}}
\ No newline at end of file
---
title: Consent for data processing by the MoodleNet search index (aka "mothership")
sidebar: false
include_footer: true
---
{{< include_md file="/static/terms/indexing.md" >}}
\ No newline at end of file
---
title: MoodleNet Privacy Notice
sidebar: false
include_footer: true
---
{{< include_md file="/static/terms/privacy.md" >}}
\ No newline at end of file
---
title: MoodleNet User Agreement
sidebar: false
include_footer: true
---
{{< include_md file="/static/terms/users.md" >}}
\ No newline at end of file
......@@ -17,14 +17,7 @@
{{ 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 }}
......
<!DOCTYPE html>
<html lang="{{ .Site.LanguageCode }}">
<head>
{{ partial "meta.html" . }}
<title>{{ .Params.title }}</title>
{{ partial "css.html" . }}
</head>
<body>
<!-- Preloader -->
<div id="preloader">
<div id="status"></div>
</div>
{{ partial "single/single.html" . }}
<!-- Back To Top Button -->
<div id="backtotop"><a href="#"></a></div>
{{ if .Params.sidebar }}
{{ partial "single/sidebar.html" . }}
{{ end }}
{{ partial "javascript.html" . }}
</body>
</html>
@charset "utf-8"
@import "generic.sass"
@import "helpers.sass"
......@@ -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">
......
......@@ -27,15 +27,7 @@
</h2>
{{ end }}
<p>
<a class="button cta rounded secondary-btn raised" href="{{ $buttonLink }}">
{{ $buttonText }}
</a>
<a class="button cta rounded btn raised" href="{{ $moreLink }}">
Find out more
</a>
</p>
</div>
</div>
......
......@@ -4,6 +4,8 @@
{{- $tiles := index $section1 "tiles" }}
{{- $tiles2 := index $section1 "tiles2" }}
<section id="section1" class="section section-feature-grey">
<div class="container">
<div class="title-wrapper has-text-centered">
......
......@@ -4,13 +4,60 @@
{{- $image := index $section3 "image" }}
{{- $buttonText := index $section3 "buttontext" }}
{{- $buttonLink := index $section3 "buttonlink" }}
<section class="section">
<div class="container">
<div class="columns">
<div class="column">
<div class="box">
<h2 class="title is-4">Join a MoodleNet instance</h2>
<p>MoodleNet is a network of independent websites for educators all running the same software. It's what's known as a <strong>federated</strong> social network. While every website is slightly different in terms of content and emphasis, being part of one is being part of the whole.</p>
<p style="margin-top: 15px;">
<div class="dropdown is-hoverable">
<div class="dropdown-trigger">
<button style="height: 42px;" class="button secondary-btn raised" aria-haspopup="true" aria-controls="dropdown-menu">
<span>Choose an instance to sign up</span>
</button>
</div>
<div class="dropdown-menu" id="dropdown-menu" role="menu">
<div class="dropdown-content">
<!-- <a href="https://home.moodle.net" class="dropdown-item">
home.moodle.net
</a>
<hr class="dropdown-divider"> -->
<a href="#" class="dropdown-item">
Coming soon...
</a>
</div>
</div>
</div>
</p>
</div>
</div>
<div class="column">
<div class="box">
<h2 class="title is-4">Set up your own MoodleNet instance</h2>
<p>MoodleNet is Free and Open Source Software (under the <a href="https://www.gnu.org/licenses/agpl-3.0.en.html">AGPL</a> licence) which can federate with other instances of MoodleNet and other compatible <a href="https://activitypub.rocks/">ActivityPub</a> servers. You are encouraged to run an instance yourself, to increase the diversity and resiliency of the federated network.</p>
<p style="margin-top: 15px;"><a style="height: 30px;" class="button secondary-btn raised" href="https://gitlab.com/moodlenet/clients/react#deploying-moodlenet">
How to deploy an instance
</a></p>
</div>
</div>
</div>
</div>
</section>
<section id="section3" class="section is-medium mt-50">
<div class="container">
<div class="columns">
<div class="column mt-50 is-10 is-offset-1">
<div class="column is-10 is-offset-1">
<div class="has-text-centered">
<img class="pushed-image" src="{{ printf "/images/%s" $image | relURL }}">
<!-- <p>Screenshot of a community on MoodleNet</p> -->
<!-- <img class="" src="{{ printf "/images/%s" $image | relURL }}"> -->
<iframe width="840" height="472" src="https://www.youtube-nocookie.com/embed/lsrcHPh77fs?controls=0" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
</div>
</div>
......@@ -18,7 +65,7 @@
</div>
</section>
<section class="section section-feature-grey is-medium">
<!-- <section class="section section-feature-grey is-medium">
<div class="container">
<div class="has-text-centered">
......@@ -33,4 +80,4 @@
</p>
</div>
</section>
\ No newline at end of file
</section> -->
\ No newline at end of file
<section class="section is-medium">
<div class="container">
<!-- <div class="columns">
<div class="column is-centered-tablet-portrait">
<h1 class="title section-title">{{ .Title }}</h1>
<h5 class="subtitle is-5 is-muted">{{ .Params.Subtitle }}</h5>
<div class="divider"></div>
</div>
</div> -->
{{ .Content }}
</div>
</section>
{{ readFile .Params.file | markdownify }}
<hr/>
<p align="right"><a href="{{ replace .Params.file "/static/" "/"}}">Download as Markdown text file</a> | <a href="/">Home</a></p>
\ No newline at end of file
static/images/screenshot.png

1.56 MB | W: | H:

static/images/screenshot.png

1.25 MB | W: | H:

static/images/screenshot.png
static/images/screenshot.png
static/images/screenshot.png
static/images/screenshot.png
  • 2-up
  • Swipe
  • Onion skin
......@@ -37,4 +37,13 @@ footer.footer-dark a {
.notification.is-secondary, .notification.is-secondary span {
background-color: #f98012;
color: #fff !important;
}
table {
border-collapse: collapse;
}
table td, table th {
padding: 6px;
border: 1px solid #ccc;
}
\ No newline at end of file
# MoodleNet Mothership Terms & Conditions for Instance Administrators
MoodleNet is a federated social network. As such, we cannot control everything that happens on the network, but nevertheless commit to make our best effort to guarantee a safe experience to MoodleNet users. For this reason we have created a MoodleNet Mothership Server Terms & Conditions in order to provide people a safe and friendly experience without compromising the open and federated nature of the project.
Administrators of MoodleNet servers (“instances”) have the option of connecting to Moodle HQ’s ‘Mothership’. This means that content stored on those instances appears both in network-wide search results, and in recommendations to other users.
To connect to the Mothership, administrators of MoodleNet instances **must commit to the following:**
1. **Foster an open and welcoming environment.** All of us (Moodle HQ, instance administrators, community moderators, and all MoodleNet participants) need to work together to maintain a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
2. **Actively moderate their instance** against racism, sexism, homophobia, transphobia, harassment, defamation, doxxing, sexual depictions of children, and conduct promoting alt-right and fascist ideologies. We want to give users the confidence that they are joining a safe place, and as such we cannot support or promote anyone spreading intolerance and hate. A [MoodleNet User Agreement](/terms/users/index.html) has been written for this purpose. Instance administrators must **monitor and be responsive to flagged content** and other user reports, and make sure every community hosted on the instance is properly moderated.
3. **Perform daily backups.** This is a basic necessity to protect from loss of user data. We recommend storing an archive of daily, weekly, and monthly backups.
4. **Give emergency access to the server infrastructure to at least two people.** The ability for others to access the MoodleNet server is a key aspect to address technical emergencies.
5. **Obtain valid consent of users**, this is required in order to provide MoodleNet service and process users personal data as part of the Moodle HQ’s ‘Mothership’. A document to obtain [consent for data processing by the MoodleNet search index (aka "mothership")](/terms/indexing/index.html) has been prepared for this purpose.
6. **Give users at least 3 months of advance warning in case of shutting down.** Users must have the confidence that their account will not suddenly disappear and therefore is vital to give them the time and the chance to export their data and migrate to another instance.
7. **Make available the source code of any customisations to your instance**, regardless how small. This is required by the AGPL licence anyway, but is always worth repeating.
If you are a MoodleNet instance administrator and can commit to the above, you can gain an API key. Please note that only instances that accept registrations from the public will be shown in the instance picker.
# **MoodleNet Cookies Policy**
*Effective: 1st of November 2019*
The operators of this MoodleNet site use cookies on this website and all affiliated websites (collectively the "Site").
Our Cookies Policy explains what cookies are, how we use cookies, how third-parties we partner with may use cookies on the Site, and your choices regarding cookies. Please read this Cookies Policy in conjunction with our Privacy Notice (see below), which sets out additional details on how we use personally identifiable information and your various rights.
## **What are cookies**
Cookies are small pieces of text sent by your web browser by a website you visit. A cookie file is stored in your web browser and allows the Site or a third-party to recognize you and make your next visit easier and the Site more useful to you. Essentially, cookies are a user’s identification card for our servers. Cookies allow us to serve you better and more efficiently, and to personalize your experience on our Site.
Cookies can be "persistent" or "session" cookies.
## **How MoodleNet uses cookies**
When you use and access the Site, we may place a number of cookies files in your web browser.
MoodleNet uses or may use cookies to help us determine and identify repeat visitors, the type of content and sites to which a user of our Site links, the length of time each user spends at any particular area of our Site, and the specific functionalities that users choose to use. To the extent that cookies data constitutes personally identifiable information, we process such data on the basis of your consent.
We use both session and persistent cookies on the Site and we use different types of cookies to run the Site:
- _Essential cookies._ Necessary for the operation of the Site. We may use essential cookies to authenticate users, prevent fraudulent use of user accounts, or offer Site features.
- _Analytical/performance cookies._ Allow us to recognize and count the number of visitors and see how visitors move around the Site when using it. This helps us improve the way the Site works.
- _Functionality cookies._ Used to recognise you when you return to the Site. This enables us to personalise our content for you, greet you by name, and remember your preferences (for example, your choice of language or region).
To view a list of MoodleNet cookies, please view ourCookies table below.
## **Third-party cookies**
In addition to our own cookies, we may also use various third-party cookies to report usage statistics of the Site.
- _Tracking cookies._ Follow on-site behaviour and tie it to other metrics allowing better understanding of usage habits.
To view a list of third-party cookies that we use, please view our Cookies table below.
## **What are your choices regarding cookies**
If you'd like to delete cookies or instruct your web browser to delete or refuse cookies, please visit the help pages of your web browser.
Please note, however, that if you delete cookies or refuse to accept them, you might not be able to use some or all of the features we offer. You may not be able to log in, store your preferences, and some of our pages might not display properly.
## **Cookies Tables**
The tables below list some of the internal and third-party cookies we use. As the names, numbers, and purposes of these cookies may change over time, this page may be updated to reflect those changes. For more information on how we use these cookies, please refer to ourCookies Policy above.
### **MoodleNet Cookies**
| **Cookie Name** | **Purpose** | **Expiration** |
| --------------- | ---------------------------------- | -------------- |
| locale | Functionality (interface language) | n/a |
| SESSION#ME | Essential (user login session) | n/a |
### **Third-Party Cookies**
| **Provider Name** | **Cookie Name** | **Purpose** | **Expiration** | **More information** |
| ----------------- | ----------------- | ------------------------------------------------------- | -------------- | --------------------------------------------------------------------- |
| Algolia | algolia-client-js | Analytical/performance & Tracking (search optimisation) | n/a | More [details from Algolia](https://www.algolia.com/policies/cookies). |
# Consent for data processing by the MoodleNet search index (aka "mothership")
[Moodle Pty Ltd](http://moodle.com) is a software company which develops and operates collaborative educational tools. [MoodleNet](http://moodle.net) is open source, and may be hosted by Moodle Pty Ltd, but also by anyone who wishes to manage an installation.
For instances _not_ hosted by Moodle Pty Ltd, they also provide the optional "mothership" API service that indexes public data as well as provides search and discovery across federated instances.
It is not compulsory for third party instances, such as ours, to link their instance of MoodleNet to the MoodleNet "mothership". However we have chosen to connect our instance, for the benefits we think it will offer.
Moodle Pty Ltd may therefore process your personal data for the purposes of offering additional functionality to the federated social network made up of individually hosted installations of MoodleNet software. This should lead to increased searchability, discovery, and sharing of resources and ideas amongst the educators using federated MoodleNet instances. Users will be able to find one another, discover relevant communities and collections, and find the resources they need.
This document exists to request you to give specific, valid and informed consent to the form of data processing this federation requires.
In [GDPR](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation) (General Data Protection Regulation 2016/679 of EU) terms adopted by Moodle Pty Ltd as global standard, their relationship with our instance is therefore both as:
- Joint Data Controller (in respect of certain elements of personal data made public by users which Moodle Pty Ltd makes searchable across the federated instances connected to the MoodleNet "mothership")
- Data Processor (Instance administrators act as the Data Controller, and can request Moodle Pty Ltd to delete personal data on the data subject from the MoodleNet "mothership")
The specific categories of data and forms of processing which will be completed by Moodle Pty Ltd will be the following:
| **CATEGORIES OF PERSONAL DATA** | **WHAT COULD BE INFERRED FROM THE DATA** | **PURPOSE OF PROCESSING** | **THE SOURCE OF PERSONAL DATA** |
| --- | --- | --- | --- |
| **Display name, avatar, bio, interests, language, occupation, location, tags** | workplace, origin, politicalopinions, religious beliefs, gender, sexuality, accessibility requirements | User registration | Data subject (user) |
| **Descriptions, language, metadata** | interests, occupation, location, workplace, location, origin, politicalopinions, religious beliefs, gender, sexuality, accessibility requirements | Describing communities, collections, or shared resources | Data subject (user) |
| **IP address** | geolocation of connection to the service | Connecting users to the service | Data subject (user) |
| **Details about browser and device** | accessibility requirements | Ensuring the service is accessible to all users | Data subject (user) |
| **Search history** | political beliefs, religious beliefs, sexuality, accessibility requirements | Improving user experience | Data subject (user) |
If you choose to enter any information involving a special category of personal data (for example, entering details about your racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning your sex life or sexual orientation) in your own personal profile, in comments, or anywhere else on this site, then we and Moodle Pty Ltd will rely on this informed consent to be able to process that data.
You have the right to withdraw consent for the processing of personal data at any time by contacting the admin of this instance, or failing that, by notifying Moodle Pty Ltd on <mailto:privacy@moodle.com>.
This diff is collapsed.
# MoodleNet User Agreement
### 1. Terms
By accessing or using this MoodleNet instance (an installation of MoodleNet, a social web application that can connect you with people and communities on any instance of MoodleNet or other federated apps, aka the "fediverse"), you are agreeing to be bound by these terms, and all applicable laws and regulations. If you do not agree with any of these terms, you are prohibited from using or accessing this instance.
### 2. Code of Conduct
#### 2.1 Pledge
In the interest of fostering an open and welcoming environment, we as contributors and project maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
#### 2.2 Encouraged Behaviour
Examples of behaviour that contributes to creating a positive environment include:
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members
#### 2.3 Unacceptable Behaviour
Racism, sexism, homophobia, transphobia, harassment, defamation, doxxing, sexual depictions of children, and conduct promoting alt-right and fascist ideologies will not be tolerated.
Other examples of unacceptable behaviour by participants include:
- Unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others’ private information, such as a physical or electronic address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting
#### 2.4 Responsibilities of users and contributors
Users and contributors are responsible for watching out for any unacceptable behaviour or content, such as harassment, and bringing it to moderators' attention by using the flagging functionality. If community moderators do not respond in a timely or appropriate manner, users are to alert the instance administrators, and failing that,Moodle Pty Ltd “Moodle HQ” at <mailto:moodlenet-moderators@moodle.com>.
#### 2.5 Responsibilities of the project maintainers
Project maintainers (including instanceadministrators, community moderators, and Moodle HQ, given the relevant access) are responsible for monitoring and acting on flagged content and other user reports, and have the right and responsibility to remove, edit, or reject comments, communities, collections, resources, images, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to suspend, block or ban (temporarily or permanently) any contributor, community, or instance for breaking these terms, or for other behaviours that they deem inappropriate, threatening, offensive, or harmful.
Instanceadministrators should ensure that every community hosted on the instance is properly moderated according to the Code of Conduct.
Project maintainers are responsible for clarifying the standards of acceptable behaviour and are expected to take appropriate and fair corrective action in response to any unacceptable behaviour.
#### 2.6 Enforcement
All complaints must be reviewed and investigated by project maintainers, and should result in a response that is deemed necessary and appropriate to the circumstances. Project maintainers are obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other project maintainers.
#### 2.7 Code of Conduct Attribution
This Code of Conduct was adapted from the [ Contributor Covenant](https://www.contributor-covenant.org/) ([CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)), [version 1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html).
### 3. Contribution, Use, Modification and Distribution Licenses
1. The software and materials contained in this website are protected by applicable copyright law and open source or similar licences as indicated.
2. Unless otherwise noted, all content or materials contributed on this instance (including resources, metadata, and contents of public discussions) is made available under a [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license](https://creativecommons.org/licenses/by-sa/4.0/). This does not necessarily include links to external instances or websites.
3. MoodleNet is powered by free software, meaning that you have the following basic freedoms:
- The freedom to run the software as you wish, for any purpose.
- The freedom to study how the software works, and change it so it does your computing as you wish. Access to the source code is a precondition for this.
- The freedom to redistribute copies so you can help others.
- The freedom to distribute copies of your modified versions to others. By doing this you can give the whole community a chance to benefit from your changes.
4. Permission is granted to run, study, redistribute, and distribute modified copies of the MoodleNet software according to the terms of the [GNU Affero Public License 3.0](https://www.gnu.org/licenses/agpl-3.0.en.html) (“AGPL”). Note that this is different to the GPL license used for Moodle Core. The AGPL mandates that the source of your MoodleNet instance must be available to be downloaded even if you are providing a service rather than making available a downloadable app. Further information is available at [tl;drlegal](https://tldrlegal.com/license/gnu-affero-general-public-license-v3-(agpl-3.0)).
### 4. Disclaimers
#### 4.1. Materials provided 'as is'
The materials on this instance (and on the "fediverse" at-large) have been contributed by other users, and are provided on an 'as is' basis. Neither the instance administrators, nor Moodle HQ, make any warranties, expressed or implied. They hereby disclaim and negate all other warranties including, without limitation, implied warranties or conditions of merchantability, fitness for a particular purpose, or non-infringement of intellectual property or other violation of rights.
#### 4.2. Accuracy
Furthermore, neither the instance administrators, nor Moodle HQ, make any representations concerning the accuracy, likely results, or reliability of use of the materials found on this instance - which may be incomplete or outdated, or could include technical, typographical, or photographic errors - or relating to such materials or on any sites linked from this instance.
Changes may be made to the materials contained on its instance at any time without notice. However, neither the instance administrators nor Moodle HQ make any commitment to update the materials.
#### 4.3. Links
Neither the instance administrators nor Moodle HQ have reviewed all of the websites, pages or resources linked or uploaded on this instance (or on the "fediverse" at-large) and are not responsible for the contents of any such links. The inclusion of any link does not imply endorsement of the site. Use of any such linked resource is at the user's own risk.
#### 4.4. Limitations
In no event shall the instance administrators, Moodle HQ, or their suppliers be liable for any damages (including, without limitation, damages for loss of data or profit, or due to business interruption) arising out of the use or inability to use the materials on this instance (or on the "fediverse" at-large), even if any authorised representative has been notified orally or in writing of the possibility of such damage. Because some jurisdictions do not allow limitations on implied warranties, or limitations of liability for consequential or incidental damages, these limitations may not apply to you.
### 5. Modifications
These terms of service may be revised at any time without notice, though the instance administrators will be notified of any significant change, and in turn they should notify you. By continuing to use this instance, you are agreeing to be bound by the published current version of these terms. For the avoidance of any doubt, these terms are applicable in addition to the terms that may be added by the instance administrators. In any case those instance-specific terms shall not reduce or replace these terms and in case of conflict these terms shall prevail.
@charset "utf-8"
@import "minireset.sass"
@import "generic.sass"
@import "helpers.sass"
/*! minireset.css v0.0.3 | MIT License | github.com/jgthms/minireset.css */
// Blocks
html,
body,
p,
ol,
ul,
li,
dl,
dt,
dd,
blockquote,
figure,
fieldset,
legend,
textarea,
pre,
iframe,
hr,
h1,
h2,
h3,
h4,
h5,
h6
margin: 0
padding: 0
// Headings
h1,
h2,
h3,
h4,
h5,
h6
font-size: 100%
font-weight: normal
// List
ul
list-style: none
// Form
button,
input,
select,
textarea
margin: 0
// Box sizing
html
box-sizing: border-box
*
&,
&::before,
&::after
box-sizing: inherit
// Media
img,
audio,
video
height: auto
max-width: 100%
// Iframe
iframe
border: 0
// Table
table
border-collapse: collapse
border-spacing: 0
td,
th
padding: 0
text-align: left
......@@ -2,8 +2,10 @@
{{- $title := index $section1 "title" }}
{{- $subtitle := index $section1 "subtitle" }}
{{- $tiles := index $section1 "tiles" }}
<section class="section section-feature-grey is-medium">
<div class="container">
<div class="title-wrapper has-text-centered">
<h2 class="title is-2">{{ $title }}</h2>
<h3 class="subtitle is-5 is-muted">{{ $subtitle }}</h3>
......