Olanetsoft / article-idea-generator

Generate your next article idea with ease. Powered by OpenAI.
https://www.articleideagenerator.com/
208 stars 62 forks source link

feat: ui-update #41

Closed Qudusayo closed 1 year ago

Qudusayo commented 1 year ago

UI Update

Made some improvements to the initial UI to make it fancier.

Screenshot 2023-02-23 at 12 07 27

Considered performance. The 92% there was reduced by a logging script most likely in my browser according to the message,

Screenshot 2023-02-23 at 13 17 52
vercel[bot] commented 1 year ago

Someone is attempting to deploy a commit to a Personal Account owned by @Olanetsoft on Vercel.

@Olanetsoft first needs to authorize it.

vercel[bot] commented 1 year ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated
article-idea-generator ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Feb 23, 2023 at 1:21PM (UTC)
Olanetsoft commented 1 year ago

Thank you so much @Qudusayo This is amazing.

Here is the preview https://article-idea-generator-git-fork-qudusayo-ui-update-olanetsoft.vercel.app/. It doesn't seem to work when you search; do you mind checking it out?

Olanetsoft commented 1 year ago

The UI looks great, but i think CSS is blocking the result preview or something. Check here https://article-idea-generator-q8qnijy15-olanetsoft.vercel.app/. @Qudusayo

Qudusayo commented 1 year ago

Issue #40 is addressed in the last commit.

I was thinking probably env wasn't set for that deployment. I tested locally and also deployed my forked version here and everything seemed to be good

Qudusayo commented 1 year ago

Looking into the network request, I noticed a 500 status code ( Internal server error ) when the request is submitted; therefore the issue is coming from the server which is most likely the env issue during the deployment.

Olanetsoft commented 1 year ago

Looking into the network request, I noticed a 500 status code ( Internal server error ) when the request is submitted; therefore, the issue is coming from the server which is most likely the env issue during the deployment.

Oh i see. Thank you.

Merged!