Content improvements

Author: zefhemel

Library/Std/Template.md

@@ -40,7 +40,7 @@ end
 -- * The extracted frontmatter
 function template.fromPage(name, raw)
   local fm = index.extractFrontmatter(space.readPage(name),  {
-    removeFrontmatterSection = true,
+    removeFrontMatterSection = true,
     removeTags = true
   })
 

website/API/index.md

@@ -56,7 +56,7 @@ It returns a table with two keys:
 The `extractOptions` is an optional table that can contain the following keys (which will affect the returned `text`):
 - `removeKeys`: An array of keys to remove from the frontmatter.
 - `removeTags`: A boolean or array of tags to remove from the frontmatter.
-- `removeFrontmatterSection`: A boolean to remove the frontmatter section from the document.
+- `removeFrontMatterSection`: A boolean to remove the frontmatter section from the document.
 
 Example applied to this page:
 ${(index.extractFrontmatter(editor.getText())).frontmatter}

website/Commands.md

@@ -3,3 +3,5 @@ Commands define actions that SilverBullet can perform. They range from simple ed
 SilverBullet ships with a lot of commands built in, but custom ones can also be defined using [[Space Lua]] and [[Plugs]].
 
 Beside the list below, all commands available commands appear in the [[Command Palette]] but may have key bindings as well (these key bindings appear in the [[Command Palette]] and are configurable in [[^Library/Std/Config]]).
+
+You can create custom command using the [[^Library/Std/Command]] API.

website/Linked Mentions.md

@@ -1,3 +1,3 @@
-On this site you see a section “Linked Mentions” appear along the bottom of every page that has incoming links. 👇🏻 This section lists all pages that contain a _link_ to the current page. This allows for easy navigation, and may help you discover linked concepts through these links.
+On this site you see a section “Linked Mentions” appear along the bottom of every page that has incoming links. 👇🏻 This section lists all pages that contain a _link to_ the current page. This allows for easy navigation, and may help you discover linked concepts through these links.
 
