Removing bad urls take3 (#4521)

* Removed additional bad reply URLs

* Fixed a few links

* Fixed blog redirect URLs to local host

* Added linter to broken links

* Fixed additional paths and hardened CI

* Relaxed lint rules

* Improved lint to focus on markdown and fixed images in the developer guide

* Fixed a few broken images and links

* Fixed some paths

* Fixed HTML urls

* Replaced linters with standard web based linters

* Switched to faster linter

* Fixed contributing path

Author: shai-almog

.github/workflows/website-docs.yml

@@ -72,6 +72,35 @@ jobs:
           WEBSITE_INCLUDE_JAVADOCS: "true"
           WEBSITE_INCLUDE_DEVGUIDE: "true"
 
+      - name: Validate internal links and images
+        uses: lycheeverse/lychee-action@v2
+        with:
+          args: >-
+            --offline
+            --no-progress
+            docs/website/public/**/*.html
+
+      - name: Reject absolute codenameone.com links
+        run: |
+          set -euo pipefail
+          report="docs/website/reports/disallowed-codenameone-links.txt"
+          mkdir -p "$(dirname "$report")"
+          rg -n --no-heading -S '\]\((https?:)?//(www\.)?codenameone\.com([/:?#)]|$)|<https?://(www\.)?codenameone\.com([/:?#>]|$)|(href|src)=["'"'"']https?://(www\.)?codenameone\.com([/:?#]|$)' \
+            docs/website/content docs/website/layouts docs/website/static > "$report" || true
+          if [ -s "$report" ]; then
+            echo "Disallowed absolute codenameone.com links found (use relative URLs or non-www subdomains):" >&2
+            sed -n '1,200p' "$report" >&2
+            exit 1
+          fi
+
+      - name: Upload codenameone link policy report
+        if: ${{ always() }}
+        uses: actions/upload-artifact@v4
+        with:
+          name: codenameone-link-policy-report
+          path: docs/website/reports/disallowed-codenameone-links.txt
+          if-no-files-found: ignore
+
       - name: Validate OTA skin output
         run: |
           set -euo pipefail

docs/developer-guide/About-This-Guide.asciidoc

@@ -7,7 +7,7 @@ This developer guide is sourced directly from the `docs` directory of the https:
 
 === How to Contribute Updates
 
-To contribute updates, clone the repository, create a feature branch, and edit the AsciiDoc files in `docs/developer-guide`. Follow the steps in the link:../../CONTRIBUTING.md[CONTRIBUTING guidelines] to open a GitHub pull request (PR) instead of using the deprecated community wiki. Each PR is automatically linted and built by continuous integration, then reviewed by a maintainer before it is merged. Once merged, the content is rendered to the web manual at https://www.codenameone.com/manual/ and to the downloadable PDF at https://www.codenameone.com/files/developer-guide.pdf[https://www.codenameone.com/files/developer-guide.pdf]. Periodically, major revisions are collected for print-on-demand distribution.
+To contribute updates, clone the repository, create a feature branch, and edit the AsciiDoc files in `docs/developer-guide`. Follow the steps in the link:https://github.com/codenameone/CodenameOne/blob/master/docs/website/CONTRIBUTING.md[CONTRIBUTING guidelines] to open a GitHub pull request (PR) instead of using the deprecated community wiki. Each PR is automatically linted and built by continuous integration, then reviewed by a maintainer before it is merged. Once merged, the content is rendered to the web manual at https://www.codenameone.com/manual/ and to the downloadable PDF at https://www.codenameone.com/files/developer-guide.pdf[https://www.codenameone.com/files/developer-guide.pdf]. Periodically, major revisions are collected for print-on-demand distribution.
 
 While this guide focuses on tutorial and conceptual material, the complete API reference remains available in the https://www.codenameone.com/javadoc/[Codename One JavaDoc]. The source code for the framework and this manual lives alongside each other in Git, so improvements to documentation and code can evolve together through the same contribution workflow.
 

docs/website/content/about-us.md

@@ -40,7 +40,7 @@ With the free version, there is a JAR size limit of 1 - 8.5mb. Notice that this
 
 The free tier allows you to use your generated apps commercially and place have no restrictions on them. There are no nag screens or license limitations!
 
-There are many additional benefits and additional features you can get in the paid plans, see the [pricing details here](https://www.codenameone.com/pricing.html).
+There are many additional benefits and additional features you can get in the paid plans, see the [pricing details here](/pricing/).
 
 ### Where can I learn more?
 

docs/website/content/advanced-build.md

@@ -18,4 +18,4 @@ Build hints/arguments allow us to manipulate the build process on the build serv
 
 When sending a build to the server you can provide additional parameters to the build which will be incorporated into the build process on the server to hint on multiple different build time options.You can do this by right clicking the Codename One project and entering the project properties. There you will find the "Build Hints" tab in which you can just type the arguments and the appropriate values from the list below.
 
-We removed this page since it duplicates content from the developer guide and we should probably maintain only one **authoritative** list. The up to date list is [here](https://www.codenameone.com/manual/advanced-topics.html#_sending_arguments_to_the_build_server).
+We removed this page since it duplicates content from the developer guide and we should probably maintain only one **authoritative** list. The up to date list is [here](/manual/advanced-topics/#_sending_arguments_to_the_build_server).

docs/website/content/blog/3-image-tools-for-app-marketing.md

@@ -72,13 +72,13 @@ Good promotional material is no substitute for good app design, but it’s a ste
 _This post was automatically migrated from the legacy Codename One blog. The original comments are preserved below for historical context. New discussion happens in the Discussion section._
 
 
-### **Chris Moore** — May 30, 2019 at 7:49 am ([permalink](https://www.codenameone.com/blog/3-image-tools-for-app-marketing.html#comment-24041))
+### **Chris Moore** — May 30, 2019 at 7:49 am ([permalink](/blog/3-image-tools-for-app-marketing/#comment-24041))
 
 > Hey Shai!
 >
 > Nice tips. I wonder whether you’ve tried Promomatic ([https://www.promomatic.com/)](<https://www.promomatic.com/>)) for building app screenshots instead of AppLaunchPad? Super easy to use and cost effective when building for the app store launch. Found them on Product Hunt a few months back.
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2F3-image-tools-for-app-marketing.html)
+
 
 ---
 

docs/website/content/blog/5-tips-for-gamifying-your-mobile-app.md

@@ -82,44 +82,44 @@ Notice: This post was automatically converted using a script from an older blogg
 _This post was automatically migrated from the legacy Codename One blog. The original comments are preserved below for historical context. New discussion happens in the Discussion section._
 
 
-### **Anonymous** — March 24, 2013 at 2:56 pm ([permalink](https://www.codenameone.com/blog/5-tips-for-gamifying-your-mobile-app.html#comment-24251))
+### **Anonymous** — March 24, 2013 at 2:56 pm ([permalink](/blog/5-tips-for-gamifying-your-mobile-app/#comment-24251))
 
 > Anonymous says:
 >
 > Great post guys! 
 >
 > Keep up the good work!
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2F5-tips-for-gamifying-your-mobile-app.html)
 
 
-### **Anonymous** — March 24, 2013 at 4:20 pm ([permalink](https://www.codenameone.com/blog/5-tips-for-gamifying-your-mobile-app.html#comment-21425))
+
+### **Anonymous** — March 24, 2013 at 4:20 pm ([permalink](/blog/5-tips-for-gamifying-your-mobile-app/#comment-21425))
 
 > Anonymous says:
 >
 > Very cool. Thanks for the post!
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2F5-tips-for-gamifying-your-mobile-app.html)
 
 
-### **Anonymous** — November 13, 2013 at 10:25 am ([permalink](https://www.codenameone.com/blog/5-tips-for-gamifying-your-mobile-app.html#comment-21681))
+
+### **Anonymous** — November 13, 2013 at 10:25 am ([permalink](/blog/5-tips-for-gamifying-your-mobile-app/#comment-21681))
 
 > Anonymous says:
 >
 > Thanks for this post. Do you have any examples of utility apps that do this well? Eg, Telecoms, banking, power etc
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2F5-tips-for-gamifying-your-mobile-app.html)
 
 
-### **Balbir singh** — February 7, 2018 at 10:16 am ([permalink](https://www.codenameone.com/blog/5-tips-for-gamifying-your-mobile-app.html#comment-23869))
+
+### **Balbir singh** — February 7, 2018 at 10:16 am ([permalink](/blog/5-tips-for-gamifying-your-mobile-app/#comment-23869))
 
 > Balbir singh says:
 >
 > thanks for sharing this informative post about mobile app.  
 > [http://www.nanoarchsoftware…](<http://www.nanoarchsoftware.com/Services/mobile-application>)  
 > .
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2F5-tips-for-gamifying-your-mobile-app.html)
+
 
 ---
 

docs/website/content/blog/64-bit-oss-vm.md

@@ -56,22 +56,22 @@ Notice: This post was automatically converted using a script from an older blogg
 _This post was automatically migrated from the legacy Codename One blog. The original comments are preserved below for historical context. New discussion happens in the Discussion section._
 
 
-### **Anonymous** — November 10, 2014 at 8:13 am ([permalink](https://www.codenameone.com/blog/64-bit-oss-vm.html#comment-21907))
+### **Anonymous** — November 10, 2014 at 8:13 am ([permalink](/blog/64-bit-oss-vm/#comment-21907))
 
 > Anonymous says:
 >
 > I got an error when I tried to build with the new vm
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2F64-bit-oss-vm.html)
 
 
-### **Anonymous** — November 26, 2014 at 8:14 am ([permalink](https://www.codenameone.com/blog/64-bit-oss-vm.html#comment-22175))
+
+### **Anonymous** — November 26, 2014 at 8:14 am ([permalink](/blog/64-bit-oss-vm/#comment-22175))
 
 > Anonymous says:
 >
 > Can you post on the forum with more details e.g. build error log?
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2F64-bit-oss-vm.html)
+
 
 ---
 

