christianlight/tutor
6
0
Fork 0
mirror of https://github.com/ChristianLight/tutor.git synced 2025-01-22 13:18:24 +00:00
Code Issues Releases Activity
tutor/docs/Makefile

18 lines
383 B
Makefile
Raw Normal View History

Improve documentation
2018-12-26 16:00:47 +01:00
.DEFAULT_GOAL := html
Better documentation - More concise table of contents - New intro - Simpler make commands - Fix a couple typos here and there - Get rid of the default github issue template, and start using the template created online.
2019-05-13 16:33:26 +02:00
.PHONY: help
Migrate openedx-docker project to Tutor :woman_teacher: The project gets a new name and some proper documentation. Build/Deploy are now properly separated.
2018-12-03 19:59:09 +01:00
docs: keep running "make watch" on failure
2021-11-23 17:59:14 +01:00
build:
sphinx-build -b html -a -E -n $(BUILD_ARGS) "." "_build/html"
Better documentation - More concise table of contents - New intro - Simpler make commands - Fix a couple typos here and there - Get rid of the default github issue template, and start using the template created online.
2019-05-13 16:33:26 +02:00
html:
docs: keep running "make watch" on failure
2021-11-23 17:59:14 +01:00
$(MAKE) build BUILD_ARGS="-W"
Migrate openedx-docker project to Tutor :woman_teacher: The project gets a new name and some proper documentation. Build/Deploy are now properly separated.
2018-12-03 19:59:09 +01:00
Improve documentation
2018-12-26 16:00:47 +01:00
browse:
sensible-browser _build/html/index.html
docs: keep running "make watch" on failure
2021-11-23 17:59:14 +01:00
watch: build browse
feat: migrate to plugins.v1 with filters & actions This is a very large refactoring which aims at making Tutor both more extendable and more generic. Historically, the Tutor plugin system was designed as an ad-hoc solution to allow developers to modify their own Open edX platforms without having to fork Tutor. The plugin API was simple, but limited, because of its ad-hoc nature. As a consequence, there were many things that plugin developers could not do, such as extending different parts of the CLI or adding custom template filters. Here, we refactor the whole codebase to make use of a generic plugin system. This system was inspired by the Wordpress plugin API and the Open edX "hooks and filters" API. The various components are added to a small core thanks to a set of actions and filters. Actions are callback functions that can be triggered at different points of the application lifecycle. Filters are functions that modify some data. Both actions and filters are collectively named as "hooks". Hooks can optionally be created within a certain context, which makes it easier to keep track of which application created which callback. This new hooks system allows us to provide a Python API that developers can use to extend their applications. The API reference is added to the documentation, along with a new plugin development tutorial. The plugin v0 API remains supported for backward compatibility of existing plugins. Done: - Do not load commands from plugins which are not enabled. - Load enabled plugins once on start. - Implement contexts for actions and filters, which allow us to keep track of the source of every hook. - Migrate patches - Migrate commands - Migrate plugin detection - Migrate templates_root - Migrate config - Migrate template environment globals and filters - Migrate hooks to tasks - Generate hook documentation - Generate patch reference documentation - Add the concept of action priority Close #499.
2022-02-07 18:11:43 +01:00
while true; do $(MAKE) wait-for-change build || true; done
wait-for-change:
inotifywait -e modify $(shell find . -name "*.rst") ../*.rst ../tutor/hooks/*.py conf.py
Copy Permalink