The django-wiki library has a breaking change from v0.5 to v0.6 in Bootstrap v4 (see here). This upgrade breaks the wiki layout, and an update to CSS class names is likely necessary to continue with a newer version of django-wiki.
Rather than continue to maintain the wiki, we can convert this site to a set of static pages, perhaps using Jekyll.
A static site should be feasible as changes to the site have been infrequent and most likely do not require a wiki with multiple users. Using a static page will have the added benefit of making the database much simpler.
The
django-wikilibrary has a breaking change fromv0.5tov0.6in Bootstrap v4 (see here). This upgrade breaks the wiki layout, and an update to CSS class names is likely necessary to continue with a newer version ofdjango-wiki.Rather than continue to maintain the wiki, we can convert this site to a set of static pages, perhaps using Jekyll.
A static site should be feasible as changes to the site have been infrequent and most likely do not require a wiki with multiple users. Using a static page will have the added benefit of making the database much simpler.