WordPress next, and beyond: breaking the technical enclosure

1

Medium

#Blogging #Blogging Platform #CMS 2607 social mentions

2

VitePress

Obligatory meme: https://rakhim.org/honestly-undefined/19/ I'm personally in the top left corner and bottom right corner. I have used WordPress since 2004-2005, and I've also written a Python static site generator before using Flask, Frozen-Flask[1], and webpack. I've also made stops through tools like Sphinx, Hugo, Gatsby, and VitePress[2]. But my personal site continues to run WordPress[3]. I think I'd prefer something like VitePress these days for a technical documentation site. Also, I recently learned that MediaWiki with a reasonable theme like Citizen[4] is a nice choice for an open source powered private wiki, although I do find the Mediawiki markup language a little cumbersome versus simpler markup languages like reST or Markdown/MyST in the Python community (or GitHub-flavored Markdown or Asciidoc elsewhere). [1]: https://frozen-flask.readthedocs.io/ [2]: https://vitepress.dev/ [3]: https://amontalenti.com [4]: https://www.mediawiki.org/wiki/Skin:Citizen.

#Documentation #Documentation As A Service & Tools #Knowledge Base 8 social mentions

3

Local by Flywheel

Yeah -- though I think VVV has been thoroughly supplanted by Local: https://localwp.com Which almost every serious WP developer I know uses. (I personally use my own simplified Vagrant package management scripts with some ssh_config integration hooks because I work on more than WP and value standardisation across VM environments more than I value the features Local adds).

#CMS #Web And Application Servers #Website Design 231 social mentions