- Notifications
You must be signed in to change notification settings - Fork252
Official SUSE Linux Enterprise Documentation [Everyone, please use feature/ branches, create PRs and ensure CI runs successfully rather than just pushing to main!]
License
SUSE/doc-sle
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
This is the source for the official SUSE Linux Enterprise and openSUSE Leapdocumentation.
This repository hosts the documentation sources including translations (ifavailable) for the following products:
SUSE Linux Enterprise Desktop (SLED)
SUSE Linux Enterprise Server (SLES)
SUSE Linux Enterprise Micro (SLE-Micro)
openSUSE Leap
SLE 11 sources: seehttps://github.com/SUSE/doc-sle-legacy
Released versions of the SLE documentation are published athttps://documentation.suse.com/. Released versions of the openSUSE Leap documentation can befound athttps://doc.opensuse.org/.
Beta documentation versions are available athttps://susedoc.github.io/, where all commits tomain
and maintenance branches are automatically built.
Name | Purpose |
---|---|
| doc development (latest development version) |
| maintenance for released versions |
Use the main branch as the basis of your commits/of new feature branches.
Bugs are collected onhttps://bugzilla.suse.com. If possible please check forduplicates before creating a new report. When creating a new report, useSUSE Linux Enterprise Desktop
orServer
as product and in the next step the version.As component selectDocumentation
.
Thank you for contributing to this repo. When creating a pull request, please follow the guidelines below:
If you want to contribute to the most recent release, create your pull request against the
main
branch. Themain
branch is protected.If you want to contribute to a previous release, please create your pull request against the respective
maintenance/*
branch. These branches are also protected.Make sure all validation (GitHub Actions) checks are passed.
For your pull request to be reviewed, please tag the relevant subject matter expert(s) from the development team (if applicable) and members of the documentation team.
Implement the required changes. If you have any questions, ping a documentation team member in #team-suse-docs on Slack.
For help on style and structure, refer to theDocumentation Style Guide.
To contribute to the documentation, you need to write DocBook.
You can learn about DocBook syntax athttp://docbook.org/tdg5/en/html .
SUSE documents are generally built with DAPS (package
daps
) and theSUSE XSL Stylesheets (packagesuse-xsl-stylesheets
).Install the documentation environment with the following command:
sudo OneClickInstallUI https://susedoc.github.io/ymp/Documentation.ymp
Basic DAPS usage:
$ daps -d DC-<YOUR_BOOK> validate
: Make sure what you have written iswell-formed XML and valid DocBook 5$ daps -d DC-<YOUR_BOOK> pdf
: Build a PDF document$ daps -d DC-<YOUR_BOOK> html
: Build multi-page HTML document$ daps -d DC-<YOUR_BOOK> optipng
: Always optimize new PNG imagesLearn more athttps://opensuse.github.io/daps
About
Official SUSE Linux Enterprise Documentation [Everyone, please use feature/ branches, create PRs and ensure CI runs successfully rather than just pushing to main!]