​Desc: Sidebar search bar is overlapping toolbar in Listing

Acceptance Criteria: The sidebar should be as wide as the search bar.

Desc: Docker Composition - v0.6 : + wordpress + mysql

Acceptance Criteria: docker compose should be able to run components in dev, and prod mode.
dev

proxy

• nginx or trafaek

leaves.lite
-- /read -> leaves:latest
-- /topic -> leaves:topic-latest
-- /app/wb -> wallabag web
-- /app/tt -> ttrss web
-- /app/wp -> wordpress web

• appleseed/leaves:latest
• appleseed/leaves:topic-latest

leaves.wb

• wallabag/wallabag
• mariadb
• redis:alpine

leaves.tt

• clue/ttrss
• nornagon/postgres

leaves.wp

• wordpess
• mariadb

​Desc: lots of typos / duplicate tags

Acceptance Criteria:

​Desc: The item is not selected when the user clicks on a grid view item.

Acceptance Criteria: The User should not have to click twice to read an item.

​Desc: The wrapper should be able to provide the same interface for retrieving the leaves items.

Acceptance Criteria:

1. Must conform to this schema example

[ { "area":"content-left", "name": "DOCKER: Self Paced Training", "path":"https://training.docker.com/self-paced-training", "ContentImages_small":"", "ContentImages_large":"", "title": "DOCKER: Self Paced Training", "content": "Docker's own self paced training class.", "category": "Training", "tags": ["docker","video"], "type": "Video", "source": "Docker" }, { "area":"content-left", "name": "Hackr.io : Learn Docker", "path":"https://hackr.io/tutorials/learn-docker", "ContentImages_small":"", "ContentImages_large":"", "title": "Hackr.io : Learn Docker", "content": "Listing of docker tutorials submitted and voted on by the programming community", "category": "Training", "tags": ["docker","tutorials"], "type": "Page", "source": "Docker" }
http://anant.co/data/topic.docker.js
2. Should be the same GET method in each implementation

https://wallabag.org/en/news/new-release-wallabag-2-3-is-there-really

Desc: New wallabag 2.3
AC: Upgrade DB + Run new Wallabag on Azure + Test on Docker

​Desc: There should be a way to toggle to the reader view.

Acceptance Criteria: If there is at least one selected article, the "Inbox" virtual tag should appear. This way when the user browses off the reader by selecting a tag, they can go back to see what they have selected. It should also show how many items are in there.

​Desc: Right now the tag listing doesn't show number of items.

Acceptance Criteria: If a new item is added to a tag, it should show that it increased the number.
Use the "Badges" CSS https://getbootstrap.com/docs/3.3/components/#badges

​Desc: Docker Composition - v0.4 : + wallabag + redis + mysql

Acceptance Criteria: docker compose should be able to run components in dev, and prod mode.
dev

proxy

• nginx or trafaek

leaves.lite
-- /read -> leaves:latest
-- /topic -> leaves:topic-latest
-- /app/wb -> wallabag web

• appleseed/leaves:latest
• appleseed/leaves:topic-latest

leaves

• wallabag/wallabag
• mariadb
• redis:alpine

​Desc: Results from the search bar show up like as if they were being pulled from wallabag API, but ranked by elastic ranking..

Acceptance Criteria: content is retrieved and shown identically to how its done now but the data is coming from an elastic search query. The search query is part of the URL so that the url can be passed around.

​Desc: reader view should show tags (linked to tags) + domain_name

Acceptance Criteria: This data is already in the entries API.

​Desc: if the user the reader enabled by having clicked on an item, the reader should persist with different tag clicks

Acceptance Criteria: On home page load, show the default view. When a user clicks an item, show the reader. If the user clicks on another tag, the reader should refresh to show the first item in the tag.

Desc: the tabs need to be robust.. no need to reinvent the wheel.. maybe use something like..

Acceptance Criteria: good robust tabs.

https://angular-ui.github.io/bootstrap/
http://nervgh.github.io/pages/angular-tabs/

​Desc:

Acceptance Criteria: show first 100 characters or so of the contents if no image similar to in wallabag.

​Desc: Need to build docker image and test on TravisCI

Acceptance Criteria: On Commit, TravisCI should create a docker image using docker build, run it and show that there were no errors.

​Desc: Needs to be flushed out, but I was thinking that under the title, it has the user, a button for the original link ( these are in place now ), a link to the reader view, and a link to the iframe view.

Acceptance Criteria: User should be able to see the contents of the original link in an iframe that fits int the place of the reader content when clicked. If they click on reader, it goes back to default view. This could be a tabbed interface toggling between reader / original view.

​Desc: These files look identical but are called from different elements. It's confusing because of the multiple files. This doesn't follow the DRY (dont repeat yourself) principle.

Acceptance Criteria: One leaves-reader that shows up when clicked from either list, card, or from a menu item if hidden ( another issue)

​Desc: toolbar should have a "read" link next to "link" in card view

Acceptance Criteria: should work the same as when you click on the link title.

​Desc: middle pane - gridview is wierd after switching back and forth from list

Acceptance Criteria: Grid view should look like it normally does.. one on top of each other

Notice that the title / content is trailing off.

​Desc: reader panel is too wide / doesn't fit all text on screen

Acceptance Criteria: User should be able to read all of the title and the content should be wrapping in the view.

Desc:
When a tag has a space in it, it should have the space replaced with "-" but when its a period, it should not be replaced with "-"

Ac: if a tag is like "app.interfaces" , the tag link should be http://localhost:9000/#!/?tag=app.interfaces. Right now it shows "app-interfaces" and it doesnt show the links

​Desc: Dockerized app can be brought up on ACS with one bash command.

Acceptance Criteria: given AZ credentials and a resource group, one command will bring up the system on azure.

​Desc: Front end should be able to access the wallabag api using a node proxy in server.js not directly from wallabag.

Acceptance Criteria: Wallabag api available through a proxy and limited to get commands.

Desc: rethink the reader view with better ways to switch between leaves

Desc: Docker Composition - v0.7 + search.engine + search.index + search.web.user

Acceptance Criteria: docker compose should be able to run components in dev, and prod mode.
dev

proxy

• nginx or trafaek

leaves.lite
-- /read -> leaves:latest
-- /topic -> leaves:topic-latest
-- /app/wb -> wallabag web
-- /app/tt -> ttrss web
-- /app/wp -> wordpress web
-- /app/searh -> appleseed/search:web-user

• appleseed/leaves:latest
• appleseed/leaves:topic-latest

leaves.wb

• wallabag/wallabag
• mariadb
• redis:alpine

leaves.tt

• clue/ttrss
• nornagon/postgres

leaves.wp

• wordpess
• mariadb

appleseed.search

• appleseed/search:engine
• appleseed/search:web-user
• solr ?
• elastic ?

​Desc: Use webpack to download bower libs. all references are downloaded to the repo, these should be pulled from NPM / processed via webpack

Acceptance Criteria:
Remove bower as a dependency. Use webpack and build into npm install / init scripts.

1. Installable and runnable via npm install and npm start
2. or npm install , npm build , http-server dist (currently serves the index)

​Desc: reader tab pane - tabs should get abbreviated

Acceptance Criteria: Tabs should dynamically resize -- similar to this and should be close able.

​Desc: Anything that is related to our own instance is moved into environment.yml and process.env.VARIABLE

Acceptance Criteria: move token, scope_base url, etc.. into environment.yml , create environment.dev.yml for testing.

​Desc: There's an issue with ios safari and chrome. Submitted by @ramseur

Acceptance Criteria: If leaves are selected, it should show the selections one after another (with x to remove ) or in tabs.

Desc: reader pane doesn't show when clicking links from list view

Steps to reproduce:

• open http://qrisp.eastus.cloudapp.azure.com:90/
• click on list view
• click on first item

Acceptance Criteria: When list item is clicked in this view, reader pane is shown.

​Desc: When a search is executed, it does client side rendering.. if it is gone to using a url e.g. /search/blah it is rendered on the server side.

Acceptance Criteria: Search page loads fast without flicker, rendered server side if access directly.

Desc: When submitting URL through wallabag API giving error "500 internal errors". I think there are some writing issues on server or API is not granted for adding URLs.

​Desc: archived links don't show actions

Acceptance Criteria: it should show buttons regardless of whether it's archived

​Desc: tag / category navigation should be like medium in that when you click it shows a grid, and there is a option to pin the list to the left side as it is now. if hamburger button is clicked it is hidden.

Acceptance Criteria: 1. Need to have a category / tag view similar to Medium when clicking on "Categories"

2. Need to have "hamburger menu" Similar to

Toggle the left menu.

​Desc: Let's keep the flipping of list / card in the same panel as the list / card for UI encapsulation.

Acceptance Criteria: User sees list / card icons above the list / card list in the middle panel.

​Desc: All views ( tag, default ) should show latest post first.

Acceptance Criteria: Add new leaf ( in wallabag or using add leaf) and it should show up on the default view as the first item.

​Desc: When a tag is clicked, it does client side rendering.. if it is gone to using a url e.g. /tagname/ it is rendered on the server side.

Acceptance Criteria: Tag filtered page loads fast without flicker, rendered server side if access directly.

​Desc: It should fit inside the width specified.

Acceptance Criteria: Should be able to add as many tabs and have it fit in the same width.

​Desc: Home page is initially rendered by node.js / .net

Acceptance Criteria: Home page loads fast without flicker, rendered serverside.

​Desc: Need to have a "landing" home page. ​This would look something like anant.co or anant.co/topic.html until someone clicks on a link, which then will go into the reader view. This will probably be a different docker container or maybe the same which does a simple read only and uses the existing anant.co template but populates from API not from the json.

Acceptance Criteria: User can go to a / and it shows a page like anant.co

or

the Docker prototype

​Desc: Add leaf button should add item to Leaves via Wallabag API

Acceptance Criteria: Add Leaf button should add a new link to the wallabag DB and then it should show up on the interface.

​Desc: Right now it shows the oldest content first, need to show the latest content first.

Acceptance Criteria: When a link is added to wallabag using chrome or the wallabag admin, the most recent post shoudl show first on the home page, or if in a tag view, the latest one there.

Desc: Docker Composition - v0.5 : + ttrss + postgres

Acceptance Criteria: docker compose should be able to run components in dev, and prod mode.
dev

proxy

• nginx or trafaek

leaves.lite
-- /read -> leaves:latest
-- /topic -> leaves:topic-latest
-- /app/wb -> wallabag web
-- /app/tt -> ttrss web

• appleseed/leaves:latest
• appleseed/leaves:topic-latest

leaves.wb

• wallabag/wallabag
• mariadb
• redis:alpine

leaves.tt

• clue/ttrss
• nornagon/postgres

​Desc: Users should be able to share the URL after picking items and have the other user see the same listing. Right now , for some reason this feature stopped working.

Acceptance Criteria: URL shouldnt be like this:

http://qrisp.eastus.cloudapp.azure.com:90/#!/leaf/2703%252C2719%252C4605%252C2702%252C4911?tag=cassandra

but rather

http://qrisp.eastus.cloudapp.azure.com:90/#!/leaf/2703,2719,4605,2702,4911?tag=cassandra

1. This is how it looks on Safari (incorrect):

2. This is how it looks on Chrome (correct):

​Desc: if the user hasn't clicked on an item, don't show the reader

Acceptance Criteria: On home page load, show the default view.

​Desc: The issue is more that the tool bar should be separate from the listing or the card view.

Acceptance Criteria: Toolbar should be above both card / list view with the normal gray background as it is in the card list view.

Card list View

List list View

​Desc: Either through asynchronous or synchronous code, all data in wallabag is searchable in elastic.

Acceptance Criteria: All data is wallabag db is searchable in one collection in elastic.

When other users start adding links periodically and we want to check on who's adding quality links with proper tagging and who's not it would be very useful to have a visualization dashboard where we can easily display that info.

Kibana is most likely the most simple and MVP solution for now

https://www.elastic.co/products/kibana
https://stackoverflow.com/questions/29671524/kibana-how-to-display-log-as-table

Improve in browser search.
Some options are to use to look for multiple terms https://stackoverflow.com/questions/15519713/highlighting-a-filtered-result-in-angularjs

or implement lunr https://lunrjs.com/guides/getting_started.html

in combination with Angular UI