v0.1.1 · MIT

HTML is the API.

YPY is a hypermedia framework. An attribute on an element says which request to make and where the answer goes. The server answers with HTML. One script, no build step, no dependency.

go get github.com/ypy-develop/[email protected]
The server side, in Go. The browser side is one script tag, below.

Install

One script tag.

Put it in the page, from either address, or add the package from npm. There is nothing to compile and nothing to configure to start; the same file works in a static page and in an application.

The Go SDK answers fragments and forms, and tells a YPY request from a browser one. Other stacks use the same headers: see server side.

jsDelivr
<script src="https://cdn.jsdelivr.net/gh/ypy-develop/[email protected]/dist/ypy.min.js"></script>
cdn.ypy.dev
<script src="https://cdn.ypy.dev/[email protected]/ypy.min.js"></script>
npm
npm install @ypy-dev/[email protected]
Go SDK
go get github.com/ypy-develop/[email protected]

A page

Read it aloud.

On click, GET /demo/hello, put the answer into #demo-out. That is the whole contract, and the button on the right runs it against this site.

Introduction
index.html
<button ypy-get="/hello" ypy-target="#out">Say hello</button>
<p id="out"></p>

The answer lands here.

Where to go

141 attributes, 127 events, 48 extensions.

  • Start here: one long page, from the first attribute to security and testing.

  • Every attribute, event, header and configuration key, generated from the library.

  • Click to edit, active search, bulk update, delete a row: complete and short.

  • Streaming, WebSocket, history cache, optimistic updates and more, one file each.

  • Why YPY is built the way it is: size, security, performance and the choices behind them.

  • Questions, ideas and show-and-tell, in the GitHub discussions.

  • The code, the issues and the releases.