Rise Learning Journal / Notes
BETA distribution files Instructions for implementation further down the page under the heading BETA Version Release. I've been working on a Learning Journal for Rise. I have an BETA version I'd like to share on SCORM Cloud. The features we have included so far are: Comments persisted between sessions (SCORM 1.2 & SCORM 2004 3rd and 4th Ed) Save comments, associated with blocks individual blocks Comments are organised into topics/pages Edit existing Comments Delete Comments Print comments (to printer, or PDF is you have the required software installed) Export comments to Word (*.doc) Pagination (If comments exceed a defined number, they are split into pages) There are some things that needs to be finalised which will not take a great deal of work to complete. Mobile compatibility WCAG 2.2 AA What I'm looking for is a bit of community input, as I know people have wanted this feature for quite some time. This is my best guess of how somebody might use a learning journal, but would love to hear any other examples of how it could function, or additional useful features that could be included. If you would like to check it out on SCORM Cloud. You can visit this URL: Rise Learning Journal on SCORM Cloud Update (3rd December 2024) I have continued to work on this project and it is now SCORM 2004 compatible. Again, it is using the cmi.comments_from_learner. Unfortunately I found a significant issue with the Articulate implementation of the SCORM 1.2 and 2004 comments. I am in communication with support after logging the issue. I am hoping I can convince them that the implementation is incorrect, and the base script is updated. In the meantime, I am applying a patch to the Articulate "WriteComment" function to ensure comments are stored correctly for SCORM 1.2 and SCORM 2004. I have also made some cosmetic changes and updated the CSS for the HTML to ensure the application picks up the current Rise module theme (colours, fonts etc). I've fixed a few bugs I have found along the way with regards to deleting journal entries, and editing journal entries when not on the page they originated from. This all appears to be working really well now. My next priority will be working on the CSS to ensure it is mobile compatible. Once all of the HTML and CSS is finalised, I'll then work on the accessibility. I've been implementing aria attributes as I go along, but there is still some testing and development to be done on that side of things. I will be looking to release this as a BETA to a handful of people early in the new year. Update (9th December 2024) Accessibility Started work on accessibility. Currently implementing and then will be looking to test using JAWS 2024 and NVDA over the xmas holiday period. On track for BETA release Jan 2025. Update (09 January 2025) Accessibility & refactoring Still working on accessibility and refactoring. There is a little more work than first forecast. Yes, I know, you've never heard that from a developer before. I'm 50/50 as to whether I can get this out in January. It will depend on other work commitments, but I will keep this post updated. I have decided to simplify the colour scheme and move away from using the defined "branding" colours inherited from Rise, as I was finding this a bit unpredictable with colour contrast, and so in the interest of ensuring the content has the best colour contrast, I'll be hard coding the CSS rather than using the CSS variables defined in Rise. I'll re-visit this in future. Looking at the code, I need some serious refactoring as I think I found some redundancies and so need to delete any unused code that I added and then abandoned. Oh, and Happy New Year. Update (24 January 2025) Accessibility & refactoring Almost ready for BETA release. Should be ready for release next Tuesday. Accessibility just about completed. I think I could spend another few days improving things, but I think this will be a good first release. BETA Version Release Contact: notes@rebusmedia.com Minimum requirements: Rise course published SCORM 1.2 or 2004 (xAPI not currently supported) LMS Support for cmi.comments (TalentLMS cmi.comments implentation is not supported as the comments are not persisted between sessions). Release Notes: This is a BETA release, and is provided as is without any warranties and It should be used with caution and fully tested for your use case before considering for production. If you do find bugs, please report them to notes@rebusmedia.com (include browser, LMS, device) and I'll release a fix as quickly as possible. This is a side project and so does come second to our day job which can be busy, and so you may need a certain level of patience. Fixes can be expedited for your use case through engagement of our services for time critical projects. It has been tested on mobile, but not extensively (Google Pixel + iPhone). Win/Chrome has been the browser used for development, and testing has also been performed on Win/Firefox and Win/Edge. Features requests: If you require any features that deviate from the BETA version, they will be considered on their merit, but can only be guaranteed for your own implementation through engagement for our services. We have a long list of features that we would like to add if there is enough interest in the application and if it is viable. Accessibility: We made the decision to remove colors from the modal window theme to keep it simple and generic and accessible (high color contrast). The application has been tested with JAWS 2024 and is fully keyboard accessible and keeps assistive technology users informed of what is happening when interacting with the modal window. I'm always willing to make improvements to accessibility as a priority. Accessibility issues are treated as a bug and not a feature request. Implementation: Publish your Rise course to either SCORM 1.2 or 2004 Download the two files note.min.css and notes.min.js files to your computer. Extract your published Rise course to your computer and then copy the note.min.css and note.min.js files to the scormcontent\lib folder Open the scormcontent\index.html file in a simple text editor such as notepad and paste the following text just before the closing head element, which looks like this </head>. <link type="text/css" rel="stylesheet" href="lib/notes.min.css"> <script type="text/javascript" src="lib/notes.min.js" data-notes-per-page="5"></script> It will look something like this: // Excerpt of scormcontent/index.html starts window.__loadEntry = __loadEntry window.__loadRemoteEntry = __loadRemoteEntry window.__loadJsonp = __loadJsonp window.__resolveJsonp = __resolveJsonp window.__fetchCourse = __fetchCourse })() </script> <link type="text/css" rel="stylesheet" href="lib/notes.min.css"> <script type="text/javascript" src="lib/notes.min.js" data-notes-per-page="5"></script> </head> <body> <div id="app"></div> // Excerpt of scormcontent/index.html ends You can adjust the data-notes-per-page="5" attribute to determine how many notes should be listed in the viewer, before the pagination (note navigation) kicks in. Save the scormcontent/index.html file It's important to get this bit right, as the LMS expects the imsmanifest file in the root of the zip file you are about to create. Navigate to the folder containing imsmanifest.xml and then select all (CTL+A) and then select archive/zip/compress depending on the software you use the terminology can be different. It must be a zip file though and the imasmanifest.xml file must be in the root of the zip file. Update (28 January 2025) Print functionality improvement After some user feedback, I have adjust the print functionality so that there is less chance of the student losing the course window during printing. When print is completed or cancelled, the print page closes and the user is return to the course window. Update (30 January 2025) Fix: Added functionality to handle learn.riseusercontent.com cmi.comments implementation. The cmi.comments implementation is incorrect on the LMS and requires the application to retrieve all comments and save to the LMS rather than appending to existing comments. This could cause memory issues if users add multiple long comments over time. CSS: Improved CSS for mobile view (using full height of the screen to display the application. Update (31 January 2025) Bug: There is a known issue with TalentLMS. TalentLMS does not persist SCORM 1.2 cmi.comments between sessions. All comments are disregarded at the end of the session. For this reason, we cannot support TalentLMS unless TalentLMS changes the functionality of the SCORM 1.2 cmi.comments. CSS: Improved CSS for mobile view. Supporting devices with a minimum screen width of 355px wide.Listing your own posts /contributions
One big disadvantage of the changes in the new community in my opinion is the 'lesser' searchability of your own posts and contributions. In the past i used that to point potential clients to my Elearning Heroes profile and there they could check my work and contributions especially to Storyline related projects. Now that isnot possible anymore as it is not as easy browsable anymore. So i have to find another solution for that...but i really dislike it, as sharing projects this way was a great way. Helping the community, while building my portfolio.3D objects in Storyline
Hi Articulate Team, Are there any plans to bring support for 3D objects (such as .obj files) into Storyline? Essentially I'm referring to a 3D model viewer component function added to Storyline allowing for some basic manipulation of the 3D object itself such as rotate and move in X/Y/Z axis, exploded view, and part isolation. This would work wonders for so many learning projects and enhance the actual learning being achieved by the learner. Whilst Storyline has an insert web object feature, this requires additional overhead of the resource itself already being suitably hosted online or in a folder that can be hosted online (i.e. it contains HTML like files - index.html, etc. which is effectively asking for it to be web-ready). This isn't always suitable or practical for every company and their respective IP assets/resources. I have come across multiple threads asking for such a feature. Here's a few of them: 3D Models in Storyline | Articulate - Community Import 3d shapes into articulate storyline 360? | Articulate - Community How to put/import 3D moldels in Storyline | Articulate - Community In one of the threads I came across, there was a reply from Katie Riggo who stated "We're working on the ability to add 360° media assets to your courses". However, later on in the thread this turned out to be referring only to 360-degree images despite the thread being filled with people asking and requesting for 3D object support in terms of 3D models and being able to manipulate them like they can in PowerPoint. You can chalk this up as another +1 to the feature request for native 3D object support by way of being able to import and, to a basic level, manipulate them. Kind regards, SamDesigning eLearning Automation with Agentic AI - A Demo Using OpenAI Realtime + Storyline360
Hello Heroes! I’m thrilled to share my latest YouTube video that begins to scratch the surface of what agentic AI controls can deliver to the Articulate Storyline user experience! 🚀 In this video, I demonstrate how generative AI, powered by OpenAI’s Realtime API, can be used to actively shape, guide, and adapt eLearning experiences in real time. 🌟 What You’ll See 🌟 Agentic AI in Action: Discover how AI can guide learners, answer their questions, and foster curiosity during eLearning modules. Function Call Demonstration: Watch AI dynamically trigger actions in Storyline 360, like changing slides based on user input, to enhance interactivity. Real-Time Audio Streaming: Explore how audio data is processed and streamed almost instantaneously, creating seamless learner-AI interactions. 🌟 Why It Matters 🌟 Customised Learning Sessions: See how session-based instructions allow AI to personalise responses, aligning them with specific learning goals. Data-Driven Insights: Learn how AI-driven function calls can unlock rich learning analytics, making adaptive learning a reality. A Vision for the Future: Imagine self-healing courses that evolve based on learner behaviour and feedback. 📢 What’s Next? Integrating real-time audio transcription for dynamic closed captions. Expanding session data capabilities to unlock even greater personalisation and interactivity. Generative AI is reshaping how we design and deliver eLearning, and this is just the beginning. Join me on this journey by watching the video here: YouTube Link. Don’t forget to subscribe to the Discover eLearning channel for more insights and demos to elevate your training projects! Let me know your thoughts or questions below—I’d love to hear how you think agentic AI development will have an impact on learning experience design! 😊 --- My name's Chris Hodgson, an eLearning developer and software trainer based in the UK. I enjoy creating fun, unique, and engaging online experiences using Articulate software! Connect with me on LinkedIn - https://www.linkedin.com/in/chrishodgson44/
3D Model Embed: model-viewer - including AR!
Hi all, Even though Sketchfab is a great way to embed 3D models into your Storyline 360 courses, sometimes you might just need a simpler approach, without having to worry about subscriptions etc. model-viewer by Google is an excellent alternative: https://modelviewer.dev/ It's open source (https://github.com/google/model-viewer) It's fast and powerful Can be embedded without JavaScript triggers ('normal' web embed) Works in AR, including iOS! Transparent embed Please see the following example (open on a mobile device to test AR): https://360.articulate.com/review/content/6579ffc4-f076-4d8c-a820-5dd374e9c3e8/review Photo taken on iPhone 11 (AR): How to embed a model-viewer into Storyline: Insert > Video > Video from Website... Add your model-viewer embed code To allow embedding, include a 'dummy' <iframe> at the end (I tend to use width and height to set aspect ratio), i.e. <iframe src="https://127.0.0.1" width="16" height="9" frameborder="0"></iframe> I have included the project below. Get in touch if you need more help implementing it! PJ Palomaki Digital Innovation Lead AVT Connect, Brighton, UKGoing past gamification to creating an actual game (example linked)!
I've been testing the limits of what Storyline can do over the years in various jobs/contracts/personal projects, and I finally took the time out to create something that can actually be shared with others! In this example, I had to leverage tons of variables and states, audio/scene tricks and balancing, etc. to try and create one seamless experience. The project contains an experience/leveling system (which opens up more options later on), branching paths, drag and drops, audio and video tricks, and all kinds of other things. If anyone is curious as to how I got anything to work, I'm free to answer here, which is why I started this discussion. Link here: https://360.articulate.com/review/content/2bfcbdd5-79fc-4c47-834f-4a6b23701aa2/reviewA glossary to use in Rise
This glossary example uses the Quote Carousel block - one letter is represented by one quote. I have inserted a table with a header in each of the quotes which can have extra rows added to them when required. You can navigate by 'swiping' left or right, clicking the left or right buttons or clicking on the hotspot dot below the table. I also added a alphabet index (roughly spaced) as an image. Note this really lends itself more for desktop/laptop viewing. The block can be saved as a 'Template Block' so can be reused in other Rise projects. Easy to edit and remove letters which are not required. :) I have added a second simple glossary example which uses a labelled graphic block, again this can be easily saved as a block template for reuse in other sections of the same project or other new projects. view projectSocial learning within Articulate RISE or Storyline?
Hello community, I am looking for any ideas on how to simulate social learning in RISE? Or storyline? Learner discussions, submissions, and commenting on submissions. Is there any way to create this with Articulate or an add-on? Thanks in advance! KathleenThe Hidden Power of Self-Motivation - Articulate Storyline
Hey everyone! I made a cool e-learning project called "The Hidden Power of Self-Motivation" I used ChatGPT to create the content, and made it interactive with Articulate Storyline. To make it even more fun, I added a little touch of JavaScript. An amazing experience underwater. Check it out now and discover the amazing power of self-motivation! Project link Project Process In general, the most important feature of this project is that the buttons move randomly and work continuously. Another important feature is that fish and bubbles constantly appear and move in a cycle. As you know, there is a timeline in the storyline and it is difficult to show continuous movement unless you use loops or gifs. In this project, I pushed the limits and made the storyline application look like a web page. It may seem easy, but this project took me weeks to make. The most challenging part for me was doing this on a single screen with a scrolling panel. Using a scrolling panel is more difficult than a normal screen, especially integrating move animation into an element. There is a huge difference between the first stages of this design and this one. Let's move on to the project steps; First you need to add a scrolling panel. To lengthen the scrolling panel, you must add a long rectangle and extend it downwards. At the top I added the title of the project, the iceberg and the surface line of the sea. Then you add the items you want to appear on the screen one by one. Items in the Project; Jellyfish gif jumping fish gif little fish gif Buttons ovals for bubble Sand, stone, crab for the ground... I added a bubble image inside the ovals to make them look like real water droplets. As you can see there is a lot of movement on the fish and the bubbles. You need to carry these animations from the bottom of the water to the finish line. It should disappear when the movement is finished. I created a loop to ensure that these items run continuously when the project is open. This move works for certain periods of time, and I added a trigger to each of them so that it works again when the animation is completed. The same goes for my fish gifs. When the animation of the fish in the upper part ends, the fish in the lower part continue to move and move forward. Our work is still not done :) Now we need to define the codes for our buttons so that they move randomly. The purpose of this is to make them look like bubbles in the water. var tl = gsap.timeline () .to(theObject,{ xPercent: "random(-7, 7, 3)", //chooses a random number between -20 and 20 yPercent: "random(-7, 7, 2)", duration:1, ease:"none", repeat:-1, repeatRefresh:true // gets a new random x and y value on each repeat }) There are two javascript codes, the reason for this is to prevent the buttons from doing the same random movement. When we are done with the Home Page, we move on to layers. There is a layer for each button. We fill the layers and add a trigger to open them when clicked. Yes, the steps of the project were like this. Now it's time to export. I hope I helped you. Enjoy it :)
