A yanky theme that uses Minecraft assets to create an accurate Minecraft experience.
Originally made for a Minecraft presentation I held in a networking course, where me and my project partners measured, analyzed, and presented the network usage of Minecraft. This presentation template is a work of my own, however.
See this repo for some more tools I used to make graphs in that project as well!
Marp is a tool for creating presentations from Markdown. It's not very difficult to learn, and once you know the basics, it's a lot more performant, efficient and portable than PowerPoint. This project is in no way officially tied to or sponsored by Marp, but it is dependent on it's toolset.
| Real menu | My Marp menu |
|---|---|
 |
 |
It's even got hover effects!
| Backgroundless slide | A slide with a background and split layout |
|---|---|
 |
 |
Note the use of the pinging symbol as a page index. While it looks best for 25 pages, you can expand it by adding more bars. As you can imagine, this is manual and not automated.
Resource packs can be replaced by just deleting the prior and importing a new one. As long as you don't change any folder names, any resource pack should act as a drop-in replacement. Keep in mind borders will need to be regenerated after switching.
No guide is provided for Marp CLI. I assume anyone using the CLI is knowledgable enough to do the proper steps themselves, though you can use part of this tutorial.
This theme is yank, and needs some work. You will likely need to implement features yourself. It is to be seen as "a good place to start". If you do implement more necessities, please do either fork this repo or commit to it directly, I would love your help!
- Visual Studio Code or VSCodium
- Marp extension
- CSS and Markdown knowhow
- WinRar or other Zip tool (if using)
- Git and basic git knowledge (if using)
- Minecraft installed, to extract textures (if using default)
- Download this GitHub repository, either by downloading the latest
release.zipor cloning. Delete the previews folder if you wish. - Download/extract the necessary third-party assets. See "Mining for assets"
- Place them according to the patterns defined in the CSS file, unless you wish to change it:
assets/
- fonts
- defaulttexturepack <-- put textures here!
- images
Follow the common steps. You won't need to do more :)
You can however, optionally, remove/change the .gitgnore to let you upload the exported textures. Please consult the proper terms of service of GitHub and the laws of your country as to wheter you can actually do this.
Note! this theme will likely not work very well together with others.
- Follow the common steps, but put the files where you'd like them and make the necessary modifications to integrate it.
- Modify your
.vscode/settings.jsonto include the following:
...
{
"markdown.marp.themes": [
...
"path/to/the-css-file.css"
...
]
}
...
The main menu is created by declaring a section as a menu section. See the code snippet in example.md to see how you should implement it. You will need to modify the code accordingly if you don't want to use the same button layout.
The menu is implemented by forcing and choking list elements to behave like buttons. This is not only cruel, but extremely yank. Feel free to provide a better solution if you have one.
For credits sake, I have to mention that this menu was originally based on this codesnippet by joexmdq, but has since been heavily modified (and updated to look like more recent versions of Minecraft).
By default, this theme uses Minecraft Seven for the font (which you can find here). Minecraftia also works great.
This stylesheet sources almost all graphics from a resource pack.
To use the default resource pack, follow this guide, which explains how to "mine" it out of the Minecraft client. Otherwise you can use any resource pack you like, just unzip it and drop it in the "assets/texturepack" folder. The way things are configured, any resource pack can act as a drop -in replacement, owing to the static nature of resource pack file structures.
You'll have to make these yourself, but the process is fairly simple:
- In your favorite design tool*, create a square canvas. The size of it is dictated by your needs, but a basic border would be
3 x size of texturepx in both height and width. - Slap your textures in there, and tile them to fill the canvas. In GIMP you can do this with the paint bucket, using the image fill tool (see this guide)
- Export it as png, and put it where you'd like. Preferably in "assets/borders". See examples for how to use.
This is an example of a border image, that creates a log border around a slide. I won't provide the source file, but heres a screenshot of it.
| Border | Border in use |
|---|---|
 |
|
The menu uses a stitched together set of screenshots, laid out like the way the game does it (see this wiki article). This image is provided for you, since it's nothing more than some screenshots. If you wish to create your own, use my image as reference together with this video.
For obvious reasons, I won't provide or host these resources myself, since they're protected under copyright law.
Caution
Similarly, I would strongly advise you not to use this theme for a presentation from which you will monetarily gain - unless you get written permission from both the font author AND Mojang or replace these assets with ones you have rights to use.
As for my stylesheet, I grant you full permission to use it and modify it as you please, but I would be glad if you credited me :)
For the animations to work, it is crucial that you export in a format that supports them. I suggest HTML, but keep in mind that it will be less portable than, say, a PDF.
When handing or sending things many people will want a PDF or PowerPoint file, so do make sure your presentation doesn't look odd in those formats!
A guide on how to export can be found in Marp's extension documentation.
If you need portability, one decent suggestion is using a free and static website host, like Netlify, so you can access the presentation without the dependencies. This is particularly preferable, since Netlify can integrate and be dynamically updated with GitHub repositories. You could, for example, fork this repo and bind it to your Netlify website. (This project is NOT affiliated with or sponsored by Netlify, it's merely a suggestion)
It is highly unlikely I personally will update this project any further. This repository mostly serves as a portfolio piece and archival entry.