Templates?

[Martin-Pitt]

I'm thinking of creating the following templates like from the wiki:

• LSL Function
• LSL Event
• LSL Constant
• LSL Constants (a collection of related constants)

The LSL function would be quite similar to the one on the LSL Wiki, with sections such as description, specification, examples, etc.

I think I can do this in Astro by setting up an astro component and using named slots to target where content goes (instead of props). Named slots means I can write large content more naturally from the source document (e.g. an mdx page).

This would probably look something like:

<LSLFunction
	name="llRezObjectWithParams"
>
	<Fragment slot="description">
		Instantiate **inventory** object at **pos** with an initial set of parameters specified in **params**.
				
		**pos** will default to the position of the object containing the script, unless REZ_POS is specified. (see below)
		
		Returns a key which will be the key of the object when it is successfully rezzed in the world.
	</Fragment>
</LSLFunction>

The templates should probably have different types of contextual "lifecycles" related to LSL implementation, editorial publishing or i18n.

---

LSL Implementation Lifecycle for a function/event/constant:

• Proposed
• Experimental
• Production
  • Recently Added
  • Recently Updated
• Deprecated
• Removed
• Broken

These are somewhat loosely based on the legend here: https://wiki.secondlife.com/wiki/Category:LSL_Functions

---

Editorial Lifecycle:

• Undocumented
• Draft
• Published

These are common editorial publishing lifecycles with addition of "undocumented" to cover for (generated) placeholder pages. Such as ones created from script based on keywords.xml

---

i18n Lifecycle

• Not translated
• Partially translated
• Translation up to date
• Content changed since translation

This is a general top level. With English set as the root locale it will be assumed that when a root page is updated that any translated pages would be out of date. I'll need to think thoroughly on a strategy for all of this, supporting different locales, being able to encourage people to step up to become a locale champion, as well as ways of tracking translation progress.

[Martin-Pitt]

With the LSL Definitions, I've also created LSL Control (for flow control keywords) and LSL Type (for types like vector, rotation etc).

Undocumented has been renamed to Stub, which is set when the page is created by the stub autogenerator. When in stub it can still be replaced by the autogenerator script in case the source of truth is edited.