docs/website/content/blog/a-junior-software-developers-journey-at-codename-one.md

@@ -35,9 +35,9 @@ I barely wrote 100 lines of code (not the best ones). Even worst than that, I fe
 
 ### What Really Helped?
 
-I found the [Codename One developer guide](https://www.codenameone.com/developer-guide.html) to be the best learning resource. It’s great for learning your way around the tool and understanding its components. 
+I found the [Codename One developer guide](/developer-guide/) to be the best learning resource. It’s great for learning your way around the tool and understanding its components. 
 
-In the [How Do I](https://www.codenameone.com/how-do-i.html) section I found some very helpful video tutorials that also helped a lot with learning common use cases, like the [Layout basics](https://www.codenameone.com/how_di_i/how-do-i-positioning-components-using-layout-managers.html) video, and the [How to convert a PSD Design into a Native Mobile App](https://www.codenameone.com/video/how-to-convert-a-psd-design-into-a-native-mobile-app.html). 
+In the [How Do I](/how-do-i/) section I found some very helpful video tutorials that also helped a lot with learning common use cases, like the [Layout basics](/how_di_i/how-do-i-positioning-components-using-layout-managers/) video, and the [How to convert a PSD Design into a Native Mobile App](/video/how-to-convert-a-psd-design-into-a-native-mobile-app/). 
 
 At that point, I was comfortable enough with a good foundation level knowledge and my work seemed much smoother and stress-free. 
 
@@ -63,29 +63,21 @@ And even better, the app contains links to the [source code](https://github.com/
 
 But more importantly, users can see and learn about the application structure and how it needs to be written.
 
-![](https://www.codenameone.com/wp-content/uploads/2020/12/kitchen-sink-screenshot_1-169x300.png)
 
-![](https://www.codenameone.com/wp-content/uploads/2020/12/kitchen-sink-screenshot_2-169x300.png)
-
-![](https://www.codenameone.com/wp-content/uploads/2020/12/kitchen-sink-screenshot_3-169x300.png)
-
-![](https://www.codenameone.com/wp-content/uploads/2020/12/kitchen-sink-screenshot_4-169x300.png)
-
-![](https://www.codenameone.com/wp-content/uploads/2020/12/kitchen-sink-screenshot_5-169x300.png)
 ---
 
 ## Archived Comments
 
 _This post was automatically migrated from the legacy Codename One blog. The original comments are preserved below for historical context. New discussion happens in the Discussion section._
 
 
-### **[email protected]** — December 26, 2020 at 2:56 pm ([permalink](https://www.codenameone.com/blog/a-junior-software-developers-journey-at-codename-one.html#comment-24368))
+### **[email protected]** — December 26, 2020 at 2:56 pm ([permalink](/blog/a-junior-software-developers-journey-at-codename-one/#comment-24368))
 
 > [[email protected]](/cdn-cgi/l/email-protection) says:
 >
 > Looking forward to having an extra hand on CN1, Sergey. Welcome 🙂
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2Fa-junior-software-developers-journey-at-codename-one.html)
+
 
 ---
 

docs/website/content/blog/a-new-idea.md

@@ -103,7 +103,7 @@ by copying them to the new plugin. Be sure to let us know immediately if you run
 _This post was automatically migrated from the legacy Codename One blog. The original comments are preserved below for historical context. New discussion happens in the Discussion section._
 
 
-### **Therk** — April 13, 2016 at 11:42 pm ([permalink](https://www.codenameone.com/blog/a-new-idea.html#comment-22656))
+### **Therk** — April 13, 2016 at 11:42 pm ([permalink](/blog/a-new-idea/#comment-22656))
 
 > Thank you for improving the plugin. It is more intuitive even though it may not be consistent with other IntelliJ plugins. Unfortunately, I started to get a NullPointerException when setting up the Run configuration for a new sample application.  
 > I am not sure the best way to report such issues, but the stack trace is:
@@ -201,10 +201,10 @@ _This post was automatically migrated from the legacy Codename One blog. The ori
 > at java.awt.EventDispatchThread.pumpEvents([EventDispatchThread.java](<http://EventDispatchThread.java>):93)  
 > at [java.awt.EventDispatchThrea…](<http://java.awt.EventDispatchThread.run)([EventDispatchThread.java](http://EventDispatchThread.java)>:82)
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2Fa-new-idea.html)
 
 
-### **Therk** — April 14, 2016 at 12:21 am ([permalink](https://www.codenameone.com/blog/a-new-idea.html#comment-22484))
+
+### **Therk** — April 14, 2016 at 12:21 am ([permalink](/blog/a-new-idea/#comment-22484))
 
 > A few suggestion on improving the IDEA plugin:  
 > 1\. In the Codename One Preferences, tabbing between fields does not seem to work, requiring a mouse click into next fields. For example in the Login or iOS Certificate Wizard.  
@@ -215,19 +215,19 @@ _This post was automatically migrated from the legacy Codename One blog. The ori
 > 6\. It should allow to select existing App ID and name for an application.  
 > 7\. Under Global Preferences and iOS Certificate Wizard, App ID and name should probably not be required, as I think Global Preferences are to be shared between other CodenameOne application.
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2Fa-new-idea.html)
 
 
-### **Shai Almog** — April 14, 2016 at 2:36 am ([permalink](https://www.codenameone.com/blog/a-new-idea.html#comment-22585))
+
+### **Shai Almog** — April 14, 2016 at 2:36 am ([permalink](/blog/a-new-idea/#comment-22585))
 
 > Thanks!  
 > Those are great issues/RFE’s.  
 > The right place to file them so they don’t get lost under our workload is the issue tracker at [http://github.com/codenameo…](<http://github.com/codenameone/CodenameOne/issues/>)
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2Fa-new-idea.html)
 
 
-### **Shai Almog** — April 14, 2016 at 8:08 am ([permalink](https://www.codenameone.com/blog/a-new-idea.html#comment-22766))
+
+### **Shai Almog** — April 14, 2016 at 8:08 am ([permalink](/blog/a-new-idea/#comment-22766))
 
 > Shai Almog says:
 >
@@ -237,44 +237,44 @@ _This post was automatically migrated from the legacy Codename One blog. The ori
 > 6\. It should have the existing app id from your app which must match the package name of your project.  
 > 7\. The global version of the wizard should allow you to customize the app id as it can be a * certificate but it can reside anywhere e.g. I can make a com.mycompany.* or just plain * as my default. This matters to the provisioning profile.
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2Fa-new-idea.html)
 
 
-### **Shai Almog** — April 14, 2016 at 8:14 am ([permalink](https://www.codenameone.com/blog/a-new-idea.html#comment-22774))
+
+### **Shai Almog** — April 14, 2016 at 8:14 am ([permalink](/blog/a-new-idea/#comment-22774))
 
 > Shai Almog says:
 >
 > How do you set the run configuration?  
 > I see the problem but I can’t reproduce it to make sure the fix is correct.
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2Fa-new-idea.html)
 
 
-### **Eric Coolman** — April 28, 2016 at 9:50 pm ([permalink](https://www.codenameone.com/blog/a-new-idea.html#comment-22466))
+
+### **Eric Coolman** — April 28, 2016 at 9:50 pm ([permalink](/blog/a-new-idea/#comment-22466))
 
 > Eric Coolman says:
 >
 > Great work, and thanks! 🙂
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2Fa-new-idea.html)
 
 
-### **James van Kessel** — May 20, 2016 at 3:56 pm ([permalink](https://www.codenameone.com/blog/a-new-idea.html#comment-22606))
+
+### **James van Kessel** — May 20, 2016 at 3:56 pm ([permalink](/blog/a-new-idea/#comment-22606))
 
 > James van Kessel says:
 >
 > Hi Shai, For someone with an existing project, are there any warnings or cautions you’d give someone still using an older CN1 plugin (i am still on 3.1) before clicking “update Plugin”?
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2Fa-new-idea.html)
 
 
-### **Shai Almog** — May 21, 2016 at 3:51 am ([permalink](https://www.codenameone.com/blog/a-new-idea.html#comment-22611))
+
+### **Shai Almog** — May 21, 2016 at 3:51 am ([permalink](/blog/a-new-idea/#comment-22611))
 
 > Shai Almog says:
 >
 > If you update to the latest it will be the new plugin and there is no warning. Notice that on the plugin page at IDEA you can always download the older versions of the plugin if you need it while we fix a potential issue you might run into.
 >
-> [Log in to Reply](https://www.codenameone.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.codenameone.com%2Fblog%2Fa-new-idea.html)
+
 
 ---