Welcome to the New E-Learning Heroes!
Hello! I’m Ginger Swart, a Community Manager here at Articulate, and I’m thrilled to welcome you to our new E-Learning Heroes Community! Please check out this article to watch a walkthrough video of our site and our FAQ article for more information. The work to move to our new site started over a year ago. To prepare for this, we have migrated over 1.5 million community members, 2100+ articles, 970+ examples and downloads, and more discussion posts than I can count! We had a beta period with our Super Heroes, and we appreciate all of the feedback we received from them. But with that much content, we anticipate there will be some hiccups, so please use this discussion to let us know about any issues you find and any feedback you want to share with us. I hope you’ll love the new community as much as I do!A New Chapter for Our E-Learning Heroes Community
It's hard to believe that two weeks have already passed since we launched our new E-Learning Heroes community platform. We're thrilled to be on this journey with you, building upon the incredible foundation of knowledge and collaboration we've cultivated together for well over a decade now. What's New and Exciting Many of you have shared positive feedback about the new forums, noting that they're easier to navigate. We're especially pleased to hear that the new dedicated groups, such as those for JavaScript and Accessibility, are welcome additions. These improvements are just the beginning – we have more exciting features in the pipeline. Acknowledging the Challenges Of course, with any significant transition, there are bound to be some hurdles along the way. We've encountered a few hiccups, and we sincerely appreciate your patience and understanding as we work through them. Here are a couple of key points to be aware of: Content Cleanup: In preparation for the move, we archived discussions that hadn't seen activity in over three years, as well as outdated articles and user guides. This means that some older content may no longer be accessible. It will take some time for search engines to update their results accordingly. Technical Issues: We're aware of a redirect bug that sometimes causes pages to load incorrectly. If you encounter this, please try refreshing the page or clearing your cache. We're actively working with our platform vendor to resolve this and some other issues. Feature Differences: We’ve heard your feedback about some features that you’re missing from our old community, such as showcasing projects on your profile, how the emails display, seeing postings on our jobs hub, and others. Some of those features are in the works, and we are sharing additional feature requests with our vendor. In the meantime, If you're looking for E-Learning job postings, we recommend ATD's job bank and and The Learning Guild Job Board. Moving Forward Together Your experience and satisfaction are our top priorities. We're committed to creating an environment where you can easily find the help and resources you need to build exceptional courses. As we navigate this transition together, please don't hesitate to reach out with any questions, concerns, or feedback. You can reply to this thread or feel free to email us at community@articulate.com. Thank you for being an integral part of our E-Learning Heroes community. Your contributions, insights, and patience during this time are invaluable. We're excited about the future and the enhanced experience that we're building together.Free Articulate Storyline 360 E-Learning Templates
Good morning my fellow developers. We have a bunch of old courses that need to be refreshed at our company. To save time, I wonder if you know any good places to find FREE modern storyline 360 templates because starting them all from scratch would take a lot more time than we have. If you know of any places, I should look please let me know.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.New Matching lay-out
Last week we received the updated lay-out of the matching knowledge check. The moment I discovered it was a bit unlucky (during a presentation, got me a bit confused) but today I had some time to look into it. The changelog as following on the articulate website: Enhanced: Matching knowledge check blocks have been upgraded with intuitive navigation, full keyboard support, and comprehensive screen reader integration. Now, I think it's great that Articulate is improving it's software's accessibility, however, I don't see anything intuitive about the new design. A lot of new things have been added which for me only make the assignment more confusing. On the left side the hamburger icon and number suggest some sort of clickability, which is not there. The drop downs on the right give the assignment a new layer of intractability which only wouldn't want for the student. Overall the lay-out is a lot less clean and drains focus away from the content towards the design. Maybe a simple solution would be to add a slider which let's us choose between this lay-out and the previous one (or this one without the rings and bells). That's just my opinion, I was wondering what other think of the new lay-out!Morph transition on Feature Roadmap
As the Morph transition made it to the Feature Roadmap for Articulate 360 ( finally! ), i do think it is good to post what we want/expect it to do, and what is a miss in our ( the users ) eyes. That way Articulate can keep that in mind while developing. For that we first need to divide Storyline elements in groups/types ... so we can discuss how we expect that type to morph. TYPES 1) Images 2) Storyline shapes 3) Video 4) Text ( SVG ) 5) Imported SVG 6) UI elements As on the roadmap it is defined as 'transition'. So i expect it to be exactly that. A Morph transition between 2 slides. So next would be defining the 'attributes' of the defined types we expect to morph. ATTRIBUTES A) Position x/y B) Scale C) Rotation D) Fill color and line ( actually all Format Shape settings ) E) Transparancy If for all the types the given attributes are morphable, i am happy. I expect 3) Video to be non-morphable. 2) Shapes and 4) Text i however expect and hope to have all attributes morphable. Do comment on this with your hopes and dreams for the Morph transition and lets hope Articulate listens.Using Rive in Storyline - States
On LinkedIN i allready posted how to get this done. Starting a series how to use Rive directly in Storyline here too. All the interactive elements in Rive can be triggered by Javascript. To get it working you need a proper Rive with named states. These you can trigger with Javascript. Like this.. https://360.articulate.com/review/content/1ea72b55-9a69-4b0e-a8d2-a566e0c59ed1/review Basically you add the Rive animation as a WebObject. The index.html used for the WebObject has a Canvas, the Rive Web runtime and specific code. <canvas id="canvas" width="404px" height="332px"></canvas> <script src="https://unpkg.com/@rive-app/canvas@2.7.0"></script> You have to replace the 'src' url for the Rive file with your own. Or add it somehow as file and target that. src:"https://public.rive.app/hosted/204711/199760/iEdeOxzF3UinRiSlCE08yA.riv", Using 'postmessage' to communicate with an iframe you can then trigger any state in the rive. window.message = ""; window.addEventListener("message", function(event) { let data = event.data; changeState(event.data); }); I am adding the .story and index file for anyone interested. Rive does have a great new functionality, 'Layouts' that change animations based on screensize. For Storyline that is quite useless as Storyline isnot responsive but scales the view. For Rise360 however this can be great. Next step for me is discovering exactly how 'Layouts' work in Rive and getting that to work in Rise360. #Rive #Interactivity
