monknomo / cardwiki Goto Github PK

Target="_blank"

When a pipe is included in a wiki link, it assumes they it is pointing to the outside world and creates the wrong URL

We should support fancier databases

This probably bothers developers and testers more than anyone, but when a card was created in a browser, then deleted from the date base, opening that card will bounce automatically to the editor, but the editor is already filled with stuff. This is confusing

Maybe try to trash auto save stuff? Or maybe prompt the user that they have a saved draft, would they like to load it?

Write documentation on rest interface

Automatically deploy card wiki to test server when the prod branch is updated

Create prod branch

Write up git workflow procedure

Look into caching resources on the client side. What should be cached? What should invalidate the cache?

Farm out more resource hosting to CDNs

Tags can't be saved, deleted or clicked on in the ui

A stack is something like a tag, in that it is a collection of cards.

A stack is like a special card that opens up all the cards listed in it. Sort of a table of contents. Perhaps cards can be added to a stack by dragging and dropping

Rather than embedding a bunch of methods into the ui, isolate them into a more portable object, then test state transitions

Explain what cardwiki is.

Develop a project vision

I think we should get a cheap ssl et or possibly one of those freebies that are coming out

Create a descriptive web page

Writing [[text i want to view | wikilinks]] results in a link: <a class="externalLink" href="wikilinks">text i want to view</a>

not: <a class="wikilink" href="#card_wikilinks" onclick="appendCard(&quot;__startCard&quot;, &quot;wikilinks&quot;)">text i want to view</a>

Wikis should have some kind of access control.

Users should be able to control who sees their cards.

Maybe role based for wiki as a whole, but something like g+ from a user perspective?

If were going to have unit tests, we should run them automatically

Ampersand breaks, as you might imagine...

Non HTML safe characters seem to break wikilinks. Either escape them or indicate to the user that they aren't allowed

Unit test ui methods and objects insofar as possible - look into mockjax

Db unit tests.

Cardwiki unit tests.

Bottle unit tests.

Ui can't list all cards in a wiki

Keep bottle layer as thin as possible

Right now card wiki is a single wiki per instance.

It would be cool to host wikis for people, and that might be easier if people could share instances

This is more of an architecture question than a straight task

Card titles ought to have an URL that will open them up automatically

Can't create new card without linking from existing card

When clicking a wiki link of a card that is already open, cardwiki opens a copy of the card, rather than scrolling to the existing card

It would be cool to transfer cards between wiki's by dragging and dropping them or some similarly easy mechanism