-
Notifications
You must be signed in to change notification settings - Fork 112
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Co-authored-by: Christopher Knapp <83461866+chrisknapp98@users.noreply.github.com>
- Loading branch information
1 parent
251ae51
commit 8d6589f
Showing
9 changed files
with
96 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
+++ | ||
title = "Challenges" | ||
weight = 3 | ||
+++ | ||
|
||
{{<section title="Research for credible Sources">}} | ||
Finding reliable sources posed its own set of challenges. While we gathered valuable information from the lecture notes, we recognized the need to seek additional sources with verifiable credibility. Hence, a lot of research has been conducted. Moreover, we aspired to enhance the transparency of the educational content we provide by incorporating a 'Sources' button. This offers users the chance to immerse further into the subject matter, substantiating their understanding directly from the original resources. | ||
{{</section>}} | ||
|
||
{{<section title="Integrating Editor.js into our Knowledge Base">}} | ||
For our vision of creating a personal knowledge base by storing learning objects, we discovered the Editor.js library, which seemed perfect for our needs. However, one drawback was that it wasn't a React library like our project. Consequently, we encountered some challenges in using certain handy React features and had to implement workarounds. The editor itself is divided into various blocks, each representing different types like texts, headings, images, or our newly created learning object type. To incorporate our React learning objects into this editor, we had to create a new React root for each learning object. As a result, the blocks were not aware of our defined browser routes for handling navigation. Additionally, using contexts was not feasible within the blocks. To address these issues, we implemented an event bus for navigation, to which the page subscribes. When the navigation button is triggered, the editor block sends an event through the event bus. | ||
{{</section>}} | ||
|
||
{{<section title="Data Structure">}} | ||
Another aspect that we found challenging was defining the data structure for our learning objects. Our goal was to keep the learning objects as compact as possible to ensure maximum flexibility for users when storing them in the knowledge base. One crucial consideration was determining the level at which data retrieval should occur. We decided to retrieve the data once per learning object on each page. Essentially, the learning object acts as a container that holds all the small contents, such as text, images, and more, and it should be savable as well. To achieve this, we envisioned the contents as components that could be loaded independently of their parent (the learning object). However, we wanted to avoid redundant data retrieval for the same request. | ||
To address this issue, we considered implementing a cache or shared repository for the data. This would allow us to store and access the data efficiently, preventing multiple redundant requests. Unfortunately, due to time constraints, this feature concept did not make it into our final MVP. | ||
{{</section>}} | ||
|
||
{{<section title="Backend">}} | ||
Initially, we focused on the conception and implementation of different learning objects. Halfway through our project, we made the decision to set up a dedicated backend for data storage and retrieval. The primary motivation behind this strategic shift was to ensure the efficient management and smooth operation of our expanding content base. This enabled us to store, access, and manage data effectively, providing a more seamless learning experience for users. Therefore, resources had to be freed up to prepare the backend accordingly. In the end, however, this was a good decision, as it allowed us to implement a true full-stack application and thus address any other issues. | ||
{{</section>}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
+++ | ||
title = "Future" | ||
weight = 5 | ||
+++ | ||
|
||
During the creation of the MVP, certain features were excluded due to considerations of scope, time limitations, or their relative importance compared to the essential feature set. This section aims to highlight some of the features that may be added to intu in the future. | ||
|
||
{{<section title="Index Cards">}} | ||
One of the features that has already been fully designed for future integration is “Index Cards”. Users will not only be able to transfer learning content into the notes in the knowledge base but also create index cards from it. This will allow them to assemble a personalized collection of index cards to help them on their learning journey. The Index Card feature will include a customizable recap mode, including randomized or ordered self-testing. While keeping track of correct and incorrect answers, learners can prove their knowledge. | ||
{{</section>}} | ||
|
||
{{<image src="index-cards.png" caption="Index cards feature in the knowledge base" alt="Index cards feature in the knowledge base">}} | ||
|
||
{{<section title="Content Transfer">}} | ||
Users will have the ability to transfer content from learning objects in smaller pieces instead of having to move the whole page. This will give users the option to transfer specific items, such as a single image, portions of text, or certain steps of diagrams. This promotes a more individualized learning process, enabling learners to flexibly compile the content they need. | ||
{{</section>}} | ||
|
||
{{<section title="Enhancement of the Knowledge Base">}} | ||
In the future, the knowledge base will also allow users to create additional pages. This feature will allow them to expand their learning space to provide more room for personalized content. In addition, the knowledge base will allow users to arrange their pages in a hierarchical order to create their own knowledge base structure. | ||
To increase ease of use, a search function for content within their pages and a favorite feature will be added. These enhancements will allow users to quickly find specific content and mark their favorite or frequently used pages for easier access. | ||
{{</section>}} | ||
|
||
{{<section title="Practice and Test Mode">}} | ||
In the future, intu will encompass all phases of learning, ranging from understanding and practicing to revisiting and testing knowledge. | ||
In practice mode, users will have the opportunity to actively engage with exercises and then review the solutions along with supportive guidance. | ||
On the other hand, the test mode is designed to allow users to certify their knowledge. | ||
In this mode, results are only revealed after submission, and no hints or assistance are provided throughout the test. This mode aims to emulate a real-world exam setting, allowing users to accurately assess their understanding and readiness. | ||
{{</section>}} | ||
|
||
{{<section title="Hints">}} | ||
In the future, intu will provide even more support to learners during tasks. Hints can be accessed within an exercise and provide varying levels of assistance, from subtle nudges to more comprehensive explanations. The inclusion of hints encourages self-directed learning, empowering learners to solve problems on their own. It also reduces frustration, as hints help learners get on the right track and guide them towards their goals. | ||
{{</section>}} | ||
|
||
{{<section title="Expanded Learning Offers">}} | ||
Currently, intu represents only a single skill path along with a learning unit through which we aim to showcase our didactic concept. Our vision for the future of intu is to provide an extensive catalog of learning paths and topics from which learners can draw. This will allow for an even more personalized learning experience, tailored to the specific interests of each learner. | ||
{{</section>}} | ||
|
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.