This was also mentioned in chat, but this post is to inform the community that as of October 25, 2023, I (aismallard) am now the official Project Lead for Wikijump, after a discussion with bluesoul. Apologies for the belated notification. This should not affect anything day-to-day within the project, and is simply intended to reflect the current reality of development. I highly appreciate bluesoul’s past and ongoing support of the project, particularly his expertise with AWS and his past work rigging up the ancient Wikidot code which sparked this project to start. His influence and assistance has been and continues…
Over the course of Wikijump development, both analyzing Wikidot code and implementing new Wikijump code, we’ve come across a fair number of table schemas. And there’s something we noticed, which is that there are a lot of database tables which essentially just link one thing to another, potentially tagging on some data. Now this is actually kind of a problem. Because, for each table, we need to have boilerplate for CRUD operations, as well as checks for sanity and permissions. This is a place where Wikidot definitely comes up short; user blocks only affect private messages, some systems for inputting…
It’s been a bit since the last development blog post, and as you can see from the post’s title, I meant to write this sooner. That said, things have generally proceeding gradually and smoothly. In this blog post I wanted to highlight one particular improvement made to DEEPWELL, our backend / internal API service. To first provide some context, within the current architecture, DEEPWELL is what stands in front of the various datastores (PostgreSQL, Redis, S3) to provide logical Wikijump operations. This means that it provides operations we think of when it comes to wikis, such as “edit this page”…
Hello all, it’s been a bit. Sorry about that. This is aismallard, I’ll be speaking about my perspective and work on Wikijump. Where we are now, why that is, and where I’d like to go from here. Past Missteps First I think there are a number of items which, while obvious in hindsight, contributed to a lot of delays which could’ve been avoided. This project originally began because bluesoul was able to, using a combination of publicly available resources and help from former contributors, piece together a Wikidot.org build. For those unaware, this was a (discarded) project to have an…
It’s been another week, and here’s another weekly update. We’ve had 230 commits in 29 merged pull requests across 200 files, for a total of 6,036 line additions and 2,406 deletions. More work has gone into our new frontend, along with incremental improvement to our PHP codebase in anticipation. This week, we got several big steps in our frontend, such as getting login and registration views, support for toasts, and infrastructure for gestures on touchscreen platforms. As this is the point where we’re gluing things together, we’ve needed re-evaluate and fix up parts of our stack, which has been challenging…
This last week has been productive. We’ve seen some steady progress on the PHP backend, and massive strides in our move towards a new frontend. In the last week we’ve pushed 298 commits across 380 files, for a total of 5,802 additions and 5,849 deletions in 29 different merged pull requests. On the PHP end, things have been incremental but not groundshaking. In addition to some refactoring and legacy code pruning, the diff functionality was updated to be more readable. Compare: Instead of Wikidot’s unusual word-based difference view, the original lines added/removed are shown. Additionally, it uses the context information…
It’s been another busy week over here in Wikijump! We’ve merged 18 pull requests from 4 people, and added 217 commits over 1,171 files. Most of the work we’ve seen has fallen into one of two categories, Docker and PHP. So let’s start with our build process: We use Docker to build Wikijump. Local deployments use docker-compose to stand up all the component containers (currently php-fpm, nginx, postgres, memcached) and permit it to run locally. Several big changes were made to our build process, primarily a refactored php-fpm Docker build to be significantly sped up by taking better advantage of…
Hello all, sorry for the delay since our last update. As a result, this post is going to be a summary of our last month and some change, rather than what happened in the last week. It’s been pretty busy, with 78 merged pull requests for a total of 877 commits across ~50,000 changed lines in 1,872 files. We’ve closed out several issues, including some rather longstanding ones. In FTML, we’ve implemented includes as two separate concepts, one “messy” (compatible with Wikidot’s notion of direct pasting, but uses a special handler due to incompatibility), and one “elements” (which uses the…
Hello again, the last week was a pretty solid one, with over 28,000 changed lines of code, although that number is inflated through the removal of some very large unused files. On the FTML side, several new changes and features were added to continue bringing the software closer to feature parity with the reference parsing and rendering. The details get into the weeds a bit, but things like rules that require being on their own line have been adjusted to work more cleanly, making future development easier. On the PHP side, the work that I mentioned last week for user…
Hello everyone, this past week has been very, very busy and a lot of important things were accomplished, with over 10,000 new lines of code merged to our dev build this past week alone. First off, the FTML parser that will replace the Text_Wiki package we’re currently using for converting wiki syntax into colors, links, modules, The ListPages Thing, and everything else that folks come up with, has officially reached 1.0 status. This is a very big deal; while that doesn’t mean that it’s ready right now as a drop-in replacement, it does mean that everything we want it to…