32 lines
2.2 KiB
Markdown
32 lines
2.2 KiB
Markdown
|
---
|
||
|
title: "Project management (Internal)"
|
||
|
date: "2023-06-24T16:05:06+03:00"
|
||
|
author: "anybody"
|
||
|
draft: true
|
||
|
has_articles: ["int-sandpoints.md", "int-infrastructure-info.md_","int-management.md","int-library.md","int-conventions.md","int-content.md","int-features.md","int-todo.md"]
|
||
|
keywords:
|
||
|
- internal
|
||
|
abstract: |
|
||
|
(Internal) 'Issue' type page, containing 'articles' related to managing and maintaining this project.
|
||
|
---
|
||
|
|
||
|
[Git]: https://git-scm.com/ "Git is a free and open-source distributed version control system."
|
||
|
[Hugo]: https://gohugo.io/ "Free and open-source static website builder."
|
||
|
|
||
|
# Introduction
|
||
|
|
||
|
This project runs on *Sandpoints*, a module/theme for the static website builder [Hugo][].
|
||
|
Sandpoints is developed for free, open, and collaborative publishing using open-source infrastructure.
|
||
|
Content is organized with plain-text Markdown files, and collaboration/version control is managed via [Git].
|
||
|
Thus, with the infrastructure in place, no programming is needed.
|
||
|
|
||
|
However, for managing and maintaining the site in a sustainable manner, as well as for processing/publishing submissions, *some knowledge is required pertaining to how this infrastructure works and how it can be maintained; how to work with ; how to manage distributed collaboration via a version control system; and adherence to the agreed upon conventions.*
|
||
|
|
||
|
This is an internal 'issue' (supposed to remain non-public, intended as a 'living document'), which contains the following 'articles':
|
||
|
|
||
|
1. , gives an overview of the philosophy of *Sandpoints*.
|
||
|
2.  contains instruction and guides for maintainers of the site.
|
||
|
3.  contains a guide for creating new content in a consistent and reliable way.
|
||
|
4.  is intended for gathering conventions we should go by.
|
||
|
5. , contains a guide for the library maintainers and contributors.
|
||
|
6. , is intended for listing potential required features, or filing issues.
|