Update README.md, public/index.html

merge-requests/1/head
Joeri Poesen 2022-11-12 11:54:04 +00:00
rodzic 7c94e78a2f
commit 4857a72740
2 zmienionych plików z 42 dodań i 69 usunięć

Wyświetl plik

@ -1,67 +1,10 @@
![Build Status](https://gitlab.com/pages/plain-html/badges/master/build.svg)
# Purpose
---
This is an unofficial list of organisations that have set up a Mastodon
instance under their own brand / identity.
Example plain HTML site using GitLab Pages.
## Why run your own instance?
Learn more about GitLab Pages at https://pages.gitlab.io and the official
documentation https://docs.gitlab.com/ce/user/project/pages/.
* https://martinfowler.com/articles/your-org-run-mastodon.html
---
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
**Table of Contents** *generated with [DocToc](https://github.com/thlorenz/doctoc)*
- [GitLab CI](#gitlab-ci)
- [GitLab User or Group Pages](#gitlab-user-or-group-pages)
- [Did you fork this project?](#did-you-fork-this-project)
- [Troubleshooting](#troubleshooting)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
## GitLab CI
This project's static Pages are built by [GitLab CI][ci], following the steps
defined in [`.gitlab-ci.yml`](.gitlab-ci.yml):
```
image: alpine:latest
pages:
stage: deploy
script:
- echo 'Nothing to do...'
artifacts:
paths:
- public
only:
- master
```
The above example expects to put all your HTML files in the `public/` directory.
## GitLab User or Group Pages
To use this project as your user/group website, you will need one additional
step: just rename your project to `namespace.gitlab.io`, where `namespace` is
your `username` or `groupname`. This can be done by navigating to your
project's **Settings**.
Read more about [user/group Pages][userpages] and [project Pages][projpages].
## Did you fork this project?
If you forked this project for your own use, please go to your project's
**Settings** and remove the forking relationship, which won't be necessary
unless you want to contribute back to the upstream project.
## Troubleshooting
1. CSS is missing! That means that you have wrongly set up the CSS URL in your
HTML files. Have a look at the [index.html] for an example.
[ci]: https://about.gitlab.com/gitlab-ci/
[index.html]: https://gitlab.com/pages/plain-html/blob/master/public/index.html
[userpages]: https://docs.gitlab.com/ce/user/project/pages/introduction.html#user-or-group-pages
[projpages]: https://docs.gitlab.com/ce/user/project/pages/introduction.html#project-pages

Wyświetl plik

@ -7,17 +7,47 @@
<link rel="stylesheet" href="style.css">
</head>
<body>
<div class="navbar">
<a href="https://pages.gitlab.io/plain-html/">Plain HTML Example</a>
<a href="https://gitlab.com/pages/plain-html/">Repository</a>
<a href="https://gitlab.com/pages/">Other Examples</a>
</div>
<h1>Hello World!!</h1>
<h1>Unofficial List of Official Mastodon Instances</h1>
<p>
This is a simple plain-HTML website on GitLab Pages, without any fancy static site generator.
This is a manually curated list of 'official' Mastodon
instances that have been set up by organisations under their
own brand / identity.
</p>
<p>
Here's Martin Fowler explaining why this is a good idea:
<a href="https://martinfowler.com/articles/your-org-run-mastodon.html">
Your organization should run its own Mastodon server
</a>.
</p>
<h2>Public sector</h2>
<ul>
<li><a href="https://social.bund.de/explore ">https://social.bund.de</a></li>
<li><a href="https://social.network.europa.eu/explore">https://social.network.europa.eu</a></li>
<li><a href="#">...</a></li>
</ul>
<h2>NGO</h2>
<ul>
<li><a href="#">...</a></li>
</ul>
<h2>Commercial<h2>
<ul>
<li><a href="#">...</a></li>
</ul>
<hr>
<h2>Contributing</h2>
<p>
Fork <a href="https://gitlab.com/mastolist/org-instances">https://gitlab.com/mastolist/org-instances</a>
and submit a merge request, or open an issue.
</p>
</body>
</html>