SEO: A Java Frontend Without JavaScript - #1109
Open
MatthewHawkins wants to merge 4 commits into
Open
MatthewHawkins wants to merge 4 commits into
MatthewHawkins wants to merge 4 commits into
Conversation
MatthewHawkins
requested review from
EHandtkeBasis,
bbrennanbasis,
gosteenBASIS,
hyyan and
laurenic0l
as code owners
August 19, 2026 21:54
hyyan
approved these changes
Aug 25, 2026
hyyan
left a comment
Member
There was a problem hiding this comment.
Choose a better cover image and get the post queued for LinkedIn as well please.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the
java-frontend-without-javascriptSEO spoke post to the blog.Post summary
Title: A Java Frontend Without JavaScript
Slug:
java-frontend-without-javascriptPrimary keyword:
java frontend without javascriptCluster: framework-decision (spoke of spring-boot-frontend-java pillar)
Tier: 1
Word count: ~1,800 (prose only — no code blocks)
Content
A decision-walkthrough post covering what a Java-only frontend costs and gains. Contrasts SPA+REST, HTMX+server HTML, and Java imperative UI as three paradigms; then covers what the team gave up (JS ecosystem access, React hire pipeline, edge cacheability), what they got (one Maven build, no JSON wire, one debugger), where a small
executeJavascriptbridge is appropriate, and when the answer is still "yes, use JavaScript." References the time-tracker from the spring-boot-frontend-java pillar as the concrete artifact.Snippet sources
This post contains no webforJ code blocks. All inline code references use standard Java identifiers (
mvn package,package.json, etc.) or backtick-formatted doc references. No STYLE.md rule #2 tracking required.Files changed
docs/blog/SEO-posts/2026-08-19-java-frontend-without-javascript/index.md— postdocs/blog/SEO-posts/2026-08-19-java-frontend-without-javascript/cover.png— cover imageGenerated by Claude Code