Collected Feedback comments

[ramiboutas]

• It'd be nice to see a few examples of resulting CVs quickly. Or perhaps some pre-populated templates ready to be edited. The one image on the front page is not too appealing to be honest, and the templates that are visible on the builder page are empty unless I invest a lot of time into populating the fields. Also the wizard feels a bit janky (at least on Firefox). The forms are jumping and changing size on mouse hover, which is a bit disorienting. Hope that helps.
• Umm, on the mobile menu (navbar) the logout button is visible even for first time visitors. Maybe you’d want to fix it :))
• Also, the login button is visible when you are logged in already
• When registering i found an internal server error, i used a somewhat easy password. Also, it would be good to build some kind of anti spam for account creation. -> The problem is when a visitor enters a non-existing email address, the application will raise an Exception. I know, I know... It shouldn't be that way. I have to find out a way to improve that: maybe a HueyEmailBackend.
• Looks good, on desktop the profile dropdown in the navbar seems to be transparent compared to the image of the cv below it.

More:

• https://news.ycombinator.com/item?id=38832074
• https://www.reddit.com/r/django/comments/18vgq2w/i_created_a_saas_with_htmx_with_django_backend/

[ramiboutas]

• Entrando desde Facebook con el móvil parece que falta un padding en la parte de preguntas frecuentes

[ramiboutas]

Hola Rami, he visitado el enlace desde el móvil y inicialmente toma mucho tiempo y dice “Bad Gateway”. Después de varios intentos y copiando el enlace en safari, así se ve:

[ramiboutas]

I’d avoid using floats for currency. Better to use decimals. Your KeyError may catch more than intended. Look before you leap may be more appropriate here.

[ramiboutas]

[ramiboutas]

I'd use different phrasing instead of "buy plan". Just use the phrase "buy" instead.

[ramiboutas]

I have a comment not related to your question. I see you're storing current language settings into cookie. While this might be easier for you to handle multilanguage, search engine crawlers will not be able to index pages other than english. They don't use cookies. You will need language info in urls for crawlers. Django have great out-of-box support for multilanguage urls.

https://www.facebook.com/groups/2310400015870119/posts/3594344414142333/?comment_id=3594682174108557&notif_id=1704550900376970&notif_t=group_comment

[ramiboutas]

Hi, when the amount is converted to euro’s I’m missing the decimal comma in the localization which in my case is NL/dutch. Perhaps you can also add a functionality based on the actual location where the user resides to show that currency. For me that is the USD.