-
Notifications
You must be signed in to change notification settings - Fork 5
/
sitemapamic.php
123 lines (105 loc) · 3.85 KB
/
sitemapamic.php
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
<?php
return [
/*
|--------------------------------------------------------------------------
| Mode
|--------------------------------------------------------------------------
|
| Generate a single sitemap or separate sitemaps per collection/taxonomy etc.
|
| Can be 'single' or 'multiple'
|
*/
'mode' => 'single',
/*
|--------------------------------------------------------------------------
| Cache Key
|--------------------------------------------------------------------------
|
| The key used to store the output. Will be cached forever until EventSaved or TermSaved is fired.
|
*/
'cache' => 'sitemapamic',
/*
|--------------------------------------------------------------------------
| Cache Duration
|--------------------------------------------------------------------------
|
| The number of seconds for how long the Sitemapamic Cache be held for.
|
| Can be an integer or DateInterval - the same options that Laravel's Cache accepts.
|
| Or set to 'forever' to remember forever (don't worry, it will get cleared when an Entry,
| Term, Taxonomy or Collection is saved or deleted.
|
*/
'ttl' => 'forever',
/*
|--------------------------------------------------------------------------
| Defaults
|--------------------------------------------------------------------------
|
| Sets defaults for different collections.
|
| The key is the collection handle, and the array includes default configurations.
| Set "include" to true to either include or exclude without explicitly setting per article
| Frequency and Priority are standard for an XML sitemap
|
| 'includeTaxonomies' enables (or disables) whether taxonomy URLs will be generated, if used,
| for the collection. Only applies to Collections that actually use Taxonomies.
|
*/
'defaults' => [
/*'blog' => [
'include' => true,
'frequency' => 'weekly',
'priority' => '0.7'
],*/
'pages' => [
'include' => true,
'frequency' => 'yearly',
'priority' => '0.5',
'includeTaxonomies' => true,
]
],
/*
|--------------------------------------------------------------------------
| Globals
|--------------------------------------------------------------------------
|
| Sets global behaviour for items like taxonomies. Currently that's all that is supported.
|
| The 'globals.taxonomies' key expects an array of Taxonomy handles, each with an optional
| priority and frequency, just like the Defaults section. This means your Taxonomy blueprint
| can also take advantage of Term-specific 'meta_change_frequency' and 'meta_priority' fields,
| or fall back to these defaults when not set (or present).
|
| If you don't want the Taxonomy included in the sitemap, simply exclude it from the array.
|
*/
'globals' => [
'taxonomies' => [
/*'tags' => [
'frequency' => 'yearly',
'priority' => '0.5',
],
'categories' => []*/
]
],
/*
|--------------------------------------------------------------------------
| Field mappings
|--------------------------------------------------------------------------
|
| Allows you to map your blueprint fields with what Sitemapamic is expecting for controlling
| the change frequency, inclusion and priority.
|
| The key is the purpose (i.e. don't change this) and the value is the field handle in your blueprints.
|
*/
'mappings' => [
'include' => 'meta_include_in_xml_sitemap',
'change_frequency' => 'meta_change_frequency',
'priority' => 'meta_priority',
]
];