this could go in many directions, but based on my experience, a thinner skill file with good instructions fares better than a huge file of very atomic configurations
congrats! love this, sometimes i get a huge huge history after 4-5 hours for working, and it is reseting. That's not a problem, what i actually want is a way to "bookmark" some of the informations that are relevant. And reaply them. Are you working on something like this?
Congrats for building this. I've seen many builders and Drag & Drop tools in the ecosystem in the past months but this one seems to be pretty simple and intuitive. I like that it doesn't have too many options to edit any action/button/CSS properties as that is usually over-complicating the builders.
I've read the comments on the PH launch and it seems you are on the right track. Also happy to see you added Argon and Admin Kit as the first starters.
Thank you for your kind words and feedback, it is really helpful!
We want to make Loopple as simple as possible for the developers. Also, we chose the best dashboards designs available in the market: Argon, Soft UI, and Admin Kit.
From a design perspective this looks really good, I like the components, the typography, the generated pages from Figma etc. Also the documentation seems to be clean and user-friendly. It's way better than most of the docs.
So I think this is a really good extension that can speed up the development process of people who like Tailwind. For those who don't like Tailwind, there are many other alternatives. There is no such thing that can fit for everybody.
Some questions
1. What did you use to create the docs?
2. What are your next steps with this project?
TailwindCSS is the biggest jump in productivity for me in years.
I think where it shine most is when you are making your own UI and need to deploy different components/customizations, ie: If you are doing a single page site is not that obvious "why is like this?", but generating UIs on the fly for a admin backend and suddenly THIS IS THE WAY!.
The "verbosed" nature of both cause some hate, but you will appreciate it the more big/complex the project is.
What you get with tailwind is exact understand of each component and how it will look based on their "types"/classes.
What you get with others like bootstrap is too abstract/implicit looks that you can't figure at a glance. So, tailwinCSS like static typed programming is optimized for "a glance"/local understanding.
What is also very counterintuitive is that my tailwind pages are LESS heavy than boostrap! (true for html and CSS)
1. We used HUGO as a static site generator and Webpack to put things together using markdown files. (it's open-source: https://github.com/themesberg/flowbite including the HUGO source files)
2. We're now working on the application UI code (pro version) but we will also add new components and external styled plugins (datepicker, charts) to the open-source library.
Any plans for Svelte? Also there is an overflow issue on mobile (popovers page). The landing page rocket icon on mobile needs additional margin on top.
That's right, it's part of the strategy but it's not generating revenue if you think of this from the marketing perspective. If we take into consideration the amount that we made based on the traffic that we got from these articles, it will be around 0.2% of the general revenue in 1 year (~2.000$ of $1M). Me, as the co-founder, I've spent many weeks planning, writing and gathering information to write these articles.
Even if it is 10$/hour, and a template is 40$, you will spend more than 4 hours just to choose colors/fonts and design ideas. Then you will spend days/weeks to plan, implement and test on tens of devices (phones, tablets, tvs, desktops etc).
The Bootstrap Templates are just 1 part of what we deliver. We also have React, Vue, Angular, Laravel, React Native, Node.js, Photoshop, Sketch, Figma, Adobe XD in our products lists. So if you take into consideration an agency who will deliver for his client a website + web app and they buy a "React + React Native + Sketch" combo from us and pay let's say 150$, that will be over 5.000$ for them if they have to build it from scratch. Also don't forget that we spend many months on building and testing our products on many devices (phones, tablets, tvs, desktops etc) Hope this makes sense.
