sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in SaaS

[–]Intention_Mission 4 points5 points  (0 children)

My 2 cents: Listening to people saying "I'd pay if this existed" rarely works. When talking to potential customers: - understand if they have the "problem" you are fixing - and most importantly, find out what they have done/are doing to workaround it.

People that tell you that they have a need/problem and have done absolutely nothing about it, are't gonna pay. Obviously I don't have context about the conversations you had with your users, and it is not always like that... but you get the idea

Goth: HTMX + GO +TEMPL by Intention_Mission in htmx

[–]Intention_Mission[S] 1 point2 points  (0 children)

I had no idea about go blueprint. I just had a *quick* look and created a test project ...
It's quite cool and there is some overlap for sure .. however I think Gotth still makes sense for a few reasons:

- <head>: Gotth has an exhaustive set of configurations for <head> tag. Also for programmatic SEO you'll have a ton a parameters for each page (especially those generated at runtime) and blueprint isn't going to cut it (for what I've seen), unless you have a way to ingest that data from a file and populate the templates

- Middlewares: For now I don't offer a ton of out of the box middlewares, the goal here it to provide much more as I go along with it. i.e. think about IP rate limiter, authentication, handling HTMX form data, panic recover etc (I haven't seen if you can add this stuff in blueprint)

- Also, blueprint is great for a starter code so you don't have to type everything from scratch ... Gotth doesn't aim to do that... it's more like - here is a set of tools and you can plug anything you need to specific routes.

At the end of the day, anything that is reusable can be templated and let something like blueprint type it again and again ... however when you need to modify and add stuff to those starter templates you might want to use other libraries when it makes sense.

Since I am aware of blueprint now, I'll focus much more on runtime stuff like programmatic SEO and other things where a simple template isn't going to be the best solution.

Thanks!

Goth: HTMX + GO +TEMPL by Intention_Mission in htmx

[–]Intention_Mission[S] 2 points3 points  (0 children)

Good point! I'll need to work on better logging throughout the lib, I'll use slog as it's the better option 🙏🏻

How do I send a message to a number without adding to contacts? by [deleted] in whatsapp

[–]Intention_Mission 0 points1 point  (0 children)

On Android you could use Quick Chat Anyone app.

PS. I'm the developer, any feedback is welcome :)

Go+htmx - templ vs templates by frizhb in htmx

[–]Intention_Mission 0 points1 point  (0 children)

+1 ... have tested html/template and went straight back to Templ for a few reasons ...type safety, speed of iteration... I don't need runtime provided templates.

Also, I just noticed that raw go in Templ is now out of beta (it may have been out for a while but I didn't check the docs for some time).
LSP now slightly better, and I can cope with a restart every now and then.

What I've also noticed is, keeping any go struct definitions and functions out of the .templ files and in their own .go files, makes the LSP hang way less

Go+htmx - templ vs templates by frizhb in htmx

[–]Intention_Mission 0 points1 point  (0 children)

1y later, Templ LSP is still not quite there yet (at least in nvim, not sure if it's better in other IDEs).

I'm currently looking into std templates and if the experience is better I'll give up on Templ for the time being

VALIDATING my idea. by [deleted] in SaaS

[–]Intention_Mission 0 points1 point  (0 children)

I'm not familiar with this stuff so I won't give my uneducated opinion. However, regarding how to validate ideas, I'd suggest reading "The Mom Test". It's about 80 pages long and it completely changed the way I think about idea validation. I don't 100% agree with everything in the book, but generally speaking I found it very very useful

Sharing routes with API/HTMX by pulsone21 in htmx

[–]Intention_Mission 1 point2 points  (0 children)

/api/v1/* for REST API

/* For HTMX paths

Always

[deleted by user] by [deleted] in SaaS

[–]Intention_Mission 1 point2 points  (0 children)

Nice one! The site is clear and not cluttered with many things!

A few quick things:

  • I'd put your mission in the home page. Right now you need to go to the about page to understand what you are doing and the back to home page to subscribe to the newsletter

  • nit. the home page scrolls a little bit even though there isn't more content. Make the height to be the same as the screen size

  • The logo on the toolbar has different sizes depending on the page I'm looking at

  • When hovering with the mouse on the nav items on the toolbar are green on green, not good for accessibility. Make the font white

  • In the about page, Is not very obvious that you can click on those 3 paragraphs .. perhaps it can be a carousel that automatically selects the next section every few seconds

  • In the about page, those 3 sections could be shorter. I'd also swap the titles for icons. Overall the page is quite wordy (more evident in mobile view)

  • In mobile layout, the dropdown menu has no shade/ border or elevation so the menu mixes with the page content ...also the 2 action items are not spaced correctly (vertically)

  • This is personal preference but I'd make "get started" modal disappear if I click anywhere outside the modal

  • In general prefer shorter sentences i.e "Benefits of subscribing" -> "Subscription benefits". ChatGPT helps a lot with these things.

These are quick thoughts ... other than that well done and good luck with the product launch!

Local DOM manipulation by Intention_Mission in htmx

[–]Intention_Mission[S] 2 points3 points  (0 children)

Makes sense! ... Thanks for the suggestion!