-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation must be prepared #6
Comments
@gsteel |
Ah, I suppose this is still a blocker for |
@Ocramius |
@froschdesign |
They should be maintained here, yep. |
Right, but only the content! No needed for MkDocs configuration here because the Markdown files will be inserted via the Snippets extension of the PyMdown Extensions in the documentation of laminas-i18n. This means:
For reference see the documentation of laminas-i18n: I recommend to use these pages as blueprints. |
The following topics must be covered and each must be presented on a separate page:
The configuration with
default-country-code
andacceptable-number-types
should be implemented in the section "Application Integration".The content of the pages must follow the existing structure.
Examples:
Unfortunately, at the moment we do not have an operational solution to merge documentations.
Therefore, the new pages will be added to the repository of laminas-i18n – temporary.(To ensure that the topic is not forgotten, the problem is followed up in a separate issue report.)
Therefore we will use the URL snippets extension of PyMdown.
The goal is still to keep information together for the reader. At the moment, a lot is fragmented and you have to search too much or coherent explanations are missing.
(Examples: laminas-paginator and laminas-paginator-adapter-laminasdb or Mezzio and authentication)
The text was updated successfully, but these errors were encountered: