LPS-179609-staticContent-sample #109
Conversation
|
To conserve resources, the PR Tester does not automatically run for every pull. If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed. If your pull was never tested, comment "ci:test" to run the PR Tester for this pull. |
|
@gamerson That's really creative. Some other ideas I had were maybe to make an example that actually generated javadocs or hosted the output of a static site generator. I guess the question is where the content would come from, if it's generated through the gradle task like you did or from some other process. |
|
Yes I think maybe a popular static site generator is a good idea. Do you
have suggestions of a common one that could be wired up pretty easily? Is
there one based on a frontend framework that we could invoke with
package.json build script?
…On Tue, Mar 28, 2023 at 12:00 PM Allen Ziegenfus ***@***.***> wrote:
@gamerson <https://github.com/gamerson> That's really creative.
Some other ideas I had were maybe to make an example that actually
generated javadocs or hosted the output of a static site generator. I guess
the question is where the content would come from, if it's generated
through the gradle task like you did or from some other process.
—
Reply to this email directly, view it on GitHub
<#109 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAERKFKGXE54AMMD3ZMXZVDW6MKMBANCNFSM6AAAAAAWKY44ZA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Greg Amerson
Liferay Cloud. liferay.com
|
|
Here's one I did with astro, a static site generator that uses vite for it's build It has some unusual file extensions so not sure if Brian would merge that. |
gamerson
force-pushed
the
LPS-179609-staticContent-sample
branch
from
85d5083
to
42e0d79
Compare
No description provided.