I think I was confused because he mentioned wiki-style page for users as the title.
I’m pretty sure you can create a closed post and edit this anytime you want, you can put in under a category or maybe a tag if you like that. I assume you are the only one that has such a summary post?
You could pin this post so every user sees it, it will unpin for them personally if they read it. There are some creative ways to reach this. You could use this plugin to create an header shortcut to your post, for example.
I didn’t make that clear either: no I mean that every user should be able to have their own curated page for things they have learned or to link to posts they think are important as they go about their journey on the site.
Just an idea: Create category: Journey - every user creates his own topic there, they can edit this or reply to their own topic to update their journey. Assuming the audience of your board this could work out.
Up to you if you make them edit or reply to their own. If they reply to their own topic it get’s bumped up so you en all users can also easily keep up with journeys, the Discourse way.
a “page” where a user can add information relevant to their journey
a link to that page that is easily accessible on that user’s profile / card
they can edit it as they please
Discourse by default has a limit on the duration in which editing a post / topic is possible - but that’s easily configured with site settings.
Will every edit cause the journey topic to be bumped up the latest list? - You can force non-bump edits for said topics
Should a journey topic look different than normal topics? - you can easily customize the way topics, in a specific category, look. See Blog Post Styling
Off the top of my head, all of these things are possible in an efficient manner with a well-crafted theme-component
Your needs will require some custom work if the default options don’t quite meet your requirements; however, like I stated above, I don’t see any red-flags that would prevent this from being done in a theme-component. Have a look at the theme guide I linked above if you want to take it on yourself, or create a topic in the #marketplace category if you want to pay someone from the community to take on the work.
I use a few Discourse instances for various knowledge base storage. My thinking: threads and/or posts are cheap in Discourse, and the taxonomy tools should be used to assist discovery and reference and no more.
I live blog lots of things, and I start these “deep dives”. When I’m learning something new, I create a new thread, and just post everything there, like a notepad. I have a different thread for all my notable Dungeon Crawl morgue files and finds. On my private instance I have a thread for every domain or other IT asset I interact with, and leave a reply to timestamp my interaction. For the various games we play we have wiki pages and replies as lore is updated.
There are some examples; I don’t particularly treat them differently (aside from a “private instance”). Anyone can comment on anything. If it is interesting, it serves the document. If a discussion gains momentum it can split off or merge somewhere with a better fit (maybe someone’s else’s notes…).
Given my method, this ends up being my activity page, but in practice I just use search and interact with the ongoing, active discussions. Meaning I don’t spend time organizing notes, beyond broad categories and maybe some tags.
I don’t know much about the TMS context aside from gleaning it in this thread, but my personal method is to take notes and externalize them to assist in initial memory and scaffolding. After that I don’t look at my notes unless a need arises.
However, I’ve found that revisiting and exapnding on notes is valuable education, so I use a combination of editorial workflow and auto-bumps/reminders to keep it fresh and moving. Part of the process is discussing the interesting parts of my tribe, to benefit from the cognitive diversity.
I picked out a few parts of what you said that I had thoughts on, but in case it is all over the place, my advice: start using Discourse as a knowledge base and logging mechanism now, and then see which parts are missing from your idea. Discourse does a lot right now.
Can that limit on editing time be varied per category?
I might just change this for the whole site though as this is a learning space and I am okay with people going back to amend things as they learn more.
Also I am assuming that, as a site admin, I can always go back and edit. To some extent that’s essential as some topics link to files which will be updated over time. For example I have a topic that presents a tool that is a PDF, I will need to update this topic to point to new versions as they are published.
Thanks for the link to the marketplace, it’s useful to know there is one. I probably won’t do anything with theming straight away as I am still vetting that Discourse is the right tool for me (all signs point to yes so far).
In addition, if it is manageable (depends on the numbers of your users), you can create a topic for each of your students, change ownership afterwards and set the permissions to See/Reply so they can’t create topics themselves.
But I think it’s mostly an admin feature, because it would require searching and displaying the full FontAwesome icon set, storing the selected icon and adding it to the site’s subset of SVG icons. IMO, a default icon (site admins can override it using a theme component) would be sufficient for this specific feature.