Did Publii ever get nested structure support? I remember having to perform workarounds for subcategories.
Publii: Open-source local WYSIWYG static site CMS
41–50 of 79 posts
Re: Publii: Open-source local WYSIWYG static site CMS
#42It'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.
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
#43I 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
#44running several blogs on publii! (https://typogram.co/blog/) Loving it!
the only feedback I have is making co-editing easy. sometimes I co-write articles. this is rly hard with a desktop app.
Also, wishing for some kind of SEO plugin that would make writing descriptions easier.
Re: Publii: Open-source local WYSIWYG static site CMS
#45Earlier quoted context omitted.
> Dreamweaver was good 19 years ago and remains good today. Notepad.exe was good 19 years ago. Dreamweaver? Not so much. :)
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.
Re: Publii: Open-source local WYSIWYG static site CMS
#46Earlier quoted context omitted.
http://jrm4.com With this: https://github.com/jrm4/Eight-Five-Zero (Kind of messy, but it's utilitarian for my work and such)
Thanks. A lot of good resources on your site!
Thanks, I think the thing that has served me the best is how easy and quick I've made it to update. I open zim (which is a native app, no login or anything), change what I need to change, and have a short little SSH/rsync shell script that updates.
It's really nice that I can update the website in the middle of class as I'm teaching with very little issue.
Re: Publii: Open-source local WYSIWYG static site CMS
#47Has anyone experimented with its WP importer and could comment about its quality or efficiency?
It works. But it only works for standard WP stuff. Throw in a non-standard gallery or something, and it will degrade.
Re: Publii: Open-source local WYSIWYG static site CMS
#48Earlier 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.
Many other fields do not have to edit turing complete results. Also you don’t need WYSIWYG but WYSIWTG, since you want to see what THEY will be getting, they being endless combinations of systems. I was there, too. Dreamweaver was not good enough.
Dreamweaver all too often spun nightmares
Re: Publii: Open-source local WYSIWYG static site CMS
#49Huge Publii fan here, glad to see it on the front page. I feel like the only thing holding Publii back is the lack of theme diversity, and definitely could use some third-party designer love to push it forward.
This was my take away too. Looks great, but personally if I'm going to use this for a docs site, or for a wiki, or some sort of knowledge base, I'd really need to have an out of the box theme available. There are some there, but not enough variation for my liking. So rather than a quick win, this has to be put on the pile of "take a look and determine if I have time".
Not that it takes away from what looks like a great product, but that's the journey I went through, as a regular, overly-busy employee-startup founder, 14 hours into a Saturday. "I love it, but it's over my time-cost threshold if it needs custom themes".
Re: Publii: Open-source local WYSIWYG static site CMS
#50Huge Publii fan here, glad to see it on the front page. I feel like the only thing holding Publii back is the lack of theme diversity, and definitely could use some third-party designer love to push it forward.
This seems to be the story for nearly all static site generators (except for maybe Jekyll, whose drawback is it's a hassle for non-Ruby devs to properly setup a Ruby environment, especially on Windows).
I migrated from WordPress to Hugo for awhile, but eventually gave and migrated back. You can love WordPress or hate it, but it has an infinite variety of paid and free professional-quality themes. Hugo has a slew of one-person amateur projects, the best of which are half-baked clones of WordPress themes. What's worse, they tend to be poorly-maintained, and stop working whenever Hugo introduces breaking changes (which at least a few years ago, was frequent).
I appreciate all of the conceptual advantages of a static site generator versus a CMS application host. But for most users, a website tool is simply only as good as its theme ecosystem.