• Reindexing
• Default HTML...atomification
• Strip out unnecessary logic of https://github.com/guardian/interactive-brexit-companion (it is currently rather slow and does not render in the app)
• Tag picker bug, pagination bug
• Search by title

Wish list:

• Delete if taken down
• Preview an atom without publishing it.
• Tag search

The current code to retrieve atom usage, relies on 3 assumptions:

• explainer id being in the body html
• The Content API search endpoint to use the body html - we are planning to to use body text
• The explainer id not used in another content

 def findExplainerUsages(explainerId: String): Future[Seq[String]] = {
    val searchQuery = SearchQuery().q(explainerId)
    client.getResponse(searchQuery).map(_.results.map(_.webUrl))
  }

This is unreliable and should move to the usage endpoint, which will work fine after explainer workaound is merged, and content reindexed.

As per https://github.com/guardian/recommendations/pull/19/files

• Split title, body blocks
• Add labels to input areas
• Show timestamp of when last saved
• Add word count (probably just client side for now) - probably 2 warnings - too long for non-collapsible then just too long generally
• Relevant links in toolbar
• Add tagmanager/composer-commissioning styles
• Make the default body blank (we should now be able to get away with inserting a character)

Tracing atoms once they have been embedded - a quick search/record. To be able to search for stories that have certain atoms embedded in them. At the moment, search function will work to find atoms, but not show you which story they are in.

Presence was working-ish when Editorial Tools took over the code from Membership but it could not display the correct initials. This, because the wrapper code did not have access to the panda auth user. So I updated that code to make it work and the result is available at the branch

https://github.com/guardian/explain-maker/tree/ph-20160716-presence

Unfortunately it works on local but not on code. So the work item here is to make it to work so that we have presence enabled to the users.

Important:

• Make it more obvious that the interactive link only works after people have clicked 'publish'
• Switch to UK datetimes on the list of explainers
• Add the ability to put bullets in explainers

Essential at some point:

• Support reindexing from content api (using media atom lib - talk to Paul)
• Put something in the default HTML block (Paul might be able to advise on this - should we include CSS?)
• Discuss with frontend getting the explainers rendered by them rather than by the interactive
• Get the explainer list to support paging
• Numbered list

Phil will do when he gets back:

• Wire up the thumbs up/down buttons into Ophan

Would be nice:

• Grey out published button when the revision number of the version in capi is the same as the revision number of our version
• Change word count to just say 'XXX words'.
• When over 100 words and not expandable suggest that people should make it expandable.
• Unbold by default
• Use icons instead of text for editor styling functionalities
• Display presence indicators on the dashboard

Needs to be updated

This will make everything happier, especially the load function which throws a None.get error at the moment when an invalid ID is given.

Just noticed this