-Implementation: [[^Library/Std/Widgets#Table of contents]]
+Implementation: [[^Library/Std/Widgets#Linked mentions]]

website/Objects.md

@@ -1,4 +1,4 @@
-SilverBullet automatically builds and maintains an index of _objects_ extracted from all markdown pages in your space. It subsequently allows you to use [[Space Lua/Lua Integrated Query]] to query this database in (potentially) useful ways.
+SilverBullet automatically builds and maintains an index of _objects_ extracted from all [[Markdown]] [[Pages]] in your [[Spaces]]. It subsequently allows you to use [[Space Lua/Lua Integrated Query]] to query this database in (potentially) useful ways.
 
 By design, the truth remains in the markdown: all data indexed as objects will have a representation in markdown text as well. This index can be flushed at any time and be rebuilt from its source markdown files kept in your space (and you can do so on demand if you like using the `Space: Reindex` command).
 
@@ -7,49 +7,19 @@ Every object has a set of [[Attributes]], some predefined, but you can add any a
 
 The following attributes are predefined, and you can expect all objects to have them:
 * `ref`: a globally unique _identifier_, often represented as a pointer to the place (page, position) in your space where the object is defined. For instance, a _page_ object will use the page name as its `ref` attribute, and a `task` will use `page@pos` (where `pos` is the location the task appears in `page`).
-* `tag`: the main type, or “tag” of the page, usually a built-in type of the object (see below).
+* `tag`: the main type, or “tag” of the object, usually a built-in type (see below for a list).
 
 In addition, many objects will also contain:
 * `tags`: an optional set of additional, explicitly assigned tags.
-* `itags`: a set of _implicit_ or _inherited_ tags: including the object’s `tag`, `tags` as well as any tags _assigned to its containing page_. This is useful to answer queries like, “give me all tasks on pages where that page is tagged with `person`“, which would be expressed as `task where itags = "person"` (although technically that would also match any tags that have the `#person` explicitly assigned).
+* `itags`: a set of _implicit_ or _inherited_ tags: including the object’s `tag`, `tags` as well as any tags _assigned to its containing page_. This is useful to answer queries like, “give me all tasks on pages where that page is tagged with `person`“, which would be expressed as `query[[from index.tag "task" where table.includes(_.itags, "person")]]` (although technically that would also match any tags that have the `#person` explicitly assigned).
 
 Beside these, any number of additional tag-specific and custom [[Attributes]] can be defined (see below).
 
 # Tags
 Every object has a main `tag`, which signifies the type of object being described. In addition, any number of additional tags can be assigned as well via the `tags` attribute. You can use either the main `tag` or any of the `tags` as query sources in [[Space Lua/Lua Integrated Query]] — examples below.
 
-## Styling
-You can add custom styles to a tag by leveraging the `data-tag-name` attribute, [CSS Attribute Selectors](https://developer.mozilla.org/en-US/docs/Web/CSS/Attribute_selectors) and custom [[Space Style]]'s. Every tag gets an attribute added to it called `data-tag-name` that is set to the tag name with the `#` symbol stripped out. So given the tag #my-cool-tag the `data-tag-name` attribute would look like: 
-
-    data-tag-name="my-cool-tag"
-
-This allows us to do things like change the color of the #my-cool-tag 
-to have a purple background, limegreen text and bold font by adding the following [[Space Style]]:
-
-```css
-.sb-hashtag[data-tag-name="my-cool-tag"] {
-  background: purple;
-  color: limegreen;
-  font-weight: bolder;
-}
-```
-
-Additionally tags written using angle brackets, such as...
-
-    #<my cool tag> 
-
-...can be styled via [[Space Style]] like this:
-```css
-.sb-hashtag[data-tag-name="my cool tag"] {
-  background: purple;
-  color: limegreen;
-  font-weight: bolder;
-}
-```
-
-## Built-in tags
-
-### page
+# Built-in tags
+## page
 Every page in your space is available via the `page` tag. You can attach _additional_ tags to a page, by either specifying them in the `tags` attribute [[Frontmatter]], or by putting additional [[Tags]] in a stand alone paragraph with no other (textual) content in them, for instance check the very first line of this page that says `#level/intermediate`.
 
 In addition to `ref` and `tags`, the `page` tag defines a bunch of additional attributes as can be seen in this example query:
@@ -59,12 +29,12 @@ ${query[[from index.tag "page" where name == _CTX.currentPage.name]]}
 Note that you can also query this page using the `level/intermediate` directly:
 ${query[[from index.tag "level/intermediate"]]}
 
-### aspiring-page
+## aspiring-page
 [[Aspiring Pages]] are pages that are linked to, but not yet created.
 
 ${query[[from index.tag "aspiring-page"]]}
 
-### table
+## table
 Markdown table rows are indexed using the `table` tag, any additional tags can be added using [[Tags]] in any of its cells.
 
 | Title | Description Text |
@@ -77,7 +47,7 @@ ${query[[from index.tag "table" where page == _CTX.currentPage.name]]}
 
 Table headers will be normalized by converting them to lowercase and replacing all non alphanumeric characters with `_`.
 
-### item
+## item
 List items (both bullet point and numbered items) are indexed with the `item` tag, and additional tags can be added using [[Tags]].
 
 Here is an example of a #quote item using a custom [[Attributes|attribute]]:
@@ -121,7 +91,7 @@ ${template.each(query[[from index.tag "upnext"]], templates.taskItem)}
 
 Similar to [[#item]], `task` objects have a `parent` attribute when nested (pointing to their parent `item`), and inherit their ancestor’s tags in `itags`.
 
-### taskstate
+## taskstate
 [[Tasks]] support the default `x` and ` ` states (done and not done), but custom states as well. Custom states used across your space are kept in `taskstate`:
 
 * [NOT STARTED] Task 1
@@ -148,25 +118,24 @@ age: 55
 Which then becomes queriable via the `contact` tag:
 ${query[[from index.tag "contact"]]}
 
-### link
+## link
 All page _links_ are tagged with `link`. You cannot attach additional tags to links. The main two attributes of a link are:
 
 * `toPage` the page the link is linking _to_
 * `page` the page the link appears on
 
 In addition, the `snippet` attribute attempts to capture a little bit of context on where the link appears.
 
-_Note_: this is the data source used for the {[Mentions: Toggle]} feature as well page {[Page: Rename]}.
-
 Here is a query that shows some links that appear in this particular page:
+
 ${query[[from index.tag "link" where page == _CTX.currentPage.name limit 5]]}
 
-### header
+## header
 Headers (lines starting with `#`, `##` etc.) are indexed as well and queriable.
 
 ${query[[from index.tag "header" where page == _CTX.currentPage.name limit 3]]}
 
-### tag
+## tag
 The ultimate meta tag is _tag_ itself, which indexes for all tags used, in which page they appear and what their “parent tag” is (the context of the tag: either `page`, `item` or `task`).
 
 Here are the tags used/defined in this page:

website/Outlines.md

@@ -1,6 +1,4 @@
-#level/intermediate
-
-While SilverBullet is not a “proper” outliner, it does offer a number of useful commands to manage outlines.
+While SilverBullet is not a “proper” outliner like e.g. [LogSeq](https://logseq.com), it does offer a useful commands to manage outlines.
 
 An outline is simply a (nested) bulleted list, for instance:
 

website/Self Hosting.md

@@ -0,0 +1,11 @@
+According to [Wikipedia](https://en.wikipedia.org/wiki/Self-hosting_(web_services)):
+
+> **Self-hosting** is the practice of running and maintaining a [website](https://en.wikipedia.org/wiki/Website) or [service](https://en.wikipedia.org/wiki/Service_\(systems_architecture\) "Service (systems architecture)") using a private [web server](https://en.wikipedia.org/wiki/Web_server "Web server"), instead of using a service outside of the administrator's own control. Self-hosting allows users to have more control over their data, privacy, and computing infrastructure, as well as potentially saving costs and improving skills.
+
+SilverBullet is the ultimate gateway to practice hosting your own stuff. 
+
+Had a taste and want more? Here are some excellent resources:
+
+* [Self hosting Reddit](https://www.reddit.com/r/selfhosted/)
+* [Awesome Self Hosted](https://github.com/awesome-selfhosted/awesome-selfhosted)
+

website/Space Style.md

@@ -22,7 +22,35 @@ The following [[Space Lua/Lua Integrated Query]] is used to determine the order
 query[[from index.tag "space-style" order by _.priority desc]]
 ```
 
-# Examples
+# Tag Styling
+You can add custom styles to a tag by leveraging the `data-tag-name` attribute, [CSS Attribute Selectors](https://developer.mozilla.org/en-US/docs/Web/CSS/Attribute_selectors) and custom [[Space Style]]'s. Every tag gets an attribute added to it called `data-tag-name` that is set to the tag name with the `#` symbol stripped out. So given the tag #my-cool-tag the `data-tag-name` attribute would look like: 
+
+    data-tag-name="my-cool-tag"
+
+This allows us to do things like change the color of the #my-cool-tag 
+to have a purple background, limegreen text and bold font by adding the following [[Space Style]]:
+
+```css
+.sb-hashtag[data-tag-name="my-cool-tag"] {
+  background: purple;
+  color: limegreen;
+  font-weight: bolder;
+}
+```
+
+Additionally tags written using angle brackets, such as...
+
+    #<my cool tag> 
+
+...can be styled via [[Space Style]] like this:
+```css
+.sb-hashtag[data-tag-name="my cool tag"] {
+  background: purple;
+  color: limegreen;
+  font-weight: bolder;
+}
+```
+# More examples
 All the actual CSS in these examples is commented out as to not affect this very website. 
 ```space-style
 html {