This is just a writing-down of plans, to capture things I want to do. Feel free to join the discussion (and the work!) – the point of me writing down things here is that they should be open for anyone.
Things to evaluate on skillcompass.org
* Is the "relations" tab on topics useful at all? (probably not)
* The terminology. (For example: "resource collections" -> "resource lists", "topic" -> "skill", "resource" -> "??", and so on.)
* Usability.
* Should search functionality be turned on?
Important and easy
* Update the README.
* Update the project page description.
* A pane with "this resource appears in these collections".
Important and difficult
* Get feedback from users (including myself).
* Rewrite all the plans.
* More tests. Consider SimpleTest for the custom code.
* Investigate how much functionality can be localized out of the box, and how much work it is to fix the rest.
* Make the topic trees accessible for screen readers, or have an alternative that is readable. (Easy when/if DraggableViews starts supporting tree structures + Entity Reference fields.)
* A content type for collecting topics into a course (or some other appropriate name).
* An "Assessment" feature, where teachers-users can note assessments on student-users' skills on topics.
* Have the relations between learning resources and topics votable, so resources (1) can move around with a growing topic tree and (2) have a way to find the most relevant/representative resource for a topic.
* Allow the topic tree to be loaded with a selected item expanded and active. This would allow including the topic tree(s) on the topic pages, which would make a lot of sense.
Easy
* Revisited: #1513198: Allow Views export of all style settings and #1513462: Implement new API from Graph API to allow exporting engine settings
* RSS feeds for resources on a given topic.
* RSS feeds for new topics. (And sub topics to a given topic?)
* Screencasts describing how Skill Compass is built.
* Prevent duplicating title of topics?
Difficult
* Add panes for creating reverse relationships. (Not only "this topic requires" but also "another topic requires this".)
* Allow the topic trees to show whether you have mastered a topic or not. (Requires patching the JIT.)
* Consider (again) using the Relation module for the topic relations.
* Get nice progress bars for earned points.
* Get the lists of learning resources to display stars (or progress bars) instead of flat percentages.
* Get a nicer implementation of the microdata used for Drupal project references, see #1513648: Get better display of Drupal project microdata.
* #1512370: New div added on every vote click
* Allow a nice 'upgrade path' if you enable topic relations *after* you have created topic references manually.
* Allow an easy way to create sub topics, super topics, required topics, lead-to topics and also learning resoruces – with references/relations created automatically.
Really difficult
* Make Flag exportable in a sane way, or replace it with something like Relation + a cool widget.
* Generalize the 'isapartof' and 'requires' relationships. In a perfect world, this would be a widget for the Entity Reference field.
* Performance tests.
* Change topics into taxonomy terms. (Which requires that you can flag any entity, or that you have a good replacement for Flag.)
* Make stuff look good.
Think more about
* Add a new learning resource type 'exercise' or 'problem', to which 'solution' content can be added? Could be a good thing to encourage people to post alternative solutions to practice problems. (Could even be a way to organize Q/A, I guess, but practicing problems probably are rather different from real-world problems people want help with.)
* Allow one-off super votes on topic relations, giving +100 instead of +1?
* Add functionality for merging topics?
* Add functionality for splitting topics?
* Add more sub functionality, using topics as something similar to OG groups – such as having Q/A forums on topics?
* Allowing a fallback "is a part of" topic, adding new topics to the "uncategorized" super topic (or something).
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | Skill_Compass-resource.png | 240.5 KB | itangalo |
| #5 | Skill Compass - topic.png | 140.75 KB | itangalo |
| #5 | Skill Compass - external learning resource.png | 240.5 KB | itangalo |
Comments
Comment #0.0
itangalo commentedAdded a bullet about comments.
Comment #0.1
itangalo commentedAdded some more bullets to the to-do.
Comment #0.2
itangalo commentedAdded two bullets about the topic trees.
Comment #0.3
itangalo commentedAdded a number of new todo things.
Comment #0.4
itangalo commentedAdded two bullets about progress meters.
Comment #0.5
itangalo commentedAdded a line about exercise/solution resource types.
Comment #1
itangalo commentedThe references to drupal.org projects are now implemented as a separate feature. It is not working 100%, but it is pretty close – and it is good enough for launch. (The feature is only useful if you're doing a learning site related to Drupal, so it's not a show stopper.)
Comment #1.0
itangalo commentedRemoved Microdata from the list of things to do before release. Critical parts are done!
Comment #1.1
itangalo commentedAdded size descriptions to tasks to do before launch.
Comment #1.2
itangalo commentedAdded more things to do, crossed one item off.
Comment #2
itangalo commentedSearch page for topics now committed and pushed.
Comment #2.0
itangalo commentedCompleted the search page for topics.
Comment #2.1
itangalo commentedAdded two bugs in Vote Up/Down
Comment #2.2
itangalo commentedAdded an issue about hiding vote widgets when user is not allowed to vote.
Comment #3
itangalo commentedAfter some experimenting I decided to just add the comments to the bottom of the topic and external learning resource pages. (In the example layout.)
The alternative was to have them on its own tab, "discuss", but it turns out it is jolly hard to change the comment permalinks. At least for me.
Comment #3.0
itangalo commentedCrossed off the comment task.
Comment #3.1
itangalo commentedAdded an issue with the Drupal web taxonomy module.
Comment #4
itangalo commentedPatches for Graph API and The JIT submitted.
Comment #4.0
itangalo commentedDegraded the web taxonomy thingie to a smallie. It now has a working patch.
Comment #4.1
itangalo commentedCompleted patching task for Graph API and The JIT.
Comment #5
itangalo commentedComment #5.0
itangalo commentedPatches for Vote Up/Down submitted.
Comment #5.1
itangalo commentedAdded two tasks, concerning automatically creating references/relations.
Comment #6
anavarreI like everything I see here. Makes me think about Khan Academy. Keep up the good work!
Comment #6.0
anavarreAdded two tasks related to theming/usability.
Comment #6.1
itangalo commentedCrossed off the task "making headers for topic creation panes look better".
Comment #6.2
itangalo commentedAdded two new tasks.
Comment #7
itangalo commentedAfter quite some experimentation with Fields Permissions, I abandon it as a solution for hiding fields that should not be visible (such as voting widget when you can't vote and also the topic reference fields when Topic Relations is enabled).
The module is *much* more nice than the D6 version, but it turns out that it is really difficult to have a field exported by one feature change permission settings with another feature – and not having the first feature overriden.
It's a sad day when I revert to custom code instead of a generic module, but getting the job done is first priority.
Comment #8
itangalo commentedDescription fields for topics and external learning resources are now changed to "plain" instead of formatted text. This should give a nicer UI for inexperienced users. (The "text format" settings can be kind of confusing.)
It might be worth considering to change this later on – maybe it should be in some kind of example feature that can be disabled or overridden?
Comment #8.0
itangalo commentedUpdated list with (a) results from experimentation with Field Permissions and (b) hiding of vote widget.
Comment #8.1
itangalo commentedCrossed off the 'plain text' task.
Comment #8.2
itangalo commentedRemoved the blocker issue for Rules stuff. With latest Entity API, export works fine. Hurra!
Comment #9
itangalo commentedProgressive permissions now implemented in a first version in sc_example_points – see #1513354: [meta] Progressive permissions sketches for Skill Compass.
There is also a feature sc_example_permissions that the progressive permission feature depends on.
Comment #9.0
itangalo commentedCrossing off the tasks relating to progressive permissions.
Comment #9.1
itangalo commentedLinked caching to its own issue. Added flag permission export issue. New formats on headers, and also some sort of welcome text.
Comment #10
itangalo commentedBiggest single commit so far – example layout is now updated to contain caching and also Rules-based cache clearing. Yeah.
Comment #10.0
itangalo commentedAdded a task on changing topics to taxonomy term.
Comment #10.1
itangalo commentedUpdated list, now that caching is in place.
Comment #10.2
itangalo commentedAdded a line about preventing duplicate topic titles.
Comment #10.3
itangalo commentedAdded a line on having a default super topic.
Comment #11
itangalo commentedREADME.txt in place. Good.
Comment #11.0
itangalo commentedUn-completed the task for exporting Graph API views. Patch has been broken. :-(
Comment #11.1
itangalo commentedCrossed off the README task.
Comment #12
itangalo commentedComment #12.0
itangalo commentedAdded a line about having topic trees (or their equivalent) accessible for screen readers.
Comment #12.1
itangalo commentedMajor updates to the roadmap.
Comment #12.2
itangalo commentedAdded two new tasks.
Comment #12.3
itangalo commentedAdded two new tasks.
Comment #12.4
itangalo commentedCrossed out the "update project description" task.