Re: Proposal: JSON + Markdown as a Viability Study for Sustainable Web Development

Hello Marlon,

I've got a few concerns regarding your proposal.


  *
Markdown dictates basic structure but it doesn't provide anything of use until it is compiled. For example, the result has to be compiled to HTML to provide semantic value to users (the stylistic choices as well as the interpretation). So my question to you, is this something to be done by browsers? By JavaScript? Why not just use HTML that doesn't have the additional compilation overhead in addition to the standard rendering that will already take place. Also: HTML is accessible by default, something that Markdown lacks, this could in some instances result in compliance issues.
  *
JSON use within websites and applications currently requires a scripting language. This may be a natural requirement of many apps but the web is also filled with pages where the need for scripting is not and should not be a prerequisite (as there are many reasons why JavaScript may be disabled or otherwise unavailable to end-users) [source<https://adamsilver.io/blog/javascript-isnt-always-available-and-its-not-the-users-fault/>, another<https://www.kryogenix.org/code/browser/everyonehasjs.html>]. This is not sustainable behavior as many individuals in developing nations do not have devices to handle JavaScript heavy/dependent pages (source<https://infrequently.org/series/performance-inequality/>).
  *
Even if browsers were to adopt JSON+MD as an alternative to traditional HTML, this would be problematic to the backward compatible nature of the web. Web standards advocates have always worked by the ethos of "not breaking what has come before<https://developer.mozilla.org/en-US/docs/Learn_web_development/Getting_started/Web_standards/The_web_standards_model#dont_break_the_web>" to ensure old websites and those using older devices can still continue to function. If websites and apps were built using such a format and only compatible (aka newer) devices were capable of viewing it, this would be a breaking change.

That being said, there is nothing to prevent anyone creating a JavaScript library that interprets JSON and Markdown, transforms it into HTML, and compare the rendering performance to existing browser performance speeds, if you wished to benchmark the numbers and address implementation concerns.

Regards,
Alexander Dawson

Note: JSON is already a web standard (EMCA<https://ecma-international.org/publications-and-standards/standards/ecma-404/>) as a data interchange format, so I don't believe it needs to be re-standardized / updated for the sake of including Markdown code within it.

________________________________
From: Marlon rel. comercial <marlonla72@gmail.com>
Sent: 03 May 2025 23:09
To: public-sustainableweb@w3.org <public-sustainableweb@w3.org>
Subject: Proposal: JSON + Markdown as a Viability Study for Sustainable Web Development

Proposal: JSON + Markdown as a Viability Study for Sustainable Web Development
To the W3C Sustainable Web Interest Group,

I am reaching out to propose a forward-thinking study on the feasibility of JSON + Markdown as a lightweight and efficient alternative to traditional HTML for web page structuring. As web applications grow increasingly complex, optimizing rendering speed and reducing resource consumption have become critical objectives for sustainable web development.

Key Benefits of JSON + Markdown

Adopting JSON for web structure while utilizing Markdown for content formatting could provide several advantages:

  *   Improved Performance: JSON parsing is significantly faster and more structured than traditional HTML document processing.

  *   Reduced Resource Consumption: Rendering a JSON-based structure requires fewer computations compared to handling large DOM trees, resulting in lower CPU and memory usage.

  *   Enhanced Readability & Maintainability: JSON's hierarchical structure simplifies data representation, while Markdown streamlines content formatting, making code more accessible for developers.

  *   Modern API Integration: JSON is natively supported by most web frameworks and APIs, enabling seamless integration with backend services.

Comparison Example: HTML vs.. JSON + Markdown

A simple HTML structure:

html

<!DOCTYPE html>
<html>
  <head>
    <title>Sample Page</title>
  </head>
  <body>
    <h1>Welcome</h1>
    <p>This is a sample paragraph.</p>
  </body>
</html>


Equivalent JSON + Markdown representation:

json

{
  "_hjmdl_spec": { "version": "1.0", "content_type": "application/hjmdl+json" },
  "document": {
    "doctype": "HJMDL/1.0",
    "html": {
      "head": { "title": "Sample Page" },
      "body": { "content": "# Welcome\n\nThis is a sample paragraph." }
    }
  }
}


Potential for Standardization

Given its efficiency, this concept could be explored as a new web standard under organizations such as:

  *   W3C (World Wide Web Consortium)

  *   WHATWG (Web Hypertext Application Technology Working Group)

  *   ECMA International

A structured feasibility study could analyze compatibility with existing browsers, security implications, and adaptation methods for modern web ecosystems.

Call to Action

I invite the W3C Sustainable Web Interest Group to evaluate JSON + Markdown as a potential direction for sustainable web development. If this approach proves viable, it could provide a foundational shift toward faster, leaner, and more resource-efficient web technologies.

Looking forward to your thoughts and insights on this matter.

Best regards, Marlon L de Albuquerque