mkarnicki

> Then I'd have to change my HTML everywhere

Nope. Once you see same (sub)set of classes repeated, you would instead define .alert and .alert-danger using Tailwind's @apply directive, and you now have a single place to change how your `alert alert-danger` looks :)

While not CSS courses directly, these resources should help you address what you're looking for.

Tailwind related playlists on Adam Wathan's YouTube: https://www.youtube.com/channel/UCy1H38XrN7hi7wHSClfXPqQ/pla...

And this publication (by same authors as Tailwind UI, that is Adam and Steve) https://refactoringui.com/book/

Enjoy!

Are you saying k8s is to blame for large file upload/download failures? Maybe your infra needs a tweak?

I recommend you check out https://jrnl.sh/

Can you elaborate? I can't agree with you. Tailwind is meant to provide a consistent design system, of which CSS size should never get out of hand (which is the case then using regular CSS). Whenever I use Tailwind, I end up adding maybe 20-30 lines of CSS and I never have to open a CSS (or other sass/less/whatever) ever again. Have you tried Tailwind or you're just assuming what you're saying?

Because you'll have 29 different margins, 67 different left paddings, etc all over the place. Tailwind allows you to create a consistent design system. CSS was supposed to be "write one class, use it everywhere instead of inlining". Usually it ends up with nobody reusing that class and everyone creating their on in the same codebase. There's an article I don't have a link handy, which explained how ridiculously many classes were used by GitHub/Lab, Airbnb, etc. Now even GitHub have their own utility based CSS system and others are following along, including Bootstrap with their CSS utility classes.

Have a look at Feedly. I, too, loved Reader. Feedly filled the void for me :).

I believe this is why recently Twitter reverted the change and now allows you to browse in chronological order.

Glad you like it :)! Thanks for sharing the link. One of the reasons I created Stackdraft was the thought "why cloud architecture diagrams can't look good as well?". It's like we're constrained to crude tools, but the technology has gone so far already :)

I went through a bunch of diagraming options. draw.io is 2D diagraming only. There's also Lucidchart and few others. One other option seems to provide more than flat diagramming, but it's fixed to isometric projection (so, it is flat in the end).

I was also inspired by these diagrams from Amazon [1]. In Stackdraft, you press V key and toggle between 2D and 3D. You have full control over the point of view :). You can also create an animated presentation, like this one [2] - that one was just to show off a few AWS 3D models, so it's quite simplistic, but you get the idea :).

[1] https://aws.amazon.com/architecture/#aws-ref-arch

[2] https://twitter.com/stackdraft_io/status/1036557211554787331

* Stackdraft

* https://www.stackdraft.io/

* Create and present 2D/3D cloud architecture diagrams that look great.

* Stage: Launched over a month ago, currently at $120 MRR. Get your hands on the early adopter plan ;)!

* Plans: Offer team plans, more cloud service models.

All right guys, looks like I can get some sleep now ;). If there's more questions, I'll definitely reply to them tomorrow, thanks!

Thank you! I really hope to improve the graphics further with postprocessing, more custom 3D models, etc.

Yes, 'multi-provider' was one of the reasons I built it :). You can naturally mix the icon sets as you wish, if you have cross cloud infrastructure, which is becoming more popular these days for HA purposes.

Thanks for your comment!

Thank you for your kind words. Yes - Stackdraft was partially inspired by Cloudcrafts sole focus on AWS. I don't blame Tomas though, only on surface supporting multiple providers seems like an easy task - I'm sure it's not. At this early stage of Stackdraft I focused on diagramming and presenting and naturally plan to add more advanced features.

To answer your second statement - I think it's a matter of doing one thing only and one thing well. While I do plan to support sub-resource level items like containers, I doubt the tool will reach as far as UML/software modeling, at least not in the foreseeable future. Do note I received lots of feedback from a LucidCharts users, who draws architecture diagrams, and in general there's a few good parts of LucidCharts I'd like to take example from.

Regardless, I will always welcome any ideas for Stackdraft, so thank you very much for your feedback :)! I appreciate you took time to leave this comment.

Hi all,

This is my very first post on HackerNews, although I’ve been a silent follower of this amazing, diverse community for years now.

My name is Michał Karnicki and I wanted to share what I've spent the last 6 months on, days and nights, and most of my savings. I'm equally excited and nervous to share it with you all :)! Stackdraft is a fully bootstrapped project.

The longer version of this story is actually available on the Pricing page, so I'll keep it short and sweet. Stackdraft allows you to create AND present 3D cloud architecture diagrams. You're not fixed to a single cloud provider or the isometric projection. It currently support AWS, GCP and DigitalOcean icon sets, but I have plans for more fancy 3D models as well, besides other things I mention on the website. Inspired by both the good sides and limitations of other diagramming solutions, I decided to try create my own. And that's how Stackdraft was born.

Stackdraft is in Beta, that's why there's an Early Adopters plan on the pricing page. I'm hoping to get some initial users seriously interested in the project as a tool for their work, close registration (so I'm not overwhelmed - haha I wish, eh ;)?), and use the feedback from them to polish the tool. If you're interested in cloud architectures, please help me shape the future of Stackdraft and consider subscribing - there's 14 day trial, 30 day money back guarantee, and it currently costs a BigMac set per month :).

There is a famous quote by Reid Hoffman, the founder of LinkedIn: If you are not embarrassed by the first version of your product, you've launched too late.

So here I am! More than happy to answer your questions :). Thank you for checking out Stackdraft!

I would upvote this more than once if I could. This is the most important argument for "reason of engagement" as it should be.

Superb comment, thank you. This is the worst pain point:

> I know of no acceptable automated method for doing this, so we just have to review the information manually at frequent intervals.

Hey Patrick, thanks for this comment.

"Plus, we're able to show our customers they have a problem that we can then sell an add-on for." - I really like that part.

If I understand correctly, finishing the last citation with:

"[in order to continue proving a service] to you."

would at least resolve the problem of retaining user data indefinitely, but I also totally agree with the free interpretation of "Conducting research and analysis".

Also, because Profitwell is available to customers in Europe, it will soon have to align with GDPR requirements (which also includes the right to being forgotten), even if it's not a European company or otherwise face fine risks.

You're losing customers by not having your website available in English as well.

We're definitely waiting for you in Poland.

I couldn't help but think: "For Open Source Software Analysis"

Nicely put github comment, well done. Thank you. I feel sick in my mouth seeing PL in his username, which clearly indicates my home country. I am beyond baffled.

While true, it really makes me wish the large companies would add 1 to all those tiers, so we wouldn't have to play along with pricing psychology - as someone else noted, you look at 499 and see 500, but there may be a difference in 500 tier authorization. So while I hate seeing 9's in prices, I understand that's a sensible way to go. At least in the higher range of prices.

Thank you for this comment. I think it's spot on with keeping some aces in your pocket for appropriate time. It's not fun to keep onto unreleased features, but the product should continue to grow with time. If one wants to increase prices, ideally this goes along with added features.

It's quite amazing (and I've read that before) that increasing prices usually increases perceived value of the product. If you charge too low, users may consider it as "it can't be good if it's that cheap".

KeeWeb.info - there you go. Open Source, $0.