Allow users to specify a CSS stylesheet to customize the theme of their Glass instance. We can provide a template that can be downloaded. Tweak the values and reupload the theme to your blog.

Currently the views can't receive variables from the DB on all views. Need to figure out the best approach. Read here:

https://stackoverflow.com/questions/28608527/how-to-pass-data-to-all-views-in-laravel-5

Add an author bio feature which displays on each post and can be updated on the users profile.

Adding an API would allow for cool things like the ability to post whenever a new YouTube video gets released and the post would include the video description and link to the video etc. This is best handled via an API.

The API needs to be incredibly simple and straightforward to use:

1. Create a post
2. Retrieve a post
3. Retrieve a list of posts

When clicking the Back to Posts button on a single post from say page 2 or 3, it'll take you back to page 1, the index, instead of respecting the pagination and page it was on. We should add a new controller function that just "goes back" a view and use that for this button and others that we need to respect pagination with.

Each post can support keywords, we need to dynamically call them on that post loading. Use the meta tag and a variable to inject them.

https://laravel.com/docs/5.3/elixir

Make sure to start using this moving forward.

The user may add a bad slug currently. Add in a way for the title to be slugified after leaving the title input field. The user can still change this later but will allow for an easier post creation workflow.

Currently if an image for a post can't be found (gets moved, corrupted, name change) then it will display nothing. Instead, if the image cannot be found, we should be displaying the default image.

I'm getting a ton of spam user signups for illegitimate users who then don't actually leave comments etc. This would be fixed by adding reCAPTCHA to user signups.

• Add recaptcha
• Ensure that it's disabled in dev mode

Allow admins to:

• change the blog name from the dashboard
• delete users
• delete comments
• allow or disallow comments spanning the entire blog
• create blog categories

Currently this project uses the old justintime50/slugify package which is published weird and is no longer supported via Composer. Instead we should be adding it as a Node module and importing it that way.

When viewing the site in horizontal mode on a screen such as an iPad 11”, the image will produce inconsistent rounded corners, I’ve yet to determine what makes some rounded and others not. This doesn’t appear to be a problem when viewing the site in vertical orientation. All photos should have rounded corners. Here’s an example of the inconsistency:

Categories should be blog specific and not user specific. This could lead to duplicates.

Currently you cannot save a draft to come back to later. Add in the ability to have posts published, draft, or inactive.

There is no default category.

Add an RSS feed so blog posts can be fed to something like the new GitHug User README's:

https://github.com/spatie/laravel-feed

For SEO purposes, the title tag on each page should be the post title, not the blog title.

The margins/padding of pictures on mobile is too much, this need to be reduced:

The code blocks on the dark mode theme render bad, we need to fix the color scheme of the text along with fixing the corners:

There are a bunch of NPM packages that need a bump due to security vulnerabilities.

npm audit fix should do the trick.

A long-time want that I had was for the ability of the user to easily theme Laraview. If I don't go that route, make a dark mode that users can switch to (themed).

Currently you have to update posts one at a time. It'd be great to add bulk actions such as image removal or category updates etc.

There are two composer files, one in the project root directory and one in Laravel. I'm assuming we only need one of them?

We should really be storing image paths/ids to the database and looking them up that way. The current image implementation is flakey at best and doesn't work in dev (only prod). Let's fix all that, clean it up, and add missing tests.

There are a bunch of TODO items in this project as it was scaffolded quickly. Take a look, log them here, and work on them one by one.

There are some missing features for categories:

• Ability to update the name of a category
• Ability to filter posts by category
• Click the link of a category on a post and be taken to all posts of that category

Currently using spaces in the url for a users full name. Instead, we should replace spaces with hyphens.

eg: http://laraview.localhost/Justin%20Hammond/testing

There's no easy way to go back to the posts page from an article. Add a back button.

Currently, the only admin user is whatever user has user->id = 1. All other users will become normal users, able to comment but not create posts etc. Need to create a way to register more admins and differentiate them with normal users.

Add in the ability to share posts to your favorite social platforms via buttons that dynamically grab the link of the post.

Currently the user cannot upload their own photo. Allow them to do so.

As the blog grows with the number of posts, it will be important to paginate the posts into pages of maybe 10 records at a time.

Images could use some love:

• Fix local image saving
• Images should be loaded to S3 or some other compatible service instead of served locally (local could be a backup method)
• Image viewer should be organized somehow instead of a page with all the pics dumped on it
• When creating/editing a post, you should be able to select the image you want to use and/or update an image from that page without losing all the edits you've made to your post

There's no way to get data out of the project, use the PHP Excel Laravel project to do so.

If an image is uploaded with an absurdly long filename, we should make the text smaller or truncate the name:

If not, it'll overtake content that comes after it and spill over its container.

Allow users to add a profile picture and display it on comments, post authorship, etc.

We want to lowercase user's names in URLs for uniformity, slugs should already get lowercased.

We can accomplish this by following something like this: https://gist.github.com/coreywelch/2de40f93a252da3b2eddc013a98b3d37