leeaustinadams / mango Goto Github PK

Need to use clojure.java.io/resource to resolve the file.

• Users
  • Duplicate usernames
• Articles
  • Duplicate titles (slugs)
  • Empty titles
• Pages
  • Duplicate titles (slugs)
  • Empty titles
• Etc

Need to run highlightjs on preview

Maybe it would be cool to utilize the twemoji project.

Users should be able to change

• First name
• Last name
• Twitter handle
• Email address

Users should not be able to change

• Username
• Account creation date
• Roles (unless they are Admin)

article-id query parameter is always specified, need to add page-id query param and call dp/update-page-media instead of dp/update-blog-article-media

I think there are some places claiming copyright, some places eclipse, etc etc. Need to unify to an understandable license.

Trying to decide if media should be associated with an article or vice versa

Reduce the duplication necessary in {prod/dev/test}/config.edn

Right now mango is strictly tied to Amazon S3 via amazonica

https://getpocket.com/publisher/button

Add a feature to allow adding/removing tags to multiple articles.

Right now mango is strictly tied to mongodb via monger

They're structurally and behaviorally extremely similar, they really only differ by being in the feed or not and what route they are reached via.

There are several possible languages and content in an article title that util/slugify will not handle well.

And which duplicate can be accessed by slug depends on the order of database results.

Probably shouldn't output those fields anywhere

https://www.chromium.org/developers/design-documents/form-styles-that-chromium-understands

Throw an error or non-fatal warning on missing or invalid configuration items

Instead of using the database directly, use a passed in data-provider

Images in articles and pages cannot be viewed any larger than the appear on the page unless the user right clicks and views it in its own window.

Currently mango hydrates page content (renders markdown to html) on read. But we probably should just hydrate on write, and write both the markdown and the html to the database. Then on read, just read the html.

Currently they refer to the site's configured twitter handle, which may be different.

Set up pagination for the articles list

Need to add an option to edit the page in the toolbar

It can be determined from the requests

Would be better to have the json api be configurable and plug in more modularly.

Offset index and count are ok, but not as flexible as it could be. Consider cursoring.

I'd like to write all the script for the front end as clojurescript ideally, or at least not have my crazy JS "build" step.

• Site title
• Site description
• Site copyright
• Admin email
• Site twitter handle

Maybe others

It's just fixed (via CSS) to float right and a width that is some percentage of the parent's width.

If it slugifies the same, then when retrieving an article by slug, the result is undefined.

e.g.

(defn blog-articles-by-query
  "Query blog articles"
  [query {:keys [page per-page] :or {page 1 per-page default-per-page}}]
  (mq/with-collection @DB config/db-article-collection
    (mq/find query)
    (mq/sort {:created -1})
    (mq/paginate :page (Integer. page) :per-page (Integer. per-page))))

There is not much in the way of admin capabilities, including inability to add/remove users

Need to add sign up pages and functionality

Should probably downcase tags. It would be cool to add typeahead/completion as well.