Utility gradle plugin to aid in authoring documentation on the Sinytra Modded MC Wiki.

Highlighted features:

• Local real-time, accurate preview of your documentation in the exact same look as it will have once uploaded to the wiki
• Automatically generating asset renders of inventory models for all mod items
• Revalidating documentation after publishing

The wiki toolkit plugin is available on the Gradle Plugin Portal.

You can install it in your project by adding the following code to your build.gradle.

plugins {
    id 'org.moddedmc.wiki.toolkit' version '<version>'
}

The initial step for using this plugin is registering documentation roots, which is done via a Gradle DSL.

A minimal setup may look like this:

wiki {
    docs {
        // The name of the object (examplemod) should match the registered wiki project ID (if it exists).
        examplemod {
            // The path to the folder containing the documentation metadata file (sinytra-wiki.json)
            root = file('docs/examplemod')
        }
    }
}

The plugin allows you to preview your mod documentation in real-time on your local machine. Behind the scenes, this is done by cloning the Wiki's GitHub repository and enabling local preview mode.

Running a local preview requires NodeJS. Please make sure you have NodeJS v20 or above installed on your computer.

To start the local preview, run the previewDocs task. This will set up and launch the local wiki environment.

Once ready, it will be available at http://localhost:3000.

Using org.gradle.daemon=false will prevent the npm task from existing when gradle is stopped, keeping it running in the background. Please check your gradle.properties file and make sure this property is either set to true or removed entirely.

This feature lets you automatically render and export images of in-game items the way they are displayed in one's inventory, saving you time preparing documentation assets.

The resulting files are placed in the appropriate subfolder inside your documentation root, ready to be referenced in docs with no additional configuration necessary.

Before running an export, make sure you have configured the exportedAssetNamespaces property of your documentation root(s).

wiki {
    docs {
        examplemod {
            // Namespaces of registered in-game item IDs that you wish to include in the asset export
            // for this documentation root.
            exportedAssetNamespaces = ['examplemod']
        }
    }
}

Next, install our Item Asset Exporter mod. There's no need to worry about it being present in all game runs, as it does not do anything by default nor does it affect the game. The exporter code only activates on designated run configurations.

// Adding a repository is not necessary; it is automatically installed by the plugin
dependencies {
    // ModDevGradle
    // Version list: https://maven.sinytra.org/org/sinytra/item-asset-export-neoforge
    runtimeOnly "org.sinytra:item-asset-export-neoforge:<version>"

    // Fabric Loom
    // Version list: https://maven.sinytra.org/org/sinytra/item-asset-export-fabric
    modRuntimeOnly "org.sinytra:item-asset-export-fabric:<version>"
}

Export tasks are created for each documentation root as automated client game runs. They will launch a game client that once initialized, exports the renders of all matching items and exists the game. Please do not interact with the client during this run. If the game reaches the main menu, please open a bug report on this repository.

To run an export for a documentation root, use the runExport<name>Assets, where <name> is the root's capitalized name, e.g. runExportExamplemodAssets.

As the wiki caches all pages once they've been visited, updates to the documentation source will not be reflected on the website until the cache has been periodically revalidated, which can take a long time.

To force all of your documentation pages to re-render the next time they're visited (effectively "publishing" your documentation), the plugin provides a straightforward way to submit a request to our API.

Before you run the task, generate a GitHub fine-grained access token with the following permissions:

• Repository permissions > Metadata = Read-only

Additionally, make sure the token can access the wiki project's GitHub repository.

Once the token is generated, add it to your gradle configuration under the wiki block.

wiki {
    wikiAccessToken = 'MY_ACCESS_TOKEN' // Starts with github_pat_
}

To revalidate a single documentation root, run revalidate<name>Docs where <name is the root's capitalized name, e.g. revalidateExamplemodDocs.

To revalidate all roots, run the revalidateDocs task.