slachiewicz opened a new pull request, #83:
URL: https://github.com/apache/maven-scripting-plugin/pull/83

   ### What
   
   `src/site/fml/faq.fml` has never contained a single `<faq>` entry since it 
was added in
   2021 — it is a licence header wrapped around an empty `<faqs>` element. It 
renders
   `faq.html` as nothing but the heading:
   
   ```html
   <main id="bodyColumn" class="span10">
   <section><a id="top"></a>
   <h1>Frequently Asked Questions</h1></section>        </main>
   ```
   
   It is also the only `faq.fml` across the ~42 in the Maven estate that its 
own `site.xml`
   does not put in a menu, so the page is reachable only from one sentence in 
`index.md.vm`
   — archetype boilerplate inviting the reader to consult a FAQ that does not 
exist. This PR
   drops that sentence too, keeping the mailing-list pointer beside it.
   
   ### Worth stating plainly
   
   This removes `faq.html` from the published site, so that URL will start 
returning 404. The
   page has no content to deep-link to and no menu entry pointing at it, so the 
risk looks
   negligible — but it is a URL removal and reviewers should weigh it rather 
than discover it.
   
   ### Verification
   
   Built the site with `mvn site` before and after:
   
   - `faq.html` is the only page that disappears; the remaining 20 build clean
   - `git grep -i faq` returns nothing afterwards — no dangling reference is 
left
   - the reworded paragraph on `index.html` renders correctly
   
   ### Context
   
   This came out of a survey of every remaining `.fml` file in the Maven 
estate. The wider
   conclusion was that FML is alive and well — `doxia-module-fml` is one of 
only five modules
   Doxia 2.x kept, and Doxia's own reference page still lists it as supported — 
so **no
   estate-wide FML migration is proposed**. This one file is a deletion 
candidate purely
   because it is empty and orphaned, not because of its format.
   
   <sub>Drafted with Claude — please verify</sub>


-- 
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