▲ | Animats 4 days ago | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
> All the tools are still there to build websites however you want. No, they're not. The good tools all died off. I wish there was still something good that just edited HTML and CSS locally and uploaded it. Mozilla Composer died long ago. Its spinoffs, Nvu, Kompozer, and Blue Griffon are all dead. You can still buy Dreamweaver, but Adobe wants $300 or so a year now, and they really want to sell you their whole "creative cloud". Brackets has been abandoned and converted to something called Phoenix, which now does more things less well. I don't want a whole "content management system" that assembles pages on the fly from a database. Just a decent WYSIWYG editor that can also manage uploads. I don't want something controlled by the hosting service. I'm using a Dreamhost account for this site, and its main purpose is to host some API endpoints implemented in Go. The human-readable web part is just the documentation. There are many images, so I need more layout than Markdown supports. It's not a blog, so Wordpress is the wrong tool for the job. You'd think there would be something good. As far as I can tell, no. Anybody know of anything? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | motorest 4 days ago | parent | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
> I wish there was still something good that just edited HTML and CSS locally and uploaded it. What's wrong with launching a file watcher, opening the page in a browser, and editing away with any IDE of your choice? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | al_borland 4 days ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
It looks like RapidWeaver still exists, though last I used it, it wasn’t a typical WYSIWYG editor like classic Dreamweaver. I found it has a higher learning curve than I’d like. https://www.realmacsoftware.com/rapidweaver/ Most WYSIWYG editors have become text editors. Panic’s Coda has become Nova (a text editor). Even what I last saw of Dreamweaver, it was very code-forward. I think the less technical users just use platforms. More technical users have historically turned up their noses as WYSIWYG editors, so it left a gap in the market. Looking at AlternativeTo, there are some options out there. https://alternativeto.net/software/adobe-dreamweaver/?featur... | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | rekabis 4 days ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
> Just a decent WYSIWYG editor that can also manage uploads. There is your problem. Any such editor will invariably be heavily limited to what its developers envisioned the user’s use cases as being, and therefore WYSIWYG software is fiendishly complex as a result for even simple layouts and designs (as opposed to straight code editors). Plus, web frameworks (HTML, CSS, JS, etc.) are still evolving on a yearly basis, requiring constant updates to any WYSIWYG that demand either a paid product or something that rides on the well-funded coattails of another service or product. If you want a piece of software that lasts, learn how to code directly. If you can picture a soccer ball in your mind, you can (mostly) reliably envision what code will appear like on the screen before you even test it. It takes practice and experience, but building the WYSIWYG aspect into your own mind is eminently doable unless you have aphantasia. And honestly, that’s how I view WYSIWYG editors: as accessibility tools for people whose legitimate disability is aphantasia. For everyone else, WYSIWYG tools are a skills-nerfing crutch, as it isolates the user’s use of code from its direct consequences. By working directly with code, you are forced to envision the output of each element and its relationship to everything else on the page. And honestly, the only major exception I can come up with is desktop publishing, where the underlying “code” is typically restricted to that master file on the designer’s computer, and has no effect beyond it… once the file is printed out (and the content leaves the designer’s control) everything is cemented ‘in stone’ and the underlying “code” no longer has any impact. Because the system is radically more constrained, with markup standards that are limited to the software and not world+dog, a WYSIWYG program makes sense. And yet… most are still paid products. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | electroly 4 days ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use SeaMonkey Composer. It's still alive and I use it. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | wolpoli 4 days ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
WordPress isn't just for blogs and I think it might fit your use case for documenting a set of API endpoint. There is likely a free swagger plugin in WordPress that would help you, although I hadn't really looked. Other than that, you could look at using a static site generator like MkDocs or Docusaurus. It'll generate a site of HTML pages, and you could either manually upload them to your host, or you could set up an automation that updates your host when you merge changes into git. I think my response illustrates another problem with modern tools compared to the 90s - there isn't any single tool that edits HTML/CSS and upload them. You now have to glue together several tools. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | Gormo 4 days ago | parent | prev [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
SeaMonkey is still actively maintained, and still has Composer. |