Keystone should respond to Web Browser with HTML

Registered by Adam Young

When pointing a browser at Keystone, it currently displays XML. If the browser will accept HTML, Keystone should respond with HTML

While a complete user experience is beyond the scope of the core keystone project, it should be easy for deployments to customize base on the concept of progressive enhancement:

Visiting a page should perform a transform from Python to HTML code much like what is done via JSON. The nesting/hierarchy will use DL/DT/DD tags for key-value pairs and UL for arrays.

Links will be specially handled to be proper hyperlinks.

This blueprint only handles the original display of existing pages, not additional navigation nor form generation.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Not
Drafter:
Adam Young
Direction:
Needs approval
Assignee:
Adam Young
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Morgan Fainberg

Related branches

Sprints

Whiteboard

This blueprint needs a specification if it is to be continued / approved.

Gerrit topic: https://review.openstack.org/#q,topic:bp/render-html,n,z

Addressed by: https://review.openstack.org/29105
    html_body

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.