Skip to content

Commit e9522f8

Browse files
committed
Rework README to separately invite existing MkDocs users and new users
1 parent 021c190 commit e9522f8

File tree

3 files changed

+28
-82
lines changed

3 files changed

+28
-82
lines changed

README.md

Lines changed: 22 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -1,85 +1,50 @@
11
# ProperDocs
22

3-
[![PyPI Version][pypi-v-image]][pypi-v-link]
4-
[![Build Status][GHAction-image]][GHAction-link]
3+
[![PyPI Version](https://img.shields.io/pypi/v/properdocs.svg)](https://pypi.org/project/properdocs/)
4+
[![Build Status](https://github.com/properdocs/properdocs/actions/workflows/ci.yml/badge.svg)](https://github.com/properdocs/properdocs/actions/workflows/ci.yml)
55

6-
ProperDocs is a static site generator intended for project documentation. Source files are written in Markdown and converted to static HTML during the build process.
6+
## Background
77

8-
Project configuration is defined in a YAML configuration file (`properdocs.yml`). This file specifies the documentation structure, theme configuration, and optional plugin settings.
8+
ProperDocs is a fork of [MkDocs](https://github.com/mkdocs/mkdocs/), aiming to be a complete drop-in replacement for it. We do not intend to make any breaking changes, but rather focus on bug fixes and incremental features. The fork was necessary because development of the original MkDocs project was abandoned.
99

10-
ProperDocs supports extension through plugins, themes and Markdown extensions.
10+
[**Please see our statement about forking MkDocs and how to migrate to ProperDocs**](https://github.com/orgs/ProperDocs/discussions/33).
1111

12-
For usage instructions and examples, see the Documentation.
12+
New users can get started using the [**documentation**](https://properdocs.org).
1313

14-
---
14+
## Description
1515

16-
## Features
16+
ProperDocs is a static site generator intended for project documentation. Source files are written in Markdown and converted to static HTML during the build process. This can then be deployed to any basic webserver (most commonly, [GitHub Pages](pages.github.com)).
1717

18-
Current functionality includes:
18+
Project configuration is defined in a YAML configuration file ([`properdocs.yml`](https://properdocs.org/user-guide/configuration/)). This file specifies the documentation structure, theme configuration, and optional plugin settings.
1919

20-
- Conversion of Markdown source files into static HTML pages
21-
- YAML-based configuration
22-
- Plugin system for extending functionality
23-
- Support for Markdown extensions
24-
- Support for third-party themes
25-
- Static output suitable for deployment on standard web servers
20+
ProperDocs is extensible through plugins, themes and Python-Markdown extensions. You can browse them in our [**catalog**](https://github.com/ProperDocs/catalog).
2621

27-
Additional functionality is available through plugins.
22+
[Our own **documentation**](https://properdocs.org/) uses ProperDocs. Examples and instructions on how to get started can be found there.
2823

29-
---
24+
If you're coming from MkDocs, check our [message welcoming MkDocs users](https://github.com/orgs/ProperDocs/discussions/33).
3025

31-
## Support
26+
## Support and discussions
3227

33-
If you encounter problems while using ProperDocs, the following resources are available:
28+
If you need help, do not hesitate to get in contact with the community!
3429

35-
- For questions and high-level discussions, use **[Discussions]** on GitHub.
36-
- For small questions, a good alternative is the **[Discord server]**.
37-
- To report a bug or make a feature request, open an **[Issue]** on GitHub.
30+
* To report a **bug** or make a **feature request** about **core ProperDocs functionality**, open an [**Issue**](https://github.com/ProperDocs/properdocs/issues/) on GitHub.
3831

39-
Support is generally limited to **core ProperDocs functionality**. Issues related to third-party themes, plugins or extensions should normally be reported to the maintainers of those projects.
32+
* For **questions** and high-level **discussions**, use [**Discussions**](https://github.com/ProperDocs/properdocs/discussions/) on GitHub.
4033

41-
Questions about such components may still be discussed in chat.
34+
Note that typically we will not be familiar with *features* of third-party plugins, so questions about them should probably go to their specific repository.
35+
But we definitely want to hear in case there are any compatibility problems versus MkDocs.
4236

43-
---
44-
45-
## Links
46-
47-
- [Official Documentation][properdocs]
48-
- [Latest Release Notes][release-notes]
49-
- [Catalog of third-party plugins, themes and recipes][catalog]
50-
51-
---
37+
* For **small questions of any kind**, a good option is the **[Discord server](https://discord.gg/CwYAgEPHZd)**.
5238

5339
## Contributing
5440

55-
Contributions are welcome.
56-
57-
For development setup, coding guidelines and contribution workflow, see the **[Contributing Guide]**.
58-
59-
---
41+
We welcome contributions from the community.
42+
Details are described in the [**Contributing Guide**](https://properdocs.org/about/contributing/) - including the development setup, coding guidelines and contribution workflow.
6043

6144
## Code of Conduct
6245

63-
All participants in the ProperDocs project are expected to follow the **[PSF Code of Conduct]**.
64-
65-
---
46+
All participants in the ProperDocs project are expected to follow the [**PSF Code of Conduct**](https://www.python.org/psf/conduct/).
6647

6748
## License
6849

6950
ProperDocs is distributed under the [**BSD-2-Clause license**](LICENSE).
70-
71-
<!-- Badges -->
72-
[pypi-v-image]: https://img.shields.io/pypi/v/properdocs.svg
73-
[pypi-v-link]: https://pypi.org/project/properdocs/
74-
[GHAction-image]: https://github.com/properdocs/properdocs/actions/workflows/ci.yml/badge.svg
75-
[GHAction-link]: https://github.com/properdocs/properdocs/actions/workflows/ci.yml
76-
77-
<!-- Links -->
78-
[properdocs]: https://properdocs.org
79-
[Issue]: https://github.com/properdocs/properdocs/issues
80-
[Discussions]: https://github.com/properdocs/properdocs/discussions
81-
[Discord server]: https://discord.gg/CwYAgEPHZd
82-
[release-notes]: https://properdocs.org/about/release-notes/
83-
[Contributing Guide]: https://properdocs.org/about/contributing/
84-
[PSF Code of Conduct]: https://www.python.org/psf/conduct/
85-
[catalog]: https://github.com/properdocs/catalog

docs/getting-started.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ An introductory tutorial!
66

77
## Installation
88

9-
To install ProperDocs, run the following command from the command line:
9+
To install ProperDocs and a basic theme for it, run the following command from the command line:
1010

1111
```bash
12-
pip install properdocs
12+
pip install properdocs properdocs-theme-mkdocs
1313
```
1414

1515
For more details, see the [Installation Guide].

docs/user-guide/installation.md

Lines changed: 4 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -66,42 +66,23 @@ $ properdocs --version
6666
properdocs, version 1.2.0 from /usr/local/lib/python3.8/site-packages/properdocs (Python 3.8)
6767
```
6868

69-
> NOTE:
70-
> If you would like manpages installed for ProperDocs, the [click-man] tool can
71-
> generate and install them for you. Simply run the following two commands:
72-
>
73-
> ```bash
74-
> pip install click-man
75-
> click-man --target path/to/man/pages properdocs
76-
> ```
77-
>
78-
> See the [click-man documentation] for an explanation of why manpages are
79-
> not automatically generated and installed by pip.
80-
<!-- -->
8169
> NOTE:
8270
> If you are using Windows, some of the above commands may not work
8371
> out-of-the-box.
8472
>
85-
> A quick solution may be to preface every Python command with `python -m`
73+
> A quick solution may be to preface every Python command with `py -m`
8674
> like this:
8775
>
8876
> ```bash
89-
> python -m pip install properdocs
90-
> python -m properdocs
77+
> py -m pip install properdocs
78+
> py -m properdocs
9179
> ```
9280
>
9381
> For a more permanent solution, you may need to edit your `PATH` environment
9482
> variable to include the `Scripts` directory of your Python installation.
95-
> Recent versions of Python include a script to do this for you. Navigate to
96-
> your Python installation directory (for example `C:\Python38\`), open the
97-
> `Tools`, then `Scripts` folder, and run the `win_add2path.py` file by double
98-
> clicking on it. Alternatively, you can download the [script][a2p] and run it
99-
> (`python win_add2path.py`).
83+
> Recent versions of Python include a script to do this for you.
10084
10185
[Python]: https://www.python.org/
10286
[python.org]: https://www.python.org/downloads/
10387
[pip]: https://pip.readthedocs.io/en/stable/installing/
10488
[get-pip.py]: https://bootstrap.pypa.io/get-pip.py
105-
[click-man]: https://github.com/click-contrib/click-man
106-
[click-man documentation]: https://github.com/click-contrib/click-man#automatic-man-page-installation-with-setuptools-and-pip
107-
[a2p]: https://github.com/python/cpython/blob/master/Tools/scripts/win_add2path.py

0 commit comments

Comments
 (0)