I'm starting an overhaul of our documentation. Since my time is limited, this will not be a short process.

I have a couple of goals:
- Convert all the documentation from its current dependency on a specific component style library to GitHub Flavored Markdown (GFM)
- Streamline the current library standards into some more beginner friendly.

I've started a new GitHub repo for our documentation so that we can have better revision history and tracking.

Here's a preview:
https://library.ldraw.org/documentation/3

Note, the above is a very rough first go. My thought process is to have all the requirements highlighted. Right now that's in bold but that style is easily changed if someone have a better idea.

As always, I welcome any and all feedback.

Found here:
https://www.ldraw.org/docs-main/ldraw-or...ndard.html

- Reformatted for clarity.
- Explicitly stated orientation 
- Added optional suffix to naming convention for non-square/rectangular boxes.

The User Dashboard - 'My Submits' sorting options are 'Filename', 'Description', and 'Status'. My actions such as submission of corrected files do not show up on the User Dashboard - 'Events On My Submits'.
Is it possible to add 'Date' to the former or my actions to the latter?

Hello there people from Ldraw! I'm in need of 2 parts for a big project. Could someone please add these to the parts list? They are both on the builders app I believe 


3473



970d54pb01 (Just the special leg; no printing needed)

normally this is something snipe would do

dual moulded windscreen (111983) in 75414
https://www.newelementary.com/2025/07/re...eeder.html

triangle panel piece (6613) in 42215
https://www.newelementary.com/2025/07/pa...chnic.html

straw hat from one piece theme, no id yet seen in 75636, 75637 and 75638

(the dark red is printed)

   

Main thread for Ideas sets released in 2025

Hello,
how do we handle stickers with identical design, but with different sheet numbers?

This is the case with:
Sticker  1.8 x  1.8 Chequered
and
Red "PORSCHE" on Black Background Sticker

For the first we have a lot of alias of the original part 6142617z: 6141875d, 6142271p, 6148328a, 6221655aj, 617973o and 6221805ah.
Some official, others in the process of being approved.
Each file shows the name of a different sheet and the keywords that refer to the set.
This seems correct to me, otherwise the reference to the single sheet is lost. If I look at the list of stickers on a sheet, it seems that some are missing.
it's a bit like the symmetrical stickers of the same sheet. Both are saved, even if it would be enough to mirror them when drawing the assembly set.


For the second we have two sets (flat sticker, formed sticker and part with sticker applied): 6221655i and 18972dy3, 6097428ao and 18972dy5.
At the moment they are copies and not aliases but it will be remedied soon.



The questions are:
 - Do we keep aliases even for shortcuts even if they appear identical? Or can 18972dy5 be deleted and can its keywords be moved to 18972dy3?
 - Do we continue to make the aliases of the parts or do we add the keywords in a single reference part? And, for each new set that uses this part, should we modify the single official part to add the keywords to the new set.

(2025-07-30, 15:25)Orion Pobursky Wrote: We also need to address if/how we want to name non-square/rectangular sticker backs if creation is desired.

The brick runners (e.g.  31202c04) are assemblies consisting of one base, four wheels, and two axles.

The base has 31202 embossed onto it and 5436 printed with black ink.
Each wheel has 31204 embossed on it.
The metal axles have no visible part numbers.

What is the part number for the chassis/base to be used in LDraw?
What is the assembly number to be used in LDRaw?
Shall the c01... follow the same logic as in BrickLink?
What u number can I use for the metal axles and which color would I make it?

Is there any special way to mark these parts as members of assemblies/shortcuts so that they do not get used outside any assembly?

I'd like to ressurect this discussion:
https://forums.ldraw.org/thread-28281-post-54224.html

To recap, the current practice is as follows:
- The part and the sticker should be color 16
- If the part is an assembly of a color 16 part and a transparent part and the sticker is placed on the transparent area:
  - For a solid color sticker, the color will be the color of the sticker back (usually white)
  - For a transparent sticker, the color will be Trans_Sticker

I'm advocating that all stickers in a sticker shortcut should be hard coded the color that they actually are.

In fact, I'm also leaning towards the notion that all sticker colors should be hard coded in the sticker itself (i.e. no color 16 boxes but white, clear, sliver, etc.). This would clear up a lot of problems but not sure we need to go that far.