|
1 | 1 | # Advanced users |
2 | 2 |
|
3 | | -Advanced users can develop their own evaluation functions. |
4 | 3 |
|
5 | | -## Evaluation functions |
| 4 | +## Microservices |
6 | 5 |
|
7 | | -Evaluation functions are responsible for taking in a user's response, comparing it with a correct answer, and providing feedback to the frontend application. Living as containserized Lambda functions on the cloud, they are infinitely customisable and language-agnostic. Content authors should be able to create their own at will. However, we are aware that in a lot of cases, this grading logic will be similar, which is why a few functions have already been created. |
| 6 | +The fundamental idea of Lambda Feedback is that it calls external microservices to provide interaction with users. There are two types of microservice: |
8 | 7 |
|
9 | | -[Evaluation functions - Quickstart Guide](evaluation_functions/quickstart.md){ .md-button .md-button--primary } |
| 8 | +Evaluate a student response and provide feedback: |
| 9 | +[Evaluation functions - Quickstart Guide](evaluation_functions/quickstart.md){ .md-button .md-button--primary style="width: 400px;"} |
10 | 10 |
|
11 | | -## Response areas |
| 11 | +Dialogic conversations with students:<br> |
| 12 | +[Chat functions - Quickstart guide ](chatbot_agents/quickstart.md){ .md-button .md-button--primary style="width: 400px;"} |
12 | 13 |
|
13 | | -Response areas are components in the frontend where student users can enter a response. The response is sent to the evaluation function, which returns feedback to the response area. In the alpha version response areas are built into the software (rather than being modular) so are not straightforward to redevelop. This website catalogues the basic behaviour of response areas, to inform developers of evaluation functions. |
| 14 | +All microservices are called over http. There is complete freedom in their implementation. Lambda Feedback also provides families of deployed microservices, using open source code available in our public GitHub repositories. |
14 | 15 |
|
15 | | -[Response areas - overview](response_areas/overview.md){ .md-button .md-button--primary} |
| 16 | +This section of documentation is to help developers of microservices. The documentation is written assuming you have basic developer skills. |
16 | 17 |
|
17 | | -## AI Chatbot Agents |
| 18 | +In addition to microservices, this 'Advanced' section caters to administrators of Lambda Feedback tenants; and to developers of interactive response areas, that can be published within our web-stack via discussion with the developers. |
18 | 19 |
|
19 | | -Chatbot agents are AI Assistants that students can chat with to ask for help or further explanations regarding the Question that they are working on. Each Agent has its own personality and approach to assisting the students. |
| 20 | +## Response areas |
20 | 21 |
|
21 | | -[Chatbot Agents - Quickstart guide](chatbot_agents/quickstart.md){ .md-button .md-button--primary} |
| 22 | +Response areas are components in the frontend where student users can enter a response. The response is sent to the evaluation function, which returns feedback to the response area. In the alpha version response areas are built into the software (rather than being modular) so are not straightforward to redevelop. This website catalogues the basic behaviour of response areas, to inform developers of evaluation functions. |
22 | 23 |
|
23 | | -## System Architecture |
| 24 | +[Response areas - overview](response_areas/overview.md){ .md-button .md-button--primary style="width: 400px;"} |
24 | 25 |
|
25 | | -- Technologies |
26 | | -- Deployment pipelines |
27 | | -- Hierarchy |
| 26 | +## Administrators |
28 | 27 |
|
29 | | -## Future Features |
| 28 | +Content to be added. |
0 commit comments