That said, I think the quality of your shuffle components are better than most of the components on Bootstrap Studio, so I bought it.
All I'd really like to see is the ability to edit content. If I'm doing a prototype for a client, I can't have everything saying Pied Piper or New Internet.
You will send out an email/newsletter to let everyone know, right?
Maybe it's possible to add a "download build" button.
I actually use Node for writing tools way more than other options because of how drama-free NPM is.
On the projects (such as Electron apps) where I'm forced to use NPM, it just feels icky to watch the thousands of sub-dependencies flowing in, crapping up my project.
So for a green-field project, which this thing seems to target, it would require installing NPM just for this thing. And then I'd need to figure out how to uninstall it cleanly without wrecking the project.
But give me a single .html and .css file that I can add to a new project and yeah, this seems cool.
There is a lot of upside/downside to NPM/Node, largly covered by smart people on the internet. The real question is "is NPM the simple solution to do X ?". And sometimes the answer is just "no, because it's over engineering the stuff".
The more I work in web development, the more I think we forgot the KISS rule to fancy tools.
I did WordPress based work a few years ago but I can't see any realistic way I could be doing that now and making any reasonable amount of money, because the reality is that just about anyone can do it, and if a company is going to pay a developer they'd rather pay them to develop something better suited to what they're doing.
I would also be more inclined to pay if you had multiple export options, e.g. pure html/css, different templating languages, scss, sass, react etc. Then I could see myself using this in every project going forward for sure. You could also expand into hosting directly and collecting leads.
I created a page, then clicked purchase and lost all my content, which was kind of annoying.
Setting up a bootstrap home page is surprisingly involved so this is really neat!
I like this project way better than Bootstrap Studio or any of the others I've tried.
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.
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 :)
I don't know what the problem is with that ?
File to adjust ( variables): https://github.com/twbs/bootstrap/blob/v4.2.1/scss/_variable...
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.
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.?
bootply.com, brix.io, pinegrow.com, layitout
(And of course the ones that are no longer with us: jetstrap and divshot)
edit: Actually, there are apparently a lot more I didn't know about: https://cssauthor.com/bootstrap-editors/
They also seem to have left out the "edit html" component, that was available in it.
I wanted an "import and export" feature or something to sync the projects. That was the most useful addition to the project.
Didn't finish it, it looks like they did a better integration ( it's 90% the same though), but they left some features out, which probably made it a lot easier.
I hated the structure of the html components with a screenshot in it. When updating the components it was a lot of "manual" hassle ( you can see the *.png files in the components.js link included below)
Edit: Found the original - https://codecanyon.net/item/sitebuilder-lite-dragdrop-site-b... This project has a changed layout ( bootstrap based) but the components work exactly the same way. Eg. https://bootstrapshuffle.com/components/js/components.js?v=a... is loading all the preconfigured html components per section ( footer, header, navigation, ...). I do think it was called elements.json though.
When i tried the project, i bought an update of the bootstrap v3 or v4 elements. But there were some issues with it ( wrong files and mismatched components) - I think it was > 1 year ago.
At least, i would have integrated angular for the builder. But they seem to have used the default/bought builder.js script and put a pricing page in front of it. This seems a doable project for 1 developer for < 2 weeks.
When I use a tool for work, I want them to charge enough to stay in business so they can 1) continue to exist (and I don't have to look for a replacement), and 2) continue to make improvements.
I can think of a hundred tools that were cheap, but died or got stagnant or let bugs fester because they couldn't afford to hire devs.
just one concern is that I want to download the source html file not the pug template one.