once the docs site is live....update that url

Since version 0.27.0 there is lightweight version checking bazel --version. This should be documented in command line reference (https://docs.bazel.build/versions/master/command-line-reference.html).

Below is a basic documentation outline. Please feel free to add your feedback.

• Organizing Groups and Events
  • Become an organizer
  • Creating and Managing Events
  • Group and Member Communications
  • Group Settings
  • Manage Members
• Using Chapter
  • How Chapter Works
  • Create an Account
  • Group and event photos
  • Member guide
  • Sharing

Warning: As of this writing, scopes are not implemented

This guide explains how scopes work

• The existing scopes (healthcheck, network, identity)
• Creating an instance of a scope in an application configuration
• Attaching a component to a scope in an application configuration
• Best practices for when to create a new scope and how to share one scope across multiple application conf

How the federation aspect of lemmy will work? Will there be a 'global database' that will make sure all 'subreddit' (how are they called on lemmy?) names are unique? Or each instance will be able to register the same 'subreddit' name and as a result we will have:
https://dev.lemmy.ml/#/c/asklemmy
https://another.instance/#/c/asklemmy
https://another.instance2/#/c/asklemmy
If it's the latter,

It seems that the official Javadoc is not up to date. I found differences in the latest releases and Javadoc site -> https://developers.google.com/protocol-buffers/docs/reference/java/.

I checked for UnsafeByteOperation.java at Javadoc site and at [github repo](https://github.com/pr

Description

So our function arrayToHtmlList is in a pretty bad space and could use an update. We already had some discussion over at #675 but I wanted to move the update discussion over to an issue for more visibility.

Current problem:

It uses an awkward query selector instead of the `document.prototype.getElementBy

Memory management in the documentation is illustrated by an example which shows a case where no manual memory management is necessary. The other is an example of an array, which is freed by a free method.

There is no other information on how the programmer can differentiate between cases where manual memory management is necessary and where it isn't, other than that leaks will be reported at ru