Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

User:Sam Hemelryk/Output 2.8 GDM reference: Difference between revisions

From MoodleDocs
No edit summary
Line 3: Line 3:
Is the start of a large movement to organise and improve output in Moodle.
Is the start of a large movement to organise and improve output in Moodle.


Overall project goals:
What we're going to be doing:
# Adoption + creation of elements.
* Adoption + creation of elements.
# Addition of element library.
* Addition of element library.
# Output documentation.
* Output documentation.
 
What we are trying to achieve:
* Standardise output in Moodle so that interfaces are more consistent, accessible, usable and every other buzz word to describe would could be summed up as a good quality.
* Make Moodle much easier to style, with the ultimate goal of making it possible to apply any frontend framework to Moodle with much greater ease.
* Speed up the development of interfaces in Moodle by providing developers with a selection of ready to use elements.
* Speed up the styling of interfaces by providing tools to aid designers in viewing the available elements in their available states without having to discover them.


==The specification==
==The specification==

Revision as of 12:05, 22 July 2014

General developer meeting output summary

Is the start of a large movement to organise and improve output in Moodle.

What we're going to be doing:

  • Adoption + creation of elements.
  • Addition of element library.
  • Output documentation.

What we are trying to achieve:

  • Standardise output in Moodle so that interfaces are more consistent, accessible, usable and every other buzz word to describe would could be summed up as a good quality.
  • Make Moodle much easier to style, with the ultimate goal of making it possible to apply any frontend framework to Moodle with much greater ease.
  • Speed up the development of interfaces in Moodle by providing developers with a selection of ready to use elements.
  • Speed up the styling of interfaces by providing tools to aid designers in viewing the available elements in their available states without having to discover them.

The specification

Elements and Atomic design

The element library

Documentation

Renderer best practices

A Renderer best practices document has been started to aid people in writing better renderers.

To summarise some key ideas that have come through it:

Element HTML and CSS guidelines

An Element HTML and CSS guidelines document has been started outlining a style guide for writing HTML and CSS for elements.
Important to note that this document is not intended to be applied outside of elements at present. As we are hoping to move entirely towards elements one day this will be the HTML and CSS guide for Moodle. However it will not be enforced in current output, its use may be recommended.

Key ideas in this document include:


Guide to creating output elements

A document titled Guide to creating output elements has been written already on how to write an output element.
This will aid us and others in writing consistent elements that conform to the ideals we have chosen.

Relevant links

Docs pages

Tracker issues