pwdonald / new_site Goto Github PK

Write pinning tests for existing functionality to ensure future enhancements do not break existing functionality.

SEO friendly (not SPA) view for content pages managed through the Admin SPA. This view will utilize the content page endpoints.

Documentation includes:

• README outlining how to deploy the project.
• LESS documentation on how to customize the look/feel.
• Explanation of external dependencies
• Roadmap

A read only (outside of the Admin SPA) view is needed for the Author profile information.

The article editor needs markdown shortcut buttons to quickly add tags to the entry editor.

A page will differ from the requirements for an article. The page endpoints should implement each verb and persist through the appropriate database model.

The admin interface needs an article collection and list view to display saved/published articles.

Allow the user to upload and manage article attachments via Google Drive.

isAuthorized
isAlreadyLoggedIn

...etc

Redundant code is emerging in routes, this needs to be moved to reusable middleware.

Currently the route navigate function is invoked by listening for the click event on specific anchors, selected by the id attribute. This needs to be abstracted into a concise pattern on each controller (maybe view) after render.

Protect sensitive data such as hash secrets and certificates from the github repository using some sort of encryption.

Currently, the app is somewhat tightly coupled with NeDB for development. As development winds down an abstraction layer is needed so that multiple DB providers can be utilized through dependency injection.

A draft article can be incomplete and saved.

A published article must have the following fields:

• _id (_id)
• title (string)
• author (_id)
• publishDate (date)
• lastModifiedDate (date)
• lastModifiedBy (_id)
• tags (string[])
• content (string)
• revisionNumber (number)
• published (bool)
• interestedVotes (number)
• notInterestedVotes (number)

Integrate information provided by Google Analytics into the Admin CMS dashboard.

Add email notifications for the following events:

• Contact form is submitted.
• An Article is posted
• An article receives >70% interesting or uninteresting votes.

The article save validation is improperly accepting any value.

Add field on profile screen to upload user avatar instead of simply allow the user to reference an external link.

Currently express is handling the rendering of the majority of the layout, this needs to be passed off to Backbone in the admin section of the site.

When submitting forms the flash message that is returned is not always properly appended to the response object. Needs further investigation.

A list of submitting messages needs to be implemented.

Generate self signed certificate for admin portion of the site.

On each article there are two buttons to rank the article as interest or not interesting. These buttons need to record the vote in the database associated with the article id and the ip address that voted.

Only one vote per session.

The article api is incomplete and needs to be implemented for the admin interface.

Code reuse from the article editor, slight field modifications TBD.

An RSS feed implementation is needed for the article/blog portion of the CMS.

Automated Tests need to be written for basic website functionality. This does not have to be an exhaustive exercise on the admin interface.

Implement disqus on articles for comments.