You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Frappe LMS relies on external links to documents hosted in Google Suite for lesson content visualization. However, Frappe already has its own tool called Drive, which allows users to generate and store documents within the ecosystem.
The proposal is to enable the visualization of documents created in Drive within the lesson section of Frappe LMS. This would allow users to manage and view documents without depending on external tools, improving the autonomy and cohesion of the Frappe ecosystem.
Benefits
• Reduced external dependency: Eliminates reliance on Google Suite for document management.
• Better integration and ecosystem cohesion: Leverages an existing Frappe tool, strengthening its ecosystem.
• Increased content creation efficiency: Publishing and managing documents directly in Drive streamlines the process, removing the need to embed external links.
• Improved user experience: Instructors and students can access learning materials more seamlessly and in an organized manner.
Requirements & Considerations
• Implement a document viewer in Frappe LMS to enable native visualization of files stored in Drive.
• Allow direct linking of Drive documents to lessons within LMS.
• Ensure that permissions and access restrictions are respected within the integration.
Use Cases
1. An instructor creates a document in Drive and links it directly to a lesson in Frappe LMS, without needing to copy and paste external links.
2. A student accesses a lesson and can view the document directly within the platform, without being redirected to an external tool.
Alternative Approaches Considered
• Continuing to rely on Google Drive, which limits the adoption of native Frappe tools.
• Developing a standalone file management system, which would duplicate efforts when Drive already exists within the ecosystem.
Expected Impact
This improvement will encourage greater adoption of Frappe’s native tools, positioning it as a more robust and self-sufficient ecosystem for educational content management.
The text was updated successfully, but these errors were encountered:
Description
Currently, Frappe LMS relies on external links to documents hosted in Google Suite for lesson content visualization. However, Frappe already has its own tool called Drive, which allows users to generate and store documents within the ecosystem.
The proposal is to enable the visualization of documents created in Drive within the lesson section of Frappe LMS. This would allow users to manage and view documents without depending on external tools, improving the autonomy and cohesion of the Frappe ecosystem.
Benefits
• Reduced external dependency: Eliminates reliance on Google Suite for document management.
• Better integration and ecosystem cohesion: Leverages an existing Frappe tool, strengthening its ecosystem.
• Increased content creation efficiency: Publishing and managing documents directly in Drive streamlines the process, removing the need to embed external links.
• Improved user experience: Instructors and students can access learning materials more seamlessly and in an organized manner.
Requirements & Considerations
• Implement a document viewer in Frappe LMS to enable native visualization of files stored in Drive.
• Allow direct linking of Drive documents to lessons within LMS.
• Ensure that permissions and access restrictions are respected within the integration.
Use Cases
Alternative Approaches Considered
• Continuing to rely on Google Drive, which limits the adoption of native Frappe tools.
• Developing a standalone file management system, which would duplicate efforts when Drive already exists within the ecosystem.
Expected Impact
This improvement will encourage greater adoption of Frappe’s native tools, positioning it as a more robust and self-sufficient ecosystem for educational content management.
The text was updated successfully, but these errors were encountered: