Skip to content

SEO: A Java Frontend Without JavaScript - #1109

Open
MatthewHawkins wants to merge 4 commits into
mainfrom
seo/java-frontend-without-javascript
Open

MatthewHawkins wants to merge 4 commits into
mainfrom
seo/java-frontend-without-javascript

Conversation

@MatthewHawkins

Copy link
Copy Markdown
Member

Adds the java-frontend-without-javascript SEO spoke post to the blog.

Post summary

Title: A Java Frontend Without JavaScript
Slug: java-frontend-without-javascript
Primary keyword: java frontend without javascript
Cluster: 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 executeJavascript bridge 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 — post
  • docs/blog/SEO-posts/2026-08-19-java-frontend-without-javascript/cover.png — cover image

Generated by Claude Code

@hyyan hyyan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a better cover image and get the post queued for LinkedIn as well please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants