5 ms·

Great job! Other than the price, you did a wonderful job. The only hesitation is the price since I can get a theme from Themeforest for $18, this would be my

Great job! Other than the price, you did a wonderful job. The only hesitation is the price since I can get a theme from Themeforest for $18, this would be my second choice after that. I think if you lower the price a bit more, you will be able to net a lot more customers. Especially those buying bootstrap themes from Themeforest.

reustle 8y ago
+1 I've often wanted to change one or two default values in bootstrap, such as the primary color, but can't be bothered to pull it locally and rebuild it. I'm not aware of any sites that do this for me, would happily pay $5 or $10 once for a web tool where I could make these changes (just list all build variables) and save configs
- jmknoll 8y ago
  Is this kind of what you're looking for? https://bootstrap.build/app https://bootstrap.build/app
  - penetrarthur 8y ago
    God, this is like the best webpage in the internet. Thanks a lot!
- NicoJuicy 8y ago
  use SASS/Less and rebuild the css. I don't know what the problem is with that ? Info: https://getbootstrap.com/docs/4.0/getting-started/theming/ https://getbootstrap.com/docs/4.0/getting-started/theming/ File to adjust ( variables): https://github.com/twbs/bootstrap/blob/v4.2.1/scss/_variables.scss https://github.com/twbs/bootstrap/blob/v4.2.1/scss/_variable...
  - jasonkester 8y ago
    Because that is a huge pain in the ass to set up. I think front-end devs forget this part, because they always tend to have a giant complicated built tooling setup in place, so adding one more little thing seems easy. But the default is to have no tooling whatsoever, so the thing you're proposing that you "don't know what the problem is with" is a process that has a step one that lies several steps before even "install Node on my dev machine". I've gone through all that (specifically to change a color in bootstrap), and even now that I have it set up and runnable, I'd still use the grandparent's proposed $10/month web service if it existed. Edit to add: ...and now that a sibling comment has pointed out the existence of bootstrap.build, I'll be signing up for a paid account.
    - philbarr 8y ago
      > because they always tend to have a giant complicated built tooling setup in place I know people must have their own setups that they use in GitHub somewhere. I have some, but I don't do lots of web dev and they're a bit shit. Does anyone have any "default toolchains" in GitHub that they use to start new projects? Including SASS, webpack, common polyfills, etc.?
INTPenis 8y ago
It is a lifetime license though. I'm yet another budding web developer and I could imagine paying 60USD for a lifetime license if I'm sure the tool will stick around and continue to be developed.
- jnsaff2 8y ago
  Thats a very big if. And lifetime usually means lifetime of the offer not your lifetime or even the lifetime of the product. They are usually well intentioned but ultimately still a scam.
ccleve 8y ago
Disagree. $60 is nothing if this tool saves me hours of time. The developers need to make sure they make enough money to keep the project going. I like this project way better than Bootstrap Studio or any of the others I've tried. Some suggestions: 1. As others have mentioned, HTML editing is pretty important. I'd like to see my actual content when picking a layout. 2. Would also like to see a theme picker, so I can cycle through combinations of colors/fonts/etc. and see what looks best. I know I can do that under Change Styles, but I haven't the artistic skills to pick individual values and have them look good. 3. Add a search box component. 4. I don't see a way to add a sidebar menu on the left and have a custom content area on the right. It would be nice to have some way to nest components. This is important because I would probably use this mostly for building admin interfaces and dashboards. 5. Someday, in the future, and maybe this is well beyond scope, I'd like to have Vue components so I could just hook them all together and they just work. I expect that that would be a massive undertaking, though. #1 & #2 are pretty important. The rest -- I don't think they're critical to having a commercially successful project.
- kemyd 8y ago
  Great comment, thank you! We are working on deployment of the first thing (content editing). Theme picker (choosing one of possible design system, like Material, Fluent etc) is on our road map. 3 i 4 is about library, which is and will be developed. And the last one, Vue, for now is the further future :)

reustle 8y ago

+1 I've often wanted to change one or two default values in bootstrap, such as the primary color, but can't be bothered to pull it locally and rebuild it. I'm not aware of any sites that do this for me, would happily pay $5 or $10 once for a web tool where I could make these changes (just list all build variables) and save configs

jmknoll 8y ago
Is this kind of what you're looking for? https://bootstrap.build/app https://bootstrap.build/app
- penetrarthur 8y ago
  God, this is like the best webpage in the internet. Thanks a lot!
NicoJuicy 8y ago
use SASS/Less and rebuild the css. I don't know what the problem is with that ? Info: https://getbootstrap.com/docs/4.0/getting-started/theming/ https://getbootstrap.com/docs/4.0/getting-started/theming/ File to adjust ( variables): https://github.com/twbs/bootstrap/blob/v4.2.1/scss/_variables.scss https://github.com/twbs/bootstrap/blob/v4.2.1/scss/_variable...
- jasonkester 8y ago
  Because that is a huge pain in the ass to set up. I think front-end devs forget this part, because they always tend to have a giant complicated built tooling setup in place, so adding one more little thing seems easy. But the default is to have no tooling whatsoever, so the thing you're proposing that you "don't know what the problem is with" is a process that has a step one that lies several steps before even "install Node on my dev machine". I've gone through all that (specifically to change a color in bootstrap), and even now that I have it set up and runnable, I'd still use the grandparent's proposed $10/month web service if it existed. Edit to add: ...and now that a sibling comment has pointed out the existence of bootstrap.build, I'll be signing up for a paid account.
  - philbarr 8y ago
    > because they always tend to have a giant complicated built tooling setup in place I know people must have their own setups that they use in GitHub somewhere. I have some, but I don't do lots of web dev and they're a bit shit. Does anyone have any "default toolchains" in GitHub that they use to start new projects? Including SASS, webpack, common polyfills, etc.?

INTPenis 8y ago

It is a lifetime license though. I'm yet another budding web developer and I could imagine paying 60USD for a lifetime license if I'm sure the tool will stick around and continue to be developed.

jnsaff2 8y ago
Thats a very big if. And lifetime usually means lifetime of the offer not your lifetime or even the lifetime of the product. They are usually well intentioned but ultimately still a scam.

ccleve 8y ago

Disagree. $60 is nothing if this tool saves me hours of time. The developers need to make sure they make enough money to keep the project going. I like this project way better than Bootstrap Studio or any of the others I've tried. Some suggestions: 1. As others have mentioned, HTML editing is pretty important. I'd like to see my actual content when picking a layout. 2. Would also like to see a theme picker, so I can cycle through combinations of colors/fonts/etc. and see what looks best. I know I can do that under Change Styles, but I haven't the artistic skills to pick individual values and have them look good. 3. Add a search box component. 4. I don't see a way to add a sidebar menu on the left and have a custom content area on the right. It would be nice to have some way to nest components. This is important because I would probably use this mostly for building admin interfaces and dashboards. 5. Someday, in the future, and maybe this is well beyond scope, I'd like to have Vue components so I could just hook them all together and they just work. I expect that that would be a massive undertaking, though. #1 & #2 are pretty important. The rest -- I don't think they're critical to having a commercially successful project.

kemyd 8y ago
Great comment, thank you! We are working on deployment of the first thing (content editing). Theme picker (choosing one of possible design system, like Material, Fluent etc) is on our road map. 3 i 4 is about library, which is and will be developed. And the last one, Vue, for now is the further future :)