solomax commented on code in PR #8:
URL: https://github.com/apache/openjpa-site/pull/8#discussion_r4495085850


##########
.gitignore:
##########
@@ -1,5 +1,100 @@
+# ============================================================================
+# Apache OpenJPA Project .gitignore
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+#     https://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+# ============================================================================
+
+# Dependencies lock files - keep these for reproducible builds
+package-lock.json
+
+# Node modules - always excluded
+node_modules/
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Build output directories - excluded from repo
+output/
+dist/
+
+# Generated static assets - NOT committed to repo, generated during build
+# These are created from npm packages during CI/CD build
+theme/apache/static/css/bootstrap.min.css

Review Comment:
   I've search a little bit
   It seems we can replace `pelican` with https://www.11ty.dev/
   And build the site with `maven-fronend-plugin`, this way we will have nodejs 
based site hosted near the manual
   Manual can be build as it is now and re-used 
   
   WDYT?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to