Xaraya Andy V 
Request for Comments: 0048 Xaraya Core Dev 
Category: Best Current Practice December 2003 

RFC-0048: Xaraya Style Guide (XSG)

Status of this Memo

This document specifies a Xaraya Best Current Practices for the Xaraya Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.

Copyright Notice

Copyright © The Digital Development Foundation (2003). All Rights Reserved.

Table of Contents

1. Introduction to Xaraya Style Guide

1 This section describes the aims and objectives of this document.

1.1 Who should read it

2 All xaraya core, modules and themes developers who develop interfaces with BL templates.

1.2 What it is

3 It is an attempt to set standards and rules describing common xaraya user interfaces (UI) and explaining how to build them within the limitations of existing xaraya framework.

1.3 What it is not

4 This guide alone cannot help those who are not familiar with W3C standards and have little or no experience working with XHTML and CSS web documents. We cannot deliver all necessary and relevant information in a single short document, so all our readers are also strongly encouraged to review accompanying references, examples and tutorials.

1.4 Guiding Principles

5 (TODO)

1.5 Limitations

6 (TODO)

1.6 Rationale

7 (TODO)

1.7 Status of readiness

8  Work in progress. Do not treat this document as the definitive guide until the status says "Completed".

2. Terms and Definitions

9 Terms and abstract models used throughout the guide. (TODO)

3. Administrator Interfaces

10 How the admin UI is built

4. User Interfaces

11 (TODO)

5. Other Examples

12 (TODO)

6. References

13 (TODO)

7. Tutorials

14 (TODO)

Author's Address

AndyVXaraya Core DevEMail:

A. Notes

15 (TODO)

Intellectual Property Statement

The DDF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the DDF's procedures with respect to rights in standards-track and standards-related documentation can be found in RFC-0.

The DDF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the DDF Board of Directors.


Funding for the RFC Editor function is provided by the DDF