|
1 | 1 | # NOTE: will log all redux actions and transfers in console |
2 | 2 | debug: false |
3 | 3 |
|
4 | | -# Angular Universal server settings |
| 4 | +# Angular User Inteface settings |
5 | 5 | # NOTE: these settings define where Node.js will start your UI application. Therefore, these |
6 | 6 | # "ui" settings usually specify a localhost port/URL which is later proxied to a public URL (using Apache or similar) |
7 | 7 | ui: |
|
17 | 17 | # Trust X-FORWARDED-* headers from proxies (default = true) |
18 | 18 | useProxies: true |
19 | 19 |
|
20 | | -universal: |
21 | | - # Whether to inline "critical" styles into the server-side rendered HTML. |
22 | | - # Determining which styles are critical is a relatively expensive operation; |
23 | | - # this option can be disabled to boost server performance at the expense of |
24 | | - # loading smoothness. |
25 | | - inlineCriticalCss: true |
| 20 | +# Angular Server Side Rendering (SSR) settings |
| 21 | +ssr: |
| 22 | + # Whether to tell Angular to inline "critical" styles into the server-side rendered HTML. |
| 23 | + # Determining which styles are critical is a relatively expensive operation; this option is |
| 24 | + # disabled (false) by default to boost server performance at the expense of loading smoothness. |
| 25 | + inlineCriticalCss: false |
| 26 | + # Path prefixes to enable SSR for. By default these are limited to paths of primary DSpace objects. |
| 27 | + paths: [ '/home', '/items/', '/entities/', '/collections/', '/communities/', '/bitstream/', '/bitstreams/', '/handle/' ] |
| 28 | + # Whether to enable rendering of Search component on SSR. |
| 29 | + # If set to true the component will be included in the HTML returned from the server side rendering. |
| 30 | + # If set to false the component will not be included in the HTML returned from the server side rendering. |
| 31 | + enableSearchComponent: false, |
| 32 | + # Whether to enable rendering of Browse component on SSR. |
| 33 | + # If set to true the component will be included in the HTML returned from the server side rendering. |
| 34 | + # If set to false the component will not be included in the HTML returned from the server side rendering. |
| 35 | + enableBrowseComponent: false, |
26 | 36 |
|
27 | 37 | # The REST API server settings |
28 | 38 | # NOTE: these settings define which (publicly available) REST API to use. They are usually |
@@ -448,6 +458,12 @@ search: |
448 | 458 | enabled: false |
449 | 459 | # List of filters to enable in "Advanced Search" dropdown |
450 | 460 | filter: [ 'title', 'author', 'subject', 'entityType' ] |
| 461 | + # |
| 462 | + # Number used to render n UI elements called loading skeletons that act as placeholders. |
| 463 | + # These elements indicate that some content will be loaded in their stead. |
| 464 | + # Since we don't know how many filters will be loaded before we receive a response from the server we use this parameter for the skeletons count. |
| 465 | + # e.g. If we set 5 then 5 loading skeletons will be visualized before the actual filters are retrieved. |
| 466 | + defaultFiltersCount: 5 |
451 | 467 |
|
452 | 468 |
|
453 | 469 | # Notify metrics |
@@ -503,6 +519,16 @@ notifyMetrics: |
503 | 519 | description: 'admin-notify-dashboard.NOTIFY.outgoing.delivered.description' |
504 | 520 |
|
505 | 521 |
|
506 | | - |
507 | | - |
508 | | - |
| 522 | +# Live Region configuration |
| 523 | +# Live Region as defined by w3c, https://www.w3.org/TR/wai-aria-1.1/#terms: |
| 524 | +# Live regions are perceivable regions of a web page that are typically updated as a |
| 525 | +# result of an external event when user focus may be elsewhere. |
| 526 | +# |
| 527 | +# The DSpace live region is a component present at the bottom of all pages that is invisible by default, but is useful |
| 528 | +# for screen readers. Any message pushed to the live region will be announced by the screen reader. These messages |
| 529 | +# usually contain information about changes on the page that might not be in focus. |
| 530 | +liveRegion: |
| 531 | + # The duration after which messages disappear from the live region in milliseconds |
| 532 | + messageTimeOutDurationMs: 30000 |
| 533 | + # The visibility of the live region. Setting this to true is only useful for debugging purposes. |
| 534 | + isVisible: false |
0 commit comments