add(README) # Documentation

This commit is contained in:
Aire-One 2021-10-21 20:12:56 +02:00
parent 4660dc62f8
commit fae32823a3
2 changed files with 23 additions and 10 deletions

View File

@ -2,7 +2,8 @@ name: Build doc
on: on:
push: push:
branches: [$default-branch] branches:
- $default-branch
workflow_dispatch: workflow_dispatch:
permissions: permissions:
@ -10,7 +11,8 @@ permissions:
pages: write pages: write
id-token: write id-token: write
# Cancel the previous run if it's still in progress # Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency: concurrency:
group: "pages" group: "pages"
cancel-in-progress: false cancel-in-progress: false
@ -19,13 +21,10 @@ jobs:
build: build:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- name: Checkout - uses: actions/checkout@v4
uses: actions/checkout@v4 - uses: lunarmodules/ldoc@v1.5.0
- name: Generate docs with LDoc - uses: actions/upload-pages-artifact@v3
uses: lunarmodules/ldoc@v1.5.0
- name: Upload static files as artifact
id: deployment id: deployment
uses: actions/upload-pages-artifact@v3
with: with:
path: doc/ path: doc/
deploy: deploy:
@ -35,6 +34,5 @@ jobs:
name: github-pages name: github-pages
url: ${{ steps.deployment.outputs.page_url }} url: ${{ steps.deployment.outputs.page_url }}
steps: steps:
- name: Deploy to GitHub Pages - uses: actions/deploy-pages@v4
id: deployment id: deployment
uses: actions/deploy-pages@v4

View File

@ -4,3 +4,18 @@ A declarative API to connect signals for the AwesomeWM.
It completes the native `gears.signal` module to make signal connection easier It completes the native `gears.signal` module to make signal connection easier
to manage. to manage.
## Documentation
API references for the latest release are available at <https://aire-one.github.io/awesome-slot/index.html>.
It is also possible to manually build the documentation locally using ldoc. The
documentation content is part of the source code, and all configurations needed
are provided by the `config.ld` file. To generate documentation, you need to
run :
```sh
ldoc .
```
The documentation site will be generated in the `doc` directory.