josemiguel-alvarez / simple-remix-blog Goto Github PK

Using a database we could very easily count the visits of each posts. For each request of a post page, we would increase the count by one in the database.

For this, we have to first add the possibility of connecting the app with a database. We can use Supabase which has a free tier.

There are two main problems now:

1. How images are rendered
2. Some errors are logged to the console

The report can be read here: https://web.dev/measure/?url=https%3A%2F%2Fsimple-remix-blog.vercel.app%2F

It would be great to have a comments section for each post. The comments could be hosted in GitHub by using any of the following 2 libraries:

• https://github.com/giscus/giscus
• https://github.com/utterance/utterances

The app already has a sitemap but it's missing a RSS feed which is important for some people.

• The feed should be available in the routes /feed.xml.

Instead of having to manually add each post to: https://github.com/josemiguel-alvarez/simple-remix-blog/blob/main/app/utils/posts.server.ts

It would nice to have a script that does it automatically.

It would be great to have a search component that can be displayed in the /tags page or the /blog list.

Add contributors section to README.

When searching using the SearchForm we could use Optimistic UI in the following way:

1. Filter the results that are already available in the client.
2. Display the filtered results. (Hint: use useTransition hook: https://remix.run/docs/en/v1/api/remix#usetransition)
3. Display the results returned by the server when available.

Optimistic UI guide: https://remix.run/docs/en/v1/guides/optimistic-ui

It would be nice if instead of displaying the web URL we could display our own logo.

Instead of this:

Be able to also display a logo:

A new design that is more classic / simpler could be added for the PostsLists component. Instead of having Cards we could renders something more simpler like:

Example taken from: https://www.joelonsoftware.com/

This would also make it easier to improve the design on dark mode.

I would make it possible to switch between both designs by adding a new property in the siteMetadata.js file.

Project: https://github.com/GoogleChrome/lighthouse-ci

Lighthouse CI is a suite of tools that make continuously running, saving, retrieving, and asserting against Lighthouse results as easy as possible.

The idea is to execute it on every commit to prevent regressions in accessibility, SEO, offline support, and performance best practices.

When the users filters posts using the SearchForm it would be nice to give the user some feedback. One possible idea is to reduce the opacity while loading:

1. Initial render

2. User enters text in the input

3. Opacity is reduced when the request to the server starts

4. Opacity is set back to its original value when the response is received

The top of the blog looks like a bit tight. I think that by moving the social media icons to the bottom it will look cleaner.

It would be great to have some tests. For example, I've thought of adding snapshot tests for the components.

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Missing name property in package.json.

The package.json's name property is required in order to publish a package to the npm registry.

Please make sure to add a valid name for your package in your package.json.

Good luck with your project ✨

Your semantic-release bot 📦🚀