forgejo/docs
32
44
Fork
You've already forked docs
203

Add documentation for webmanifset customization #1669

Open
Mai-Lapyst wants to merge 2 commits from Mai-Lapyst/forgejo-docs:document-extended-webmanifest into next
pull from: Mai-Lapyst/forgejo-docs:document-extended-webmanifest
merge into: forgejo:next
forgejo:next
forgejo:v14.0
forgejo:v13.0
forgejo:v11.0
forgejo:v12.0
forgejo:bp-v12.0-a6c8557
forgejo:v7.0
forgejo:v10.0
forgejo:v9.0
forgejo:v8.0
forgejo:v1.21
forgejo:v1.20
forgejo:v1.19

This documents the changes proposed in forgejo/forgejo#5384.

This documents the changes proposed in https://codeberg.org/forgejo/forgejo/pulls/5384.
Add documentation for webmanifset customization
All checks were successful
pr / preview (pull_request_target) Successful in 1m48s
964905c542
 
This documents the changes proposed in forgejo/forgejo#5384.
Collaborator
Copy link

Preview ready: https://forgejo.codeberg.page/@docs_pull_1669/

Preview ready: https://forgejo.codeberg.page/@docs_pull_1669/
@ -192,0 +199,4 @@
The `display` property is omitted by default but can be set to `"standalone"` via the setting `STANDALONE` in the `[pwa]` section of `app.ini`.
If this is not enough for your usecase, forgejo additionally looks for an `manifest.json` file in your custom public files to serve instead. (See [Serving custom public files](#serving-custom-public-files)).
Member
Copy link

s/forgejo/Forgejo

s/forgejo/Forgejo
Mai-Lapyst marked this conversation as resolved
@ -192,0 +195,4 @@
Forgejo provides an [Web application manifest](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Manifest), retrieveable from the `/manifest.json` route. It is also included in every HTML response's `<head>` element.
By default, this manifest is configured very minimal, only setting the absolute required properties of `name`, `shortname`, `start_url` and two entries for `icons`.
Member
Copy link

Slight grammatical correction: "configured very minimally" or "configured to be very minimal".

Slight grammatical correction: "configured very minimal**ly**" or "configured **to be** very minimal".
Mai-Lapyst marked this conversation as resolved
Fix grammar
All checks were successful
pr / preview (pull_request_target) Successful in 1m50s
139b9eb86d

Can you also add the new [pwa] section to the config cheat sheet, please?

Can you also add the new `[pwa]` section to the config cheat sheet, please?
@ -192,0 +199,4 @@
The `display` property is omitted by default but can be set to `"standalone"` via the setting `STANDALONE` in the `[pwa]` section of `app.ini`.
If this is not enough for your usecase, Forgejo additionally looks for an `manifest.json` file in your custom public files to serve instead. (See [Serving custom public files](#serving-custom-public-files)).
Member
Copy link

s/an/a

Sorry, just saw this one now.

`s/an/a` Sorry, just saw this one now.
@ -192,0 +193,4 @@
## Customizing the PWA (Progressive Web App)
Forgejo provides an [Web application manifest](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Manifest), retrieveable from the `/manifest.json` route. It is also included in every HTML response's `<head>` element.
Member
Copy link

retrieveable is a misspelling of retrievable

retrieveable is a misspelling of retrievable
All checks were successful
pr / preview (pull_request_target) Successful in 1m50s
Required
Details
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u document-extended-webmanifest:Mai-Lapyst-document-extended-webmanifest
git switch Mai-Lapyst-document-extended-webmanifest
Sign in to join this conversation.
No reviewers
Labels
Clear labels
404

Broken links or missing content
backport/v1.19

Changes which should be backported to the v1.19 docs

Archived

backport/v1.20

Changes which should be backported to the v1.20 docs

Archived

backport/v1.21

Changes which should be backported to the v1.21 docs

Archived

backport/v10.0

Automated backport to v10.0

Archived

backport/v11.0

Automated backport to v11.0
backport/v12.0

Automated backport to v12.0

Archived

backport/v13.0

Automated backport to v13.0
backport/v14.0

Automated backport to v14.0
backport/v7.0

Automated backport to the v7.0 docs

Archived

backport/v8.0

Automated backport to the v8.0 docs

Archived

backport/v9.0

Automated backport to the v9.0 docs

Archived

good first issue

This issue is suitable for "drive-by contributors" wanting to contribute for the first time, and fixing it should be straightforward.
meta

Tooling and processes for maintaining the docs
new docs

Content to be added to the documentation

Archived

User research - Accessibility

Requires input about accessibility features, likely involves user testing.
User research - Blocked

Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community

Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)

Instance-wide configuration, authentication and other admin-only needs.
User research - Errors

How to deal with errors in the application and write helpful error messages.
User research - Filters

How filter and search is being worked with.
User research - Future backlog

The issue might be inspiring for future design work.
User research - Git workflow

AGit, fork-based and new Git workflow, PR creation etc
User research - Labels

Active research about Labels
User research - Moderation

Moderation Featuers for Admins are undergoing active User Research
User research - Needs input

Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard

Research on how users should know what to do next.
User research - Rendering

Text rendering, markup languages etc
User research - Repo creation

Active research about the New Repo dialog.
User research - Repo units

The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)

How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/docs!1669
Reference in a new issue
forgejo/docs
No description provided.
Delete branch "Mai-Lapyst/forgejo-docs:document-extended-webmanifest"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?