@angular-wave/angular.ts 0.0.7 → 0.0.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (65) hide show
  1. package/dist/angular-ts.cjs.js +1 -1
  2. package/dist/angular-ts.esm.js +1 -1
  3. package/dist/angular-ts.umd.js +1 -1
  4. package/docs/.cspell.yml +8 -0
  5. package/docs/.github/dependabot.yml +14 -0
  6. package/docs/.nvmrc +1 -0
  7. package/docs/CONTRIBUTING.md +28 -0
  8. package/docs/Dockerfile +4 -0
  9. package/docs/LICENSE +201 -0
  10. package/docs/README.md +184 -0
  11. package/docs/assets/scss/_variables_project.scss +6 -0
  12. package/docs/config.yaml +15 -0
  13. package/docs/content/en/_index.md +77 -0
  14. package/docs/content/en/about/featured-background.jpg +0 -0
  15. package/docs/content/en/about/index.md +35 -0
  16. package/docs/content/en/blog/_index.md +8 -0
  17. package/docs/content/en/blog/news/_index.md +4 -0
  18. package/docs/content/en/blog/news/first-post/featured-sunset-get.png +0 -0
  19. package/docs/content/en/blog/news/first-post/index.md +48 -0
  20. package/docs/content/en/blog/news/second-post.md +244 -0
  21. package/docs/content/en/blog/releases/_index.md +4 -0
  22. package/docs/content/en/blog/releases/in-depth-monoliths-detailed-spec.md +244 -0
  23. package/docs/content/en/community/_index.md +6 -0
  24. package/docs/content/en/docs/_index.md +29 -0
  25. package/docs/content/en/docs/concepts/_index.md +14 -0
  26. package/docs/content/en/docs/contribution-guidelines/_index.md +79 -0
  27. package/docs/content/en/docs/examples/_index.md +13 -0
  28. package/docs/content/en/docs/getting-started/_index.md +35 -0
  29. package/docs/content/en/docs/getting-started/example-page.md +240 -0
  30. package/docs/content/en/docs/overview/_index.md +36 -0
  31. package/docs/content/en/docs/reference/_index.md +12 -0
  32. package/docs/content/en/docs/reference/parameter-reference.md +211 -0
  33. package/docs/content/en/docs/tasks/Ponycopters/_index.md +12 -0
  34. package/docs/content/en/docs/tasks/Ponycopters/configuring-ponycopters.md +238 -0
  35. package/docs/content/en/docs/tasks/Ponycopters/launching-ponycopters.md +236 -0
  36. package/docs/content/en/docs/tasks/_index.md +21 -0
  37. package/docs/content/en/docs/tasks/beds.md +237 -0
  38. package/docs/content/en/docs/tasks/porridge.md +237 -0
  39. package/docs/content/en/docs/tasks/task.md +237 -0
  40. package/docs/content/en/docs/tutorials/_index.md +13 -0
  41. package/docs/content/en/docs/tutorials/multi-bear.md +236 -0
  42. package/docs/content/en/docs/tutorials/tutorial2.md +236 -0
  43. package/docs/content/en/featured-background.jpg +0 -0
  44. package/docs/content/en/search.md +4 -0
  45. package/docs/docker-compose.yaml +13 -0
  46. package/docs/docsy.work +5 -0
  47. package/docs/docsy.work.sum +0 -0
  48. package/docs/go.mod +5 -0
  49. package/docs/go.sum +6 -0
  50. package/docs/hugo-disabled.toml +221 -0
  51. package/docs/hugo.yaml +220 -0
  52. package/docs/layouts/404.html +7 -0
  53. package/docs/layouts/_default/_markup/render-heading.html +1 -0
  54. package/docs/netlify.toml +12 -0
  55. package/docs/package.json +42 -0
  56. package/package.json +1 -1
  57. package/src/core/compile.js +13 -165
  58. package/src/core/compile.md +51 -16
  59. package/src/core/filter.md +23 -17
  60. package/src/core/interval.md +73 -72
  61. package/src/core/sce.js +2 -13
  62. package/src/injector.md +30 -1
  63. package/test/messages/messages.spec.js +1 -1
  64. package/test/ng/compile.spec.js +91 -289
  65. package/test/ng/directive/form.spec.js +8 -8
@@ -0,0 +1,8 @@
1
+ # cSpell:ignore textlintrc
2
+ # For settings, see
3
+ # https://www.streetsidesoftware.com/vscode-spell-checker/docs/configuration/
4
+ version: '0.2'
5
+ caseSensitive: true
6
+ words:
7
+ - Docsy
8
+ - Goldydocs
@@ -0,0 +1,14 @@
1
+ version: 2
2
+ updates:
3
+ - package-ecosystem: npm
4
+ directory: "/"
5
+ schedule:
6
+ interval: daily
7
+ time: '20:00'
8
+ open-pull-requests-limit: 10
9
+ - package-ecosystem: bundler
10
+ directory: "/"
11
+ schedule:
12
+ interval: daily
13
+ time: '20:00'
14
+ open-pull-requests-limit: 10
package/docs/.nvmrc ADDED
@@ -0,0 +1 @@
1
+ lts/*
@@ -0,0 +1,28 @@
1
+ # How to Contribute
2
+
3
+ We'd love to accept your patches and contributions to this project. There are
4
+ just a few small guidelines you need to follow.
5
+
6
+ ## Contributor License Agreement
7
+
8
+ Contributions to this project must be accompanied by a Contributor License
9
+ Agreement. You (or your employer) retain the copyright to your contribution;
10
+ this simply gives us permission to use and redistribute your contributions as
11
+ part of the project. Head over to <https://cla.developers.google.com/> to see
12
+ your current agreements on file or to sign a new one.
13
+
14
+ You generally only need to submit a CLA once, so if you've already submitted one
15
+ (even if it was for a different project), you probably don't need to do it
16
+ again.
17
+
18
+ ## Code reviews
19
+
20
+ All submissions, including submissions by project members, require review. We
21
+ use GitHub pull requests for this purpose. Consult
22
+ [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
23
+ information on using pull requests.
24
+
25
+ ## Community Guidelines
26
+
27
+ This project follows
28
+ [Google's Open Source Community Guidelines](https://opensource.google.com/conduct/).
@@ -0,0 +1,4 @@
1
+ FROM floryn90/hugo:ext-alpine
2
+
3
+ RUN apk add git && \
4
+ git config --global --add safe.directory /src
package/docs/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/docs/README.md ADDED
@@ -0,0 +1,184 @@
1
+ # Docsy Example
2
+
3
+ [Docsy][] is a [Hugo theme module][] for technical documentation sites, providing easy
4
+ site navigation, structure, and more. This **Docsy Example Project** uses the Docsy
5
+ theme component as a hugo module and provides a skeleton documentation structure for you to use.
6
+ You can clone/copy this project and edit it with your own content, or use it as an example.
7
+
8
+ In this project, the Docsy theme is pulled in as a Hugo module, together with
9
+ its dependencies:
10
+
11
+ ```console
12
+ $ hugo mod graph
13
+ ...
14
+ ```
15
+
16
+ For Docsy documentation, see [Docsy user guide][].
17
+
18
+ This Docsy Example Project is hosted on [Netlify][] at [example.docsy.dev][].
19
+ You can view deploy logs from the [deploy section of the project's Netlify
20
+ dashboard][deploys], or this [alternate dashboard][].
21
+
22
+ This is not an officially supported Google product. This project is currently maintained.
23
+
24
+ ## Using the Docsy Example Project as a template
25
+
26
+ A simple way to get started is to use this project as a template, which gives you a site project that is set up and ready to use. To do this:
27
+
28
+ 1. Use the dropdown for switching branches/tags to change to the **latest** released tag.
29
+
30
+ 2. Click **Use this template**.
31
+
32
+ 3. Select a name for your new project and click **Create repository from template**.
33
+
34
+ 4. Make your own local working copy of your new repo using git clone, replacing https://github.com/me/example.git with your repo’s web URL:
35
+
36
+ ```bash
37
+ git clone --depth 1 https://github.com/me/example.git
38
+ ```
39
+
40
+ You can now edit your own versions of the site’s source files.
41
+
42
+ If you want to do SCSS edits and want to publish these, you need to install `PostCSS`
43
+
44
+ ```bash
45
+ npm install
46
+ ```
47
+
48
+ ## Running the website locally
49
+
50
+ Building and running the site locally requires a recent `extended` version of [Hugo](https://gohugo.io).
51
+ You can find out more about how to install Hugo for your environment in our
52
+ [Getting started](https://www.docsy.dev/docs/getting-started/#prerequisites-and-installation) guide.
53
+
54
+ Once you've made your working copy of the site repo, from the repo root folder, run:
55
+
56
+ ```bash
57
+ hugo server
58
+ ```
59
+
60
+ ## Running a container locally
61
+
62
+ You can run docsy-example inside a [Docker](https://docs.docker.com/)
63
+ container, the container runs with a volume bound to the `docsy-example`
64
+ folder. This approach doesn't require you to install any dependencies other
65
+ than [Docker Desktop](https://www.docker.com/products/docker-desktop) on
66
+ Windows and Mac, and [Docker Compose](https://docs.docker.com/compose/install/)
67
+ on Linux.
68
+
69
+ 1. Build the docker image
70
+
71
+ ```bash
72
+ docker-compose build
73
+ ```
74
+
75
+ 1. Run the built image
76
+
77
+ ```bash
78
+ docker-compose up
79
+ ```
80
+
81
+ > NOTE: You can run both commands at once with `docker-compose up --build`.
82
+
83
+ 1. Verify that the service is working.
84
+
85
+ Open your web browser and type `http://localhost:1313` in your navigation bar,
86
+ This opens a local instance of the docsy-example homepage. You can now make
87
+ changes to the docsy example and those changes will immediately show up in your
88
+ browser after you save.
89
+
90
+ ### Cleanup
91
+
92
+ To stop Docker Compose, on your terminal window, press **Ctrl + C**.
93
+
94
+ To remove the produced images run:
95
+
96
+ ```bash
97
+ docker-compose rm
98
+ ```
99
+ For more information see the [Docker Compose documentation][].
100
+
101
+ ## Using a local Docsy clone
102
+
103
+ Make sure your installed go version is `1.18` or higher.
104
+
105
+ Clone the latest version of the docsy theme into the parent folder of your project. The newly created repo should now reside in a sibling folder of your site's root folder.
106
+
107
+ ```shell
108
+ cd root-of-your-site
109
+ git clone --branch v0.7.2 https://github.com/google/docsy.git ../docsy
110
+ ```
111
+
112
+ Now run:
113
+
114
+ ```shell
115
+ HUGO_MODULE_WORKSPACE=docsy.work hugo server --ignoreVendorPaths "**"
116
+ ```
117
+
118
+ or, when using npm, prepend `local` to the script you want to invoke, e.g.:
119
+
120
+ ```shell
121
+ npm run local serve
122
+ ```
123
+
124
+ By using the `HUGO_MODULE_WORKSPACE` directive (either directly or via prefix `local` when using npm), the server now watches all files and directories inside the sibling directory `../docsy` , too. Any changes inside the local `docsy` theme clone are now immediately picked up (hot reload), you can instantly see the effect of your local edits.
125
+
126
+ In the command above, we used the environment variable `HUGO_MODULE_WORKSPACE` to tell hugo about the local workspace file `docsy.work`. Alternatively, you can declare the workspace file inside your settings file `hugo.toml`:
127
+
128
+ ```toml
129
+ [module]
130
+ workspace = "docsy.work"
131
+ ```
132
+
133
+ Your project's `hugo.toml` file already contains these lines, the directive for workspace assignment is commented out, however. Remove the two trailing comment characters '//' so that this line takes effect.
134
+
135
+ ## Troubleshooting
136
+
137
+ As you run the website locally, you may run into the following error:
138
+
139
+ ```console
140
+ $ hugo server
141
+ WARN 2023/06/27 16:59:06 Module "project" is not compatible with this Hugo version; run "hugo mod graph" for more information.
142
+ Start building sites …
143
+ hugo v0.101.0-466fa43c16709b4483689930a4f9ac8add5c9f66+extended windows/amd64 BuildDate=2022-06-16T07:09:16Z VendorInfo=gohugoio
144
+ Error: Error building site: "C:\Users\foo\path\to\docsy-example\content\en\_index.md:5:1": failed to extract shortcode: template for shortcode "blocks/cover" not found
145
+ Built in 27 ms
146
+ ```
147
+
148
+ This error occurs if you are running an outdated version of Hugo. As of docsy theme version `v0.7.0`, hugo version `0.110.0` or higher is required.
149
+ See this [section](https://www.docsy.dev/docs/get-started/docsy-as-module/installation-prerequisites/#install-hugo) of the user guide for instructions on how to install Hugo.
150
+
151
+ Or you may be confronted with the following error:
152
+
153
+ ```console
154
+ $ hugo server
155
+
156
+ INFO 2021/01/21 21:07:55 Using config file:
157
+ Building sites … INFO 2021/01/21 21:07:55 syncing static files to /
158
+ Built in 288 ms
159
+ Error: Error building site: TOCSS: failed to transform "scss/main.scss" (text/x-scss): resource "scss/scss/main.scss_9fadf33d895a46083cdd64396b57ef68" not found in file cache
160
+ ```
161
+
162
+ This error occurs if you have not installed the extended version of Hugo.
163
+ See this [section](https://www.docsy.dev/docs/get-started/docsy-as-module/installation-prerequisites/#install-hugo) of the user guide for instructions on how to install Hugo.
164
+
165
+ Or you may encounter the following error:
166
+
167
+ ```console
168
+ $ hugo server
169
+
170
+ Error: failed to download modules: binary with name "go" not found
171
+ ```
172
+
173
+ This error occurs if you have not installed the `go` programming language on your system.
174
+ See this [section](https://www.docsy.dev/docs/get-started/docsy-as-module/installation-prerequisites/#install-go-language) of the user guide for instructions on how to install `go`.
175
+
176
+
177
+ [alternate dashboard]: https://app.netlify.com/sites/goldydocs/deploys
178
+ [deploys]: https://app.netlify.com/sites/docsy-example/deploys
179
+ [Docsy user guide]: https://docsy.dev/docs
180
+ [Docsy]: https://github.com/google/docsy
181
+ [example.docsy.dev]: https://example.docsy.dev
182
+ [Hugo theme module]: https://gohugo.io/hugo-modules/use-modules/#use-a-module-for-a-theme
183
+ [Netlify]: https://netlify.com
184
+ [Docker Compose documentation]: https://docs.docker.com/compose/gettingstarted/
@@ -0,0 +1,6 @@
1
+ /*
2
+
3
+ Add styles or override variables from the theme here.
4
+
5
+ */
6
+
@@ -0,0 +1,15 @@
1
+ # THIS IS A TEST CONFIG ONLY!
2
+ # FOR THE CONFIGURATION OF YOUR SITE USE hugo.yaml.
3
+ #
4
+ # As of Docsy 0.7.0, Hugo 0.110.0 or later must be used.
5
+ #
6
+ # The sole purpose of this config file is to detect Hugo-module builds that use
7
+ # an older version of Hugo.
8
+ #
9
+ # DO NOT add any config parameters to this file. You can safely delete this file
10
+ # if your project is using the required Hugo version.
11
+
12
+ module:
13
+ hugoVersion:
14
+ extended: true
15
+ min: 0.110.0
@@ -0,0 +1,77 @@
1
+ ---
2
+ title: Goldydocs
3
+ ---
4
+
5
+ {{< blocks/cover title="Welcome to Goldydocs: A Docsy Example Project!" image_anchor="top" height="full" >}}
6
+ <a class="btn btn-lg btn-primary me-3 mb-4" href="/docs/">
7
+ Learn More <i class="fas fa-arrow-alt-circle-right ms-2"></i>
8
+ </a>
9
+ <a class="btn btn-lg btn-secondary me-3 mb-4" href="https://github.com/google/docsy-example">
10
+ Download <i class="fab fa-github ms-2 "></i>
11
+ </a>
12
+ <p class="lead mt-5">Porridge temperature assessment &mdash; in the cloud!</p>
13
+ {{< blocks/link-down color="info" >}}
14
+ {{< /blocks/cover >}}
15
+
16
+
17
+ {{% blocks/lead color="primary" %}}
18
+ Goldydocs provides a single web UI providing visibility into porridge
19
+ temperature, chair size, and bed softness metrics! You can even find out who's
20
+ been eating **your** porridge.
21
+
22
+ (Sadly, Goldydocs isn't a real project, but you can use this site as an example
23
+ to create your own real websites with [Docsy](https://docsy.dev))
24
+ {{% /blocks/lead %}}
25
+
26
+
27
+ {{% blocks/section color="dark" type="row" %}}
28
+ {{% blocks/feature icon="fa-lightbulb" title="New chair metrics!" %}}
29
+ The Goldydocs UI now shows chair size metrics by default.
30
+
31
+ Please follow this space for updates!
32
+ {{% /blocks/feature %}}
33
+
34
+
35
+ {{% blocks/feature icon="fab fa-github" title="Contributions welcome!" url="https://github.com/google/docsy-example" %}}
36
+ We do a [Pull Request](https://github.com/google/docsy-example/pulls) contributions workflow on **GitHub**. New users are always welcome!
37
+ {{% /blocks/feature %}}
38
+
39
+
40
+ {{% blocks/feature icon="fab fa-twitter" title="Follow us on Twitter!" url="https://twitter.com/docsydocs" %}}
41
+ For announcement of latest features etc.
42
+ {{% /blocks/feature %}}
43
+
44
+
45
+ {{% /blocks/section %}}
46
+
47
+
48
+ {{% blocks/section %}}
49
+ This is the second section
50
+ {.h1 .text-center}
51
+ {{% /blocks/section %}}
52
+
53
+
54
+ {{% blocks/section type="row" %}}
55
+
56
+ {{% blocks/feature icon="fab fa-app-store-ios" title="Download **from AppStore**" %}}
57
+ Get the Goldydocs app!
58
+ {{% /blocks/feature %}}
59
+
60
+ {{% blocks/feature icon="fab fa-github" title="Contributions welcome!"
61
+ url="https://github.com/google/docsy-example" %}}
62
+ We do a [Pull Request](https://github.com/google/docsy-example/pulls)
63
+ contributions workflow on **GitHub**. New users are always welcome!
64
+ {{% /blocks/feature %}}
65
+
66
+ {{% blocks/feature icon="fab fa-twitter" title="Follow us on Twitter!"
67
+ url="https://twitter.com/GoHugoIO" %}}
68
+ For announcement of latest features etc.
69
+ {{% /blocks/feature %}}
70
+
71
+ {{% /blocks/section %}}
72
+
73
+
74
+ {{% blocks/section %}}
75
+ This is the another section
76
+ {.h1 .text-center}
77
+ {{% /blocks/section %}}
@@ -0,0 +1,35 @@
1
+ ---
2
+ title: About Goldydocs
3
+ linkTitle: About
4
+ menu: {main: {weight: 10}}
5
+ ---
6
+
7
+ {{% blocks/cover title="About Goldydocs" image_anchor="bottom" height="auto" %}}
8
+
9
+ A sample site using the Docsy Hugo theme.
10
+ {.mt-5}
11
+
12
+ {{% /blocks/cover %}}
13
+
14
+ {{% blocks/lead %}}
15
+
16
+ Goldydocs is a sample site using the [Docsy](https://github.com/google/docsy)
17
+ Hugo theme that shows what it can do and provides you with a template site
18
+ structure. It’s designed for you to clone and edit as much as you like. See the
19
+ different sections of the documentation and site for more ideas.
20
+
21
+ {{% /blocks/lead %}}
22
+
23
+ {{% blocks/section %}}
24
+
25
+ # This is another section
26
+ {.text-center}
27
+
28
+ {{% /blocks/section %}}
29
+
30
+ {{% blocks/section %}}
31
+
32
+ # This is another section
33
+ {.text-center}
34
+
35
+ {{% /blocks/section %}}
@@ -0,0 +1,8 @@
1
+ ---
2
+ title: Blog
3
+ menu: {main: {weight: 30}}
4
+ ---
5
+
6
+ This is the **blog** section. It has two categories: News and Releases.
7
+
8
+ Files in these directories will be listed in reverse chronological order.
@@ -0,0 +1,4 @@
1
+ ---
2
+ title: News
3
+ weight: 20
4
+ ---
@@ -0,0 +1,48 @@
1
+ ---
2
+ date: 2018-10-06
3
+ title: Easy documentation with Docsy
4
+ linkTitle: Announcing Docsy
5
+ description: >
6
+ The Docsy Hugo theme lets project maintainers and contributors focus on content,
7
+ not on reinventing a website infrastructure from scratch
8
+ author: Riona MacNamara ([@rionam](https://twitter.com/bepsays))
9
+ resources:
10
+ - src: "**.{png,jpg}"
11
+ title: "Image #:counter"
12
+ params:
13
+ byline: "Photo: Riona MacNamara / CC-BY-CA"
14
+ ---
15
+
16
+ **This is a typical blog post that includes images.**
17
+
18
+ The front matter specifies the date of the blog post, its title, a short description that will be displayed on the blog landing page, and its author.
19
+
20
+ ## Including images
21
+
22
+ Here's an image (`featured-sunset-get.png`) that includes a byline and a caption.
23
+
24
+ {{< imgproc sunset Fill "600x300" >}}
25
+ Fetch and scale an image in the upcoming Hugo 0.43.
26
+ {{< /imgproc >}}
27
+
28
+ The front matter of this post specifies properties to be assigned to all image resources:
29
+
30
+ ```
31
+ resources:
32
+ - src: "**.{png,jpg}"
33
+ title: "Image #:counter"
34
+ params:
35
+ byline: "Photo: Riona MacNamara / CC-BY-CA"
36
+ ```
37
+
38
+ To include the image in a page, specify its details like this:
39
+
40
+ ```
41
+ {{< imgproc sunset Fill "600x300" >}}
42
+ Fetch and scale an image in the upcoming Hugo 0.43.
43
+ {{< /imgproc >}}
44
+ ```
45
+
46
+ The image will be rendered at the size and byline specified in the front matter.
47
+
48
+