luanti-org / luanti-org/luanti-org.github.io

Create an official media kit page for Minetest

Open
#175 5 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

@content enhancement good first issue
Dominant language
SCSS
Stars
141
Forks
82
PR merge metrics
No merged PRs in 30d

Description

Media kit is promotional tool that contains specific information about a website, publication, games, etc. While some people thought media kits are press kits, they are slightly different in nature.

Media kit page will greatly help people who want to share about Minetest on other platforms or websites. It creates a standard guideline on how to promote the game or website.

I propose that the website to have a page of media kit, and at least includes the following:

  • A simple paragraph or catchphrases that can be used to identify Minetest from all other games.
  • The Minetest logo in original colours (at least in SVG, optionally PNG) -downloadable
  • The Minetest logo in white-on-other-colour variant (at least in SVG, optionally PNG) - downloadable
  • The mentions of the official colour codes of Minetest logo (and optionally the blueprint of the logo layout - eg the shapes and the features of the logo: I see cactus, tree, grass, sand, water, cave, is that correct?)
  • A brochure and/or leaflet of Minetest (maybe ask Rubenwardy for this, iirc he has created PDF that he use to print in some conventions before? or create new one if he refuses to include his) - downloadable

Of course, all these should also be licensed the same way as the rest of the website (or mention the specific license if they were not licensed the same way).

Looking at the license file in the main repo, it looks like the base SVG file of the Minetest logo might be licensed under CC BY-SA 3.0, can someone confirm it? And the base SVG file itself is here.

I feel that media kit page should be stand-alone page but I don't mind if it's combined with the suggestions in #123

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the proposed related work in #123, the main repository's LICENSE.txt, and misc/minetest.svg to confirm asset licensing. Define a standalone media kit page containing the listed copy, logo variants, colour information, and downloadable brochure, with licensing stated; completion means all unchecked requirements are addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
scss
Domain
content, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.