Publii: Open-source local WYSIWYG static site CMS
51–60 of 79 posts
Re: Publii: Open-source local WYSIWYG static site CMS
#52Re: Publii: Open-source local WYSIWYG static site CMS
#53Earlier quoted context omitted.
Dreamweaver was a good idea, but impossible for them to maintain. In my experience it was regularly giving bad results. It was a great tool for learning HTML and CSS though, but mainly because you would always end up just going into the source to fix it and view in DW. I would be very nervous of anyone using it these days for anything else.
I'm actually curious to see what Dreamweaver looks like these days, because I just recently found out that it's still around. I haven't seen it since like 2009 and I honestly thought it had been shut down.
Most who used Dreamweaver and relied on its extensions are now using another similar app called Wappler.
Re: Publii: Open-source local WYSIWYG static site CMS
#54I use Publii for a blog and enjoy it. I wanted actively developed static site generation with some reasonable template/theme options, and I didn't care about multi-user or team collaboration. I achieved multi-device sync via storing Publii in a cloud location. I looked into developing a theme using their theme system and it seemed unattainable for anyone who doesn't have significant time to invest in understanding th…
do you know if tailwind can be used in it?
Re: Publii: Open-source local WYSIWYG static site CMS
#55Earlier quoted context omitted.
> It's interesting to see people rediscover this idea of "develop locally, push static site to web," Yes! Dreamweaver was good 19 years ago and remains good today. Being able to see what you're doing, without running like treacle in the browser whilst editing (I'm looking at you, Divi and other WP visual theme builders), is an awesome experience. Like professionals in many other fields expect from their software.
I used dreamweaver when they had coldfusion integration. We ended up using the wysiwig just for verification because it would make the code so bloated (by late 90's standards). I recall using HotDog Professional for my personal stuff. Anyone else use it?
Re: Publii: Open-source local WYSIWYG static site CMS
#56Earlier quoted context omitted.
I'm actually curious to see what Dreamweaver looks like these days, because I just recently found out that it's still around. I haven't seen it since like 2009 and I honestly thought it had been shut down.
It's still around, but it's no longer being improved, just getting maintenance. Most of the people involved with it migrated elsewhere. Most who used Dreamweaver and relied on its extensions are now using another similar app called Wappler.
Re: Publii: Open-source local WYSIWYG static site CMS
#57It's interesting to see people rediscover this idea of "develop locally, push static site to web," but I think the weirdest thing for me is, why was this not a continuous thing? Broadly, this looks good for a blog format, but not sure if that's what people need? Anyway, for those interested, I just use http://zim-wiki.org plus a custom CSS template I did.
> It's interesting to see people rediscover this idea of "develop locally, push static site to web," Yes! Dreamweaver was good 19 years ago and remains good today. Being able to see what you're doing, without running like treacle in the browser whilst editing (I'm looking at you, Divi and other WP visual theme builders), is an awesome experience. Like professionals in many other fields expect from their software.
Good for what ? I remember designers trying to create pages with and the generated code was useless garbage once the customisation requests came in and they called in a dev
Re: Publii: Open-source local WYSIWYG static site CMS
#58It's interesting to see people rediscover this idea of "develop locally, push static site to web," but I think the weirdest thing for me is, why was this not a continuous thing? Broadly, this looks good for a blog format, but not sure if that's what people need? Anyway, for those interested, I just use http://zim-wiki.org plus a custom CSS template I did.
We had the likes of Netscape Composer, Front Page and Dreamweaver. They produced mountains of un-maintainable and not non-compliant html code.
When HTML5 came along there was a big push for compliant sites. Also it made sense to have a developer use the power of CSS3 to handle layouts and responsiveness elegantly. So the WYSIWYG editors fell out of favour.
Re: Publii: Open-source local WYSIWYG static site CMS
#59Earlier quoted context omitted.
> It's interesting to see people rediscover this idea of "develop locally, push static site to web," Yes! Dreamweaver was good 19 years ago and remains good today. Being able to see what you're doing, without running like treacle in the browser whilst editing (I'm looking at you, Divi and other WP visual theme builders), is an awesome experience. Like professionals in many other fields expect from their software.
I used dreamweaver when they had coldfusion integration. We ended up using the wysiwig just for verification because it would make the code so bloated (by late 90's standards). I recall using HotDog Professional for my personal stuff. Anyone else use it?
Re: Publii: Open-source local WYSIWYG static site CMS
#60It's interesting to see people rediscover this idea of "develop locally, push static site to web," but I think the weirdest thing for me is, why was this not a continuous thing? Broadly, this looks good for a blog format, but not sure if that's what people need? Anyway, for those interested, I just use http://zim-wiki.org plus a custom CSS template I did.
The inability to have interactive data-based content in static sites is why I went away from them, but the ability to progressively enhance a Next or (especially) SvelteKit site with data-y bits when it makes sense has gotten me in the habit of using them. Kind of a fan.