"pvt.k12.ca.us",
          "site.ac.jp",
          "site.ad.jp",
          "site.cc",
          "site.ed.jp",
          "site.ee",
          "site.fi",
          "site.fm",
          "site.geo.jp",
          "site.go.jp",
          "site.gr",
          "site.gr.jp",
          "site.jp",
          "site.lg.jp",
          "site.ma",
          "site.mk",
          "site.ne.jp",

          COMMIT_SHA: ${{ github.event.workflow_run.head_sha }}
          RUN_ID: ${{ github.run_id }}
      - name: Clean site
        run: |
          rm -rf ./site
          mkdir ./site
      - uses: actions/download-artifact@v5
        with:
          path: ./site/
          pattern: docs-site-*
          merge-multiple: true
          github-token: ${{ secrets.GITHUB_TOKEN }}

For the more details, see the implementation code in [GsaApiManager](/src/main/java/org/codelibs/fess/api/gsa/GsaApiManager.java).

### Google Site Search (GSS) / Google Custom Search (GSE)

[Fess Site Search](https://github.com/codelibs/fess-site-search) provides [scripts](https://fss-generator.codelibs.org/docs/manual) (see below) to help you migrate from GSS/CSE.
Using the, you can replace existing GSS/CSE JavaScript codes with:

    }

    /**
     * Gets the path to site-specific files directory.
     *
     * @param names the path components to append to the site directory
     * @return the Path object pointing to the site directory
     */
    public static Path getSitePath(final String... names) {
        return getPath("WEB-INF/", "site", names);
    }

    /**
     * Gets the path to plugin files directory.

*[Fess Site Search](https://github.com/codelibs/fess-site-search)* is a free alternative to [Google Site Search](https://enterprise.google.com/search/products/gss.html). For more details, see the [FSS JS Generator documentation](https://fss-generator.codelibs.org/docs/manual).

## Website

	<property name="suggest.dir" value="${basedir}/src/main/webapp/WEB-INF/env/suggest" />
	<property name="thumbnail.dir" value="${basedir}/src/main/webapp/WEB-INF/env/thumbnail" />
	<property name="site.dir" value="${basedir}/src/main/webapp/WEB-INF/site" />
	<property name="kopf.branch" value="fess-15" />

	<!-- Maven Repository -->
	<property name="maven.snapshot.repo.url" value="https://central.sonatype.com/repository/maven-snapshots" />

*[Fess Site Search](https://github.com/codelibs/fess-site-search)* est une alternative gratuite à [Google Site Search](https://enterprise.google.com/search/products/gss.html). Pour plus de détails, consultez la [documentation FSS JS Generator](https://fss-generator.codelibs.org/docs/manual).

## Site Web

[fess.codelibs.org](https://fess.codelibs.org/)

## Problèmes/Questions

 * triggers all preceding phases, ensuring that each step of the build process is
 * completed in the correct order. The three main lifecycles in Maven are
 * {@link #DEFAULT default}, {@link #CLEAN clean}, and {@link #SITE site}, with the
 * {@code default} lifecycle being the most commonly used for project builds.
 *
 * @since 4.0.0
 */
@Experimental
@Immutable
public interface Lifecycle extends ExtensibleEnum {

cat README.md | grep -v 'project website' > docs/index.md
cp CHANGELOG.md docs/changelogs/changelog.md
cp CONTRIBUTING.md docs/contribute/contributing.md

# Build the site locally

        <executions>
          <execution>
            <id>attach-docs</id>
          </execution>
          <execution>
            <id>generate-javadoc-site-report</id>
            <phase>site</phase>
            <goals><goal>javadoc</goal></goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>