{{ template "base.html" . }} {{ define "extrahead" }} {{ end }} {{ define "content" }}
At Handmade Network, we pride ourselves on being open to hosting all sorts of projects, from low level tools to games to conscientious web applications to innumerable other carefully crafted varieties of software. With this in mind, there are certain standards of content quality that we expect projects hosted on the site to meet, and certain characteristics that we believe projects should uphold in order to best contribute to the community of software development we are attempting to cultivate.
This document outlines these standards and characteristics as specifically as possible, allowing for exceptions both in favor and against project approval if unanticipated circumstances arise. All project approvals or rejections will be accompanied by a justification, and we expect to be held accountable if the provided justification is insufficiently backed by these guidelines.
A high-quality Handmade Network project submission will:
Have a thorough description, which will give visitors several vital pieces of information in understanding the project:
Excellent descriptions will also make use of (BBCode) markup to make it easier for readers to scan for relevant information.
Provide links to other relevant websites where visitors may find out more about project development or the current activity of the author(s).
Common examples:
Provide several screenshots showcasing the current state of project development, if the project is visually oriented. Examples:
Providing as much information about your project as possible will help us decide whether it meets the qualifications listed below, and whether community members will be invested in your project's success.
For us to be willing to approve a project on the site, it should:
Be the development effort of an individual or small team, organization or company. We wish to keep the focus of this site on projects which highlight the inspiring work of small developers, projects which provide a high ratio of value-added to man-hours worked, and the exploration of software creation as a craft. We will refrain from defining “small” for the purposes of this guideline, and instead give examples of approvals and rejections:
Enrich to the community by releasing finished projects for community members to use or purchase and providing regular updates that inform and educate community members. We heavily encourage activities such as:
For more information on this, please see our Monthly Update Policy requirements and suggestions.
Additionally, there are some criteria that we guarantee will not be considered in approving or rejecting a project: