No Maven site structure (src/site/) for project documentation and site descriptor

## Problem
Project lacks Maven site structure (`src/site/` directory) and site descriptor (`site.xml`). This prevents creating a professional project website with documentation, reports, and navigation.

## Current State

```bash
ls src/site/
# No src/site directory

find . -name "site.xml"
# No site.xml descriptor
```

## Impact

### Cannot Customize Maven Site
- Generated site uses default layout
- No custom navigation
- No project branding
- No additional documentation pages

### Missing Professional Website
**Similar projects have**:
- Project overview page
- Getting started guide
- API documentation (JavaDoc)
- Architecture documentation
- Contributing guidelines
- Change history

**jcommons currently**: Only default Maven-generated pages

### No Central Documentation Hub
Documentation scattered:
- README.md (GitHub)
- CONTRIBUTING.md (GitHub)
- CHANGELOG.md (GitHub)
- JavaDoc (needs #151 - not generated)
- Quality reports (needs #197 - no reporting section)

**No unified site** bringing it all together

## Recommended Solution

### Create src/site Structure

```
src/site/
├── site.xml           # Site descriptor (navigation, skin)
├── markdown/          # Markdown pages (optional)
│   ├── index.md       # Home page
│   ├── getting-started.md
│   └── architecture.md
├── resources/         # Static resources
│   ├── css/
│   │   └── site.css   # Custom styling
│   └── images/
│       └── logo.png
└── apt/               # APT format pages (optional)
```

### Example site.xml

```xml
<?xml version="1.0" encoding="UTF-8"?>
<project name="jcommons">
    <bannerLeft>
        <name>jcommons</name>
        <src>images/logo.png</src>
        <href>https://github.com/FlossWare/jcommons</href>
    </bannerLeft>

    <publishDate position="right"/>
    <version position="right"/>

    <body>
        <links>
            <item name="GitHub" href="https://github.com/FlossWare/jcommons"/>
            <item name="Issues" href="https://github.com/FlossWare/jcommons/issues"/>
            <item name="Solenopsis" href="https://github.com/solenopsis"/>
        </links>

        <menu name="Overview">
            <item name="Introduction" href="index.html"/>
            <item name="Getting Started" href="getting-started.html"/>
            <item name="Architecture" href="architecture.html"/>
        </menu>

        <menu name="Documentation">
            <item name="JavaDoc" href="apidocs/index.html"/>
            <item name="Source Xref" href="xref/index.html"/>
        </menu>

        <menu name="Quality Reports">
            <item name="Code Coverage" href="jacoco/index.html"/>
            <item name="SpotBugs" href="spotbugs.html"/>
            <item name="PMD" href="pmd.html"/>
            <item name="Checkstyle" href="checkstyle.html"/>
        </menu>

        <menu name="Project Info">
            <item name="Dependencies" href="dependencies.html"/>
            <item name="Team" href="team.html"/>
            <item name="License" href="license.html"/>
            <item name="SCM" href="scm.html"/>
        </menu>

        <menu ref="reports"/>
    </body>

    <skin>
        <groupId>org.apache.maven.skins</groupId>
        <artifactId>maven-fluido-skin</artifactId>
        <version>2.0.0-M10</version>
    </skin>
</project>
```

### Example index.md (Home Page)

```markdown
# jcommons

Foundation utilities for the [Solenopsis](https://github.com/solenopsis) 
Salesforce SOAP framework.

## Features

* **SOAP Utilities**: Configure Apache CXF clients for Salesforce
* **String Utilities**: Validation, encoding, concatenation
* **File Utilities**: Safe I/O operations
* **Array Utilities**: Validation and manipulation
* **Logging Utilities**: Enhanced logging with varargs

## Quality Standards

* 93% code coverage (JaCoCo enforced)
* Zero SpotBugs violations
* Google Java Style Guide (Checkstyle)
* PMD code quality rules
* 80% mutation coverage (PIT)

## Quick Start

[Getting Started Guide](getting-started.html)

## Project Information

* [JavaDoc](apidocs/index.html)
* [Code Coverage](jacoco/index.html)
* [Dependencies](dependencies.html)
```

## Benefits

### Professional Project Site
```bash
mvn site
# Generates: target/site/index.html
# Professional layout with navigation
# Custom branding
# Integrated reports
```

### Centralized Documentation
- All docs in one place
- Consistent navigation
- Cross-linked content
- Professional appearance

### Deployment to GitHub Pages
```yaml
# .github/workflows/main.yml
- name: Generate Maven Site
  run: mvn site site:stage

- name: Deploy to GitHub Pages
  uses: peaceiris/actions-gh-pages@v4
  with:
    publish_dir: ./target/staging
    destination_dir: site
```

**Result**: https://flossware.github.io/jcommons/site/

### Better Discoverability
- Search engines index site
- Users find documentation easily
- Professional image
- Showcases quality metrics

## Comparison with Similar Projects

### Apache Commons Lang
- ✅ Full Maven site structure
- ✅ Custom site.xml
- Published: https://commons.apache.org/proper/commons-lang/

### Google Guava
- ✅ Maven site with navigation
- ✅ Integrated JavaDoc and reports

### jcommons (Current)
- ❌ No src/site/ directory
- ❌ No site descriptor
- ❌ Default Maven layout only

## Implementation Steps

### Phase 1: Basic Structure
1. Create `src/site/site.xml` with navigation
2. Create `src/site/markdown/index.md` (home page)
3. Test: `mvn site`
4. Review: `target/site/index.html`

### Phase 2: Additional Pages
1. getting-started.md (installation, usage)
2. architecture.md (design overview)
3. migration-v2.md (v2.0 migration guide)

### Phase 3: Integration
1. Requires #197 (reporting section) for quality reports
2. Requires #151 (JavaDoc plugin) for API docs
3. Link to GitHub (README, CONTRIBUTING, CHANGELOG)

### Phase 4: Deployment (Optional)
1. Configure GitHub Pages deployment
2. Update README with site link
3. Automated deployment on release

## Minimal Implementation

**If full site too much work**, at minimum create:

```
src/site/
└── site.xml    # Just navigation for existing reports
```

This provides:
- Custom navigation
- Project branding
- Links to GitHub
- No additional pages needed

## Related
- Part of production quality audit
- #197: Missing reporting section (needed for reports in site)
- #151: Missing JavaDoc plugin execution (needed for API docs in site)
- Improves project professionalism
- Centralized documentation

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

No Maven site structure (src/site/) for project documentation and site descriptor #199

Problem

Current State

Impact

Cannot Customize Maven Site

Missing Professional Website

No Central Documentation Hub

Recommended Solution

Create src/site Structure

Example site.xml

Example index.md (Home Page)

Benefits

Professional Project Site

Centralized Documentation

Deployment to GitHub Pages

Better Discoverability

Comparison with Similar Projects

Apache Commons Lang

Google Guava

jcommons (Current)

Implementation Steps

Phase 1: Basic Structure

Phase 2: Additional Pages

Phase 3: Integration

Phase 4: Deployment (Optional)

Minimal Implementation

Related

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

No Maven site structure (src/site/) for project documentation and site descriptor #199

Description

Problem

Current State

Impact

Cannot Customize Maven Site

Missing Professional Website

No Central Documentation Hub

Recommended Solution

Create src/site Structure

Example site.xml

Example index.md (Home Page)

Benefits

Professional Project Site

Centralized Documentation

Deployment to GitHub Pages

Better Discoverability

Comparison with Similar Projects

Apache Commons Lang

Google Guava

jcommons (Current)

Implementation Steps

Phase 1: Basic Structure

Phase 2: Additional Pages

Phase 3: Integration

Phase 4: Deployment (Optional)

Minimal Implementation

Related

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions