diff --git a/public/docs/guides/index.xml b/public/docs/guides/index.xml
index c9eff58..ffff427 100644
--- a/public/docs/guides/index.xml
+++ b/public/docs/guides/index.xml
@@ -2,46 +2,46 @@
Getting Started on Beacon SDK
- http://localhost:1313/beacon-docs/docs/guides/
+ //localhost:1313/docs/guides/
Recent content in Getting Started on Beacon SDKHugoenCopyright (c) 2020-2024 HyasSat, 07 Sep 2024 16:13:18 +0200
-
+ Introduction
- http://localhost:1313/beacon-docs/docs/guides/introduction/
+ //localhost:1313/docs/guides/introduction/
Tue, 07 May 2024 16:04:48 +0200
- http://localhost:1313/beacon-docs/docs/guides/introduction/
+ //localhost:1313/docs/guides/introduction/The Beacon SDK is a toolset designed to enhance and streamline the development of virtual tabletop (VTT) character sheets and other interactive elements.Installation
- http://localhost:1313/beacon-docs/docs/guides/installation/
+ //localhost:1313/docs/guides/installation/
Sun, 07 Apr 2024 16:04:48 +0200
- http://localhost:1313/beacon-docs/docs/guides/installation/
+ //localhost:1313/docs/guides/installation/Prerequisites Before you can install the Beacon SDK, you’ll need to have Node.js installed on your machine. If you don’t have Node.Glossary
- http://localhost:1313/beacon-docs/docs/guides/glossary/
+ //localhost:1313/docs/guides/glossary/
Thu, 07 Mar 2024 16:04:48 +0200
- http://localhost:1313/beacon-docs/docs/guides/glossary/
+ //localhost:1313/docs/guides/glossary/Background: The background color of the alert box.
Character: An entity in the game with attributes, bio, GM notes, and a token representation.FAQ
- http://localhost:1313/beacon-docs/docs/guides/faq/
+ //localhost:1313/docs/guides/faq/
Sun, 07 Jan 2024 16:04:48 +0200
- http://localhost:1313/beacon-docs/docs/guides/faq/
+ //localhost:1313/docs/guides/faq/Q1: What are actions in the context of the VTT?
Actions are methods executed from the VTT, often used for rolls triggered from macros or chat buttons.Contributing Guide
- http://localhost:1313/beacon-docs/docs/guides/contributing-guide/
+ //localhost:1313/docs/guides/contributing-guide/
Wed, 07 Feb 2024 16:13:18 +0200
- http://localhost:1313/beacon-docs/docs/guides/contributing-guide/
+ //localhost:1313/docs/guides/contributing-guide/We appreciate your interest in contributing to the Beacon SDK project. Here are some guidelines to help you get started:
diff --git a/public/docs/guides/installation/index.html b/public/docs/guides/installation/index.html
index 400615c..631ba0c 100644
--- a/public/docs/guides/installation/index.html
+++ b/public/docs/guides/installation/index.html
@@ -1,57 +1,57 @@
-
+
-
-
-
+
+
+
-
+
-
-
+
+
Installation | Beacon SDK
-
+
-
+
-
+
-
+
-
+
@@ -64,19 +64,19 @@
"itemListElement": [
{
"@type": "ListItem",
- "item": "http://localhost:1313/beacon-docs/",
+ "item": "//localhost:1313/",
"name": "Welcome to Beacon Sdk",
"position": 1
},
{
"@type": "ListItem",
- "item": "http://localhost:1313/beacon-docs/docs/",
+ "item": "//localhost:1313/docs/",
"name": "Docs",
"position": 2
},
{
"@type": "ListItem",
- "item": "http://localhost:1313/beacon-docs/docs/guides/",
+ "item": "//localhost:1313/docs/guides/",
"name": "Getting Started",
"position": 3
},
@@ -101,7 +101,7 @@
diff --git a/public/docs/tutorials/index.xml b/public/docs/tutorials/index.xml
index 782883a..669ca5d 100644
--- a/public/docs/tutorials/index.xml
+++ b/public/docs/tutorials/index.xml
@@ -2,18 +2,18 @@
Tutorials on Beacon SDK
- http://localhost:1313/beacon-docs/docs/tutorials/
+ //localhost:1313/docs/tutorials/
Recent content in Tutorials on Beacon SDKHugoenCopyright (c) 2020-2024 HyasTue, 07 May 2024 16:13:18 +0200
-
+ Beginner Beacon Sheet
- http://localhost:1313/beacon-docs/docs/tutorials/beginner-beacon-sheet/
+ //localhost:1313/docs/tutorials/beginner-beacon-sheet/
Tue, 07 May 2024 16:13:18 +0200
- http://localhost:1313/beacon-docs/docs/tutorials/beginner-beacon-sheet/
+ //localhost:1313/docs/tutorials/beginner-beacon-sheet/Prerequisites To set this sheet up properly, make sure that you have the following tools installed:
Vue.js Vite SCSS Figure 1: Quickstart sheet
diff --git a/public/docs/tutorials/sitemap.xml b/public/docs/tutorials/sitemap.xml
index 8c8a1a9..224b481 100644
--- a/public/docs/tutorials/sitemap.xml
+++ b/public/docs/tutorials/sitemap.xml
@@ -2,7 +2,7 @@
xmlns:xhtml="http://www.w3.org/1999/xhtml">
- http://localhost:1313/beacon-docs/docs/tutorials/beginner-beacon-sheet/
+ //localhost:1313/docs/tutorials/beginner-beacon-sheet/2024-05-07T16:13:18+02:00monthly0.5
diff --git a/public/index.html b/public/index.html
index 9cff17a..f85dc75 100644
--- a/public/index.html
+++ b/public/index.html
@@ -1,56 +1,56 @@
-
+
-
-
-
+
+
+
-
+
-
-
-
+
+
+
Welcome to Beacon SDK
-
+
-
+
-
+
-
+
-
+
@@ -307,11 +307,11 @@
Read the docs
diff --git a/public/index.xml b/public/index.xml
index a6b98ae..ed35221 100644
--- a/public/index.xml
+++ b/public/index.xml
@@ -2,81 +2,81 @@
Welcome to Beacon SDK on Beacon SDK
- http://localhost:1313/beacon-docs/
+ //localhost:1313/
Recent content in Welcome to Beacon SDK on Beacon SDKHugoenCopyright (c) 2020-2024 HyasWed, 07 Feb 2024 16:04:48 +0200
-
+ Example Post
- http://localhost:1313/beacon-docs/blog/example-post/
+ //localhost:1313/blog/example-post/
Thu, 07 Sep 2023 16:27:22 +0200
- http://localhost:1313/beacon-docs/blog/example-post/
+ //localhost:1313/blog/example-post/You can use blog posts for announcing product updates and features.Introduction
- http://localhost:1313/beacon-docs/docs/guides/introduction/
+ //localhost:1313/docs/guides/introduction/
Tue, 07 May 2024 16:04:48 +0200
- http://localhost:1313/beacon-docs/docs/guides/introduction/
+ //localhost:1313/docs/guides/introduction/The Beacon SDK is a toolset designed to enhance and streamline the development of virtual tabletop (VTT) character sheets and other interactive elements.Installation
- http://localhost:1313/beacon-docs/docs/guides/installation/
+ //localhost:1313/docs/guides/installation/
Sun, 07 Apr 2024 16:04:48 +0200
- http://localhost:1313/beacon-docs/docs/guides/installation/
+ //localhost:1313/docs/guides/installation/Prerequisites Before you can install the Beacon SDK, you’ll need to have Node.js installed on your machine. If you don’t have Node.Glossary
- http://localhost:1313/beacon-docs/docs/guides/glossary/
+ //localhost:1313/docs/guides/glossary/
Thu, 07 Mar 2024 16:04:48 +0200
- http://localhost:1313/beacon-docs/docs/guides/glossary/
+ //localhost:1313/docs/guides/glossary/Background: The background color of the alert box.
Character: An entity in the game with attributes, bio, GM notes, and a token representation.FAQ
- http://localhost:1313/beacon-docs/docs/guides/faq/
+ //localhost:1313/docs/guides/faq/
Sun, 07 Jan 2024 16:04:48 +0200
- http://localhost:1313/beacon-docs/docs/guides/faq/
+ //localhost:1313/docs/guides/faq/Q1: What are actions in the context of the VTT?
Actions are methods executed from the VTT, often used for rolls triggered from macros or chat buttons.Overview
- http://localhost:1313/beacon-docs/docs/components/overview/
+ //localhost:1313/docs/components/overview/
Fri, 07 Jun 2024 16:12:37 +0200
- http://localhost:1313/beacon-docs/docs/components/overview/
+ //localhost:1313/docs/components/overview/The Beacon SDK is composed of various components that allow developers to create dynamic and interactive character sheets for virtual tabletop (VTT) games.Actions
- http://localhost:1313/beacon-docs/docs/components/actions/
+ //localhost:1313/docs/components/actions/
Tue, 07 May 2024 16:12:37 +0200
- http://localhost:1313/beacon-docs/docs/components/actions/
+ //localhost:1313/docs/components/actions/Actions are a collection of methods that can be executed from the VTT. These actions are used for any rolls that may need to be triggered outside of the sheet itself, such as from a macro or a chat button.Computed
- http://localhost:1313/beacon-docs/docs/components/computed/
+ //localhost:1313/docs/components/computed/
Sun, 07 Apr 2024 16:12:37 +0200
- http://localhost:1313/beacon-docs/docs/components/computed/
+ //localhost:1313/docs/components/computed/Sheet authors define computed properties that are accessed by the host. These computed properties can be used as attributes in macros and are available to assign as values to token bars - if the tokenBarValue property is set to true.Handlers
- http://localhost:1313/beacon-docs/docs/components/handlers/
+ //localhost:1313/docs/components/handlers/
Thu, 07 Mar 2024 16:12:37 +0200
- http://localhost:1313/beacon-docs/docs/components/handlers/
+ //localhost:1313/docs/components/handlers/Handler functions allow the sheet to respond to messages from the host. The handlers argument requires the following methods:
onInit The onInit function provides the initial set of data to the sheet.Handling Legacy Macro Attributes
- http://localhost:1313/beacon-docs/docs/components/handling-legacy-macro-attributes/
+ //localhost:1313/docs/components/handling-legacy-macro-attributes/
Wed, 07 Feb 2024 16:12:37 +0200
- http://localhost:1313/beacon-docs/docs/components/handling-legacy-macro-attributes/
+ //localhost:1313/docs/components/handling-legacy-macro-attributes/When utilizing Macros within the VTT, there are instances where a legacy macro might need to be employed for a Beacon sheet.
diff --git a/public/manifest.webmanifest b/public/manifest.webmanifest
index 5fcdbbe..0b07fa2 100644
--- a/public/manifest.webmanifest
+++ b/public/manifest.webmanifest
@@ -18,5 +18,5 @@
"theme_color": "#ffffff",
"background_color": "#ffffff",
"display": "standalone",
- "start_url": "/beacon-docs/"
+ "start_url": "/"
}
diff --git a/public/privacy/index.html b/public/privacy/index.html
index 1bbc0f3..c754267 100644
--- a/public/privacy/index.html
+++ b/public/privacy/index.html
@@ -1,57 +1,57 @@
-
+
-
-
-
+
+
+
-
+
-
-
+
+
Privacy Policy | Beacon SDK
-
+
-
+
-
+
-
+
-
+
@@ -62,7 +62,7 @@
"itemListElement": [
{
"@type": "ListItem",
- "item": "http://localhost:1313/beacon-docs/",
+ "item": "//localhost:1313/",
"name": "Welcome to Beacon Sdk",
"position": 1
},
@@ -87,7 +87,7 @@
diff --git a/public/robots.txt b/public/robots.txt
index 723f408..e4b90a1 100644
--- a/public/robots.txt
+++ b/public/robots.txt
@@ -1,3 +1,3 @@
User-agent: *
Disallow: /admin/
-Sitemap: http://localhost:1313/sitemap.xml
+Sitemap: //localhost:1313/sitemap.xml
diff --git a/public/search-index.json b/public/search-index.json
index e38fae0..8a6d055 100644
--- a/public/search-index.json
+++ b/public/search-index.json
@@ -1 +1 @@
-[{"content":"Well-thought-through product announcements will help increase feature awareness and engage users with new functionality. Just like sharing your public roadmap, it\u0026rsquo;s also a great way to let potential customers see that you\u0026rsquo;re constantly improving.\nFurther reading Read How to announce product updates and features ","date":"2023-09-07","id":0,"permalink":"/beacon-docs/blog/example-post/","summary":"You can use blog posts for announcing product updates and features.","tags":[],"title":"Example Post"},{"content":"","date":"2023-09-07","id":1,"permalink":"/beacon-docs/blog/","summary":"","tags":[],"title":"Blog"},{"content":"","date":"2024-06-07","id":2,"permalink":"/beacon-docs/docs/guides/","summary":"","tags":[],"title":"Getting Started"},{"content":"The Beacon SDK is a toolset designed to enhance and streamline the development of virtual tabletop (VTT) character sheets and other interactive elements.\nWhether you\u0026rsquo;re a game master (GM), a developer, or a player, the Beacon SDK provides a framework to create dynamic, responsive, and fully integrated VTT experiences.\nWhat is the Beacon SDK? The Beacon SDK is a specialized software development kit for virtual tabletops.\nIt facilitates creating and managing interactive character sheets, roll templates, macros, and other VTT functionalities.\nThe SDK ensures easy communication between the VTT platform and the character sheets, allowing real-time updates and interactions.\nKey Features Character Sheets: Design and implement detailed character sheets with dynamic attributes and real-time updates. Roll Mechanics: Integrate complex roll formulas and display roll results directly within the VTT. Macros: Create and manage macros for automated actions and roll calculations. Event Handling: Utilize a comprehensive set of handlers to manage various events and interactions within the VTT. Legacy Support: Convert and integrate legacy macros and roll templates with the new Beacon architecture. Customization: Define custom actions computed properties and handle specific roll templates tailored to your game\u0026rsquo;s needs. Components Overview The Beacon SDK is composed of several key components:\nActions: Define and manage custom actions that can be triggered within the VTT. Handlers: Event handlers that process and respond to various VTT events and messages. Computed Properties: Define dynamically computed properties based on other attributes. Macro Attributes: Convert and manage legacy macro attributes for compatibility with the Beacon SDK. Rolls: Implement advanced roll mechanics and display results dynamically within the VTT. For a comprehensive overview of these components, view the components section.\nGetting Started To get started with the Beacon SDK, you must initialize the relay, set up your character sheets, and define the necessary actions, handlers, and computed properties.\nThis documentation provides detailed guides and examples to help you through each step of the process.\nBy leveraging the Beacon SDK, you can create rich, interactive, fully integrated VTT experiences that enhance gameplay and streamline game management.\nWhether adapting existing character sheets or building new ones from scratch, the Beacon SDK offers the tools and flexibility to bring your virtual tabletop to life.\n","date":"2024-05-07","id":3,"permalink":"/beacon-docs/docs/guides/introduction/","summary":"The Beacon SDK is a toolset designed to enhance and streamline the development of virtual tabletop (VTT) character sheets and other interactive elements.","tags":[],"title":"Introduction"},{"content":"Prerequisites Before you can install the Beacon SDK, you\u0026rsquo;ll need to have Node.js installed on your machine. If you don\u0026rsquo;t have Node.js installed, use the following steps in the official Node.js documentation.\nStep 1: Accessing Beacon SDK npm i @roll20-official/beacon-sdk\rStep 2: Install \u0026amp; Import The following steps will guide you in installing the package in your application:\nAdd the package to your package.json:\nUnder the dependencies object key of your package.json, add a new string key called @roll20/beacon-sdk with the version you want to install from our version history.\nFor example:\n{ \u0026#34;@roll20/beacon-sdk\u0026#34;: \u0026#34;0.0.0\u0026#34; }\rFor more information about installing packages, refer to the NPM documentation.\nRun npm install:\nOpen a terminal in the root of your application’s folder and run the following command:\nnpm install\rFor more information about NPM commands, refer to the NPM install documentation.\nImport the necessary package contents in your application:\nThe package exports various utilities you can use in your application. For example, you will need to utilize the initRelay function from the package.\nHere\u0026rsquo;s an import statement for that function:\nimport { initRelay } from \u0026#39;@roll20/beacon-sdk\u0026#39;;\rFor more information about imports, refer to the JavaScript import documentation.\n","date":"2024-04-07","id":4,"permalink":"/beacon-docs/docs/guides/installation/","summary":"Prerequisites Before you can install the Beacon SDK, you\u0026rsquo;ll need to have Node.js installed on your machine. If you don\u0026rsquo;t have Node.","tags":[],"title":"Installation"},{"content":"Background: The background color of the alert box.\nCharacter: An entity in the game with attributes, bio, GM notes, and a token representation.\nCharacter sheet: A digital or printed page used to track a character\u0026rsquo;s attributes, abilities, and other relevant information in a role-playing game.\nComputed Property: Properties that have both get and set methods, which can be dynamically calculated.\nConvertLegacyMacroAttributes: A function to handle mapping legacy macro attributes to the new Beacon Sheet format.\nDispatch: A set of functions enabling the sheet to send commands back to the VTT.\nGM (Game Master): The person who runs the game, controls the NPCs \u0026amp; the story, and provides challenges for the players.\nHandler: Methods that act as event handlers to process messages from the host.\nInitRelay: Function to initialize the SDK relay, setting up communication between the host and the character sheet.\nMacro: A script that automates repetitive tasks in the VTT.\nRoll Template: A predefined format for displaying the results of a dice roll.\nToken: A visual representation of a character or object on the virtual tabletop, with various properties like position, size, and attributes.\nVTT (Virtual Tabletop): An online platform that allows players to play tabletop role-playing games over the internet.\nValidationMessage: A message displayed when an input value does not meet specific criteria.\nQuantum Roll: A system that ensures the fairness and authenticity of dice rolls in the VTT by using cryptographic methods.\n","date":"2024-03-07","id":5,"permalink":"/beacon-docs/docs/guides/glossary/","summary":"Background: The background color of the alert box.\nCharacter: An entity in the game with attributes, bio, GM notes, and a token representation.","tags":[],"title":"Glossary"},{"content":"\rQ1: What are actions in the context of the VTT?\rActions are methods executed from the VTT, often used for rolls triggered from macros or chat buttons. They are defined in the sheet\u0026rsquo;s configuration and can interact with character data. Q2: How are computed properties used in the VTT?\rComputed properties are defined attributes accessible by the host, usable in macros, and assignable to token bars. They can represent derived values or complex calculations based on character data. Q3: What is the dispatch function used for?\rThe dispatch function provides methods for sending commands from the character sheet back to the host, including updating character data, performing actions, and interacting with the VTT interface. Q4: What are roll buttons, and how do they work?\rRoll buttons are HTML elements with specific attributes that execute designated sheet actions when clicked. They can pass arguments to the action method and are commonly used for triggering rolls from the character sheet. Q5: How are legacy macro attributes handled in the VTT?\rLegacy macro attributes can be mapped to the new sheet structure using the convertLegacyMacroAttributes function. Sheet developers can define how to handle legacy attribute values to ensure compatibility with existing macros. Q6: What is the purpose of the query function?\rThe query function displays a SweetAlert prompt to users and returns the results along with any errors. It is commonly used for interactive prompts or confirmations within the VTT interface. Q7: How are tokens managed in the VTT?\rTokens represent characters or objects on the virtual tabletop. Functions like getTokens, updateTokensByCharacter, and addToTracker are used to retrieve token information, update token data, and manage tokens in the turn tracker. Q8: What is the role of the convertLegacyMacroAttributesArgs type?\rThe convertLegacyMacroAttributesArgs type defines the arguments used for handling legacy macro attributes. It includes the attribute name, character ID, and character data needed for mapping legacy attributes to the new sheet structure. ","date":"2024-01-07","id":6,"permalink":"/beacon-docs/docs/guides/faq/","summary":"Q1: What are actions in the context of the VTT?\rActions are methods executed from the VTT, often used for rolls triggered from macros or chat buttons.","tags":[],"title":"FAQ"},{"content":"The Beacon SDK is composed of various components that allow developers to create dynamic and interactive character sheets for virtual tabletop (VTT) games.\nThese components are crucial for handling actions, computations, macros, and rolls. This overview provides a high-level summary of each section, helping you understand their roles and how they integrate within the SDK.\nActions\rActions define specific operations that can be performed by characters within the VTT. These operations can range from simple tasks like rolling a dice to more complex interactions such as casting spells or activating abilities.\nHandlers\rHandlers are event listeners that manage communication between the VTT and the character sheet. They respond to various events, such as changes in character attributes or settings, and trigger appropriate actions or updates.\nComputed\rComputed properties are dynamic values derived from other character attributes. They allow for the creation of complex, calculated attributes that automatically update when their dependencies change.\nMacro Attributes\rMacro attributes handle the conversion of legacy macro attributes to the new format used in the Beacon SDK. This ensures compatibility with older character sheets and macros, allowing for a smooth transition to the new system.\nRolls\rThe Rolls component allows for advanced dice-rolling mechanics within the VTT. It supports both simple and complex rolls, providing flexibility in how roll results are displayed and computed.\n","date":"2024-06-07","id":7,"permalink":"/beacon-docs/docs/components/overview/","summary":"The Beacon SDK is composed of various components that allow developers to create dynamic and interactive character sheets for virtual tabletop (VTT) games.","tags":[],"title":"Overview"},{"content":"Actions are a collection of methods that can be executed from the VTT. These actions are used for any rolls that may need to be triggered outside of the sheet itself, such as from a macro or a chat button. Generally, most or all of a sheet’s rolls should be defined as actions.\nactions: { [name: string]: { method: (props: { dispatch: Dispatch, character: Character, messageId?: string, rolls?: RollResults }, ...args: string[]): void | Promise\u0026lt;void\u0026gt; } }\rActions are passed into the initRelay function in an object, where the keys are the unique names of the actions, and the values are objects containing a method property (additional metadata fields may be added to this object in the future).\nThe method receives a props object containing the following properties:\ndispatch: A Dispatch object. character: The data of the character performing the action. Currently, the action will not receive the character’s bio or GM notes, regardless of whether the player has access to those fields. messageId (optional): A unique ID for an existing chat message. It\u0026rsquo;s included in actions triggered from chat buttons to provide context for the original roll. rolls (optional): Included when action is triggered from a chat button. Contains the roll results of the original roll. These functions can also receive an unlimited number of additional arguments. This is because these actions can be triggered by plain text via a macro. However, all additional arguments must be strings. Additionally, these functions can be synchronous or asynchronous and do not return a value.\n","date":"2024-05-07","id":8,"permalink":"/beacon-docs/docs/components/actions/","summary":"Actions are a collection of methods that can be executed from the VTT. These actions are used for any rolls that may need to be triggered outside of the sheet itself, such as from a macro or a chat button.","tags":[],"title":"Actions"},{"content":"","date":"2024-05-07","id":9,"permalink":"/beacon-docs/docs/quick/","summary":"","tags":[],"title":"Quick Start"},{"content":"","date":"2024-04-07","id":10,"permalink":"/beacon-docs/docs/components/","summary":"","tags":[],"title":"Components"},{"content":"Sheet authors define computed properties that are accessed by the host. These computed properties can be used as attributes in macros and are available to assign as values to token bars - if the tokenBarValue property is set to true.\ncomputed: { [name: string]: { tokenBarValue?: boolean, description?: string, get: ( props: { character: Character }, ...args: string[] ) =\u0026gt; ComputedResult, set?: ( props: { character: Character, dispatch: Dispatch }, ...args: string[] ) =\u0026gt; void | Promise\u0026lt;void\u0026gt; } }\rComputed properties are passed into the initRelay function in an object where the keys are the names of the properties, and the value should be an object containing the following:\nget (required): It receives character data along with any number of string parameters and should return the computed value. tokenBarValue (optional): A boolean indicating whether this property should be available for use in token bars. description (optional): A text value indicating what this computed summary property represents. set (optional): This method receives character data and a dispatch, along with string arguments. This method does not need to return a value. Setting tokenBarValue to true will make the property available to use as a value for token bars. To work correctly, the get function must not rely on any additional arguments and must return either a simple value (a string or number) or an object: { current: number | string, max: number | string }\rIf the set function is omitted, the value will not be editable from the token itself. If defined, set methods will receive one string argument, which is whatever the user types into the input for modifying the bar. ","date":"2024-04-07","id":11,"permalink":"/beacon-docs/docs/components/computed/","summary":"Sheet authors define computed properties that are accessed by the host. These computed properties can be used as attributes in macros and are available to assign as values to token bars - if the tokenBarValue property is set to true.","tags":[],"title":"Computed"},{"content":"Handler functions allow the sheet to respond to messages from the host. The handlers argument requires the following methods:\nonInit The onInit function provides the initial set of data to the sheet.\nonInit(e: { character: Character, settings: { colorTheme: string, language: string, gm: boolean, owned: boolean, settingsSheet: boolean, headless: boolean, sandbox: boolean, campaignId: number, environment: string, currentUserId: string, singleSheet: boolean }, sharedSettings: {}, compendiumDropData: { pageName: string, categoryName: string, expansion: number } }, dispatch: Dispatch): void;\rThe event object contains the following:\ncharacter: The primary character for this sheet. settings: Campaign and character-specific settings. sharedSettings: Data shared between all characters in this campaign. compendiumDropData: Populated when the character sheet is created from a compendium entry such as a creature or NPC. This function may be called multiple times during development in the sheet sandbox as part of hot reloads.\nonChange onChange is called whenever a character’s data is changed on the host’s end. The event object contains a partial character with only the character’s ID and the changed data. This could be the character’s bio, GM notes, or attributes (only the changed attributes).\nonChange(e: { character: Partial\u0026lt;Character\u0026gt; }, dispatch: Dispatch): void;\ronSettingsChange onSettingsChange is called when either the VTT’s color theme is changed, or when the current player’s ownership of the primary character changes.\nonSettingsChange(e: { colorTheme: string, owned: boolean }, dispatch: Dispatch): void;\ronSharedSettingsChange onSharedSettingsChange is called when someone changes a shared setting in the VTT.\nonSharedSettingsChange({ settings: { [key: string]: any } }): void;\ronTranslationsRequest onTranslationsRequest is called before the relay is fully initialized and returns the translation JSON data corresponding to the two-letter language argument.\nonTranslationsRequest(language: string): { [key: string]: string };\ronDragOver (optional) onDragOver is called when a compendium item from the compendium tab is dragged over the iframe window containing the character sheet.\nCoordinates of the drag are provided via top and left values, and basic compendium data is passed so that a subsequent compendium request can be made via the provided dispatch. If the item is moved outside of the iframe, dragData and coordinates are null.\nonDragOver(e: { coordinates: { top: number, left: number }, dragData: { pageName: string, categoryName: string, expansionId: number } | null }, dispatch: Dispatch): void\ronDropOver (optional) onDropOver is called when a compendium item from the compendium tab is dropped over the iframe window containing the character sheet.\nCoordinates of the drop are provided via top and left values, and basic compendium data is passed so that a subsequent compendium request can be made via the provided dispatch.\nonDropOver(e: { coordinates: { top: number, left: number }, dropData: { pageName: string, categoryName: string, expansionId: number } }, dispatch: Dispatch): void\r","date":"2024-03-07","id":12,"permalink":"/beacon-docs/docs/components/handlers/","summary":"Handler functions allow the sheet to respond to messages from the host. The handlers argument requires the following methods:\nonInit The onInit function provides the initial set of data to the sheet.","tags":[],"title":"Handlers"},{"content":"","date":"2024-02-07","id":13,"permalink":"/beacon-docs/docs/changelog/","summary":"","tags":[],"title":"Changelog"},{"content":"When utilizing Macros within the VTT, there are instances where a legacy macro might need to be employed for a Beacon sheet.\nThis scenario commonly arises when transitioning from an existing legacy sheet to a Beacon sheet. During such transitions, it\u0026rsquo;s possible that the attributes called from the legacy macro may not align with the structure of attributes in the Beacon Sheet.\nThe convertLegacyMacroAttributes function serves as a pivotal tool, empowering Sheet Developers to determine the mapping strategy for legacy attributes to the new Beacon Sheet.\nconvertLegacyMacroAttributes This function is defined during the initial SDK initialization process and is invoked by the host when it encounters a failure in locating an attribute\u0026rsquo;s value.\nconvertLegacyMacroAttributes: (messages: convertLegacyMacroAttributesArgs) =\u0026gt; {}: any\rAdvanced sheet macros typically first search through the defined computed properties before resorting to the convertLegacyMacroAttributes function.\nThe function\u0026rsquo;s purpose is to return a value that will be substituted in the macro. However, it grants Sheet Developers the autonomy to devise their preferred approach for handling legacy attribute values.\n","date":"2024-02-07","id":14,"permalink":"/beacon-docs/docs/components/handling-legacy-macro-attributes/","summary":"When utilizing Macros within the VTT, there are instances where a legacy macro might need to be employed for a Beacon sheet.","tags":[],"title":"Handling Legacy Macro Attributes"},{"content":"The VTT (Virtual Tabletop) has several new features that enhance the way rolls are handled and displayed. These features include attributes and elements that allow for dynamic roll results and interactivity within the VTT environment.\ndata-rollname The data-rollname attribute tells the VTT that this HTML element is displaying the result of a roll.\n\u0026lt;span data-rollname=\u0026#34;attack\u0026#34;\u0026gt;\u0026lt;/span\u0026gt;\rThe VTT will both add the Quantum Roll signature tooltip to the element and replace the contents of the element with the result from the roll.\nThis is the preferred method for displaying roll results wherever possible, that is, sending the whole roll formula to the roll server and allowing the VTT to display the result.\ndata-computed Tagging an element with both a data-rollname and a data-computed=\u0026quot;true\u0026quot; tells the VTT that this element is associated with a roll, but the results of that roll were computed by the author, as opposed to the roll server computing the result.\n\u0026lt;span data-rollname=\u0026#34;complex\u0026#34; data-computed=\u0026#34;true\u0026#34;\u0026gt;25\u0026lt;/span\u0026gt;\rThe VTT will add the Quantum Roll signature tooltip, but the content of the element will not be modified. Generally, this should only be used when the roll server does not support a particular dice mechanic.\nRoll Buttons Roll buttons are interactive elements that trigger sheet actions, such as damage rolls, when clicked. These buttons use the data-sheet-action attribute to specify the action to be executed.\n\u0026lt;button data-sheet-action=\u0026#34;damage\u0026#34; data-args=\u0026#34;arg1:arg2\u0026#34;\u0026gt;Click Me\u0026lt;/button\u0026gt;\rAdditional arguments can be provided using the data-args attribute, and the character, messageId, and original rolls will be included automatically.\n","date":"2024-01-07","id":15,"permalink":"/beacon-docs/docs/components/rolls/","summary":"The VTT (Virtual Tabletop) has several new features that enhance the way rolls are handled and displayed. These features include attributes and elements that allow for dynamic roll results and interactivity within the VTT environment.","tags":[],"title":"Rolls"},{"content":"","date":"2024-01-07","id":16,"permalink":"/beacon-docs/docs/tutorials/","summary":"","tags":[],"title":"Tutorials"},{"content":"Release Date: 2022-03-17\nNew Features Initial release of the Beacon SDK. Support for Vue.js framework. Setup with Vite for rapid development. Basic and advanced sheet examples. Improvements Detailed comments added to example files for better understanding. Support for complex roll templates and rich sheet actions. Bug Fixes N/A (initial release). Version 2.0.0 Release Date: 2023-03-17\nNew Features SCSS support for styling. Integration with Roll20 and VTT. Mock Relay for offline development. Improvements TypeScript integration for type checking and improved development experience. Unit testing with Vitest. End-to-End testing with Cypress. Bug Fixes N/A (initial release). ","date":"2024-01-07","id":17,"permalink":"/beacon-docs/docs/changelog/version-1.0.0/","summary":"Release Date: 2022-03-17\nNew Features Initial release of the Beacon SDK. Support for Vue.js framework. Setup with Vite for rapid development.","tags":[],"title":"Version 1.0.0"},{"content":"Prerequisites To set this sheet up properly, make sure that you have the following tools installed:\nVue.js Vite SCSS Figure 1: Quickstart sheet\nUse the following steps to get started:\nInstall the Beacon SDK: Run the following command. npm i @roll20-official/beacon-sdk\rInstall dependencies: Install the dependencies for the project. npm install\rStart the Vite server: After installing the project\u0026rsquo;s dependencies, you\u0026rsquo;ll need to start the Vite server. There are two ways to do this: a. Offline Development: This method will run the Vite server with the default port and environment set to development.\nnpm run dev\rOnce this code executes successfully, you can access the Vite server at http://localhost:5173.\nThis method is useful when you do not have access to the Roll20 website or would like to work on parts of your project that do not depend on a connection to the VTT or Roll20 Characters, such as working on styling, mocking up the environment, building Vue components, testing functionality, etc.\n::: info In development mode, you cannot save or access existing character data or use the Beacon SDK functions that depend on VTT or Roll20 Characters functionality, such as dice rolling and token manipulation. :::\nb. Sandbox Development: This method will run the Vite server with the port set to 7620 and the environment set to staging mode.\nnpm run sandbox\rThis command will build the SCSS files and then run the Vite server. This will set the server up for connecting to a VTT custom sheet sandbox as well as through the sandbox in Roll20 Characters.\nTo test your changes in the VTT custom sheet sandbox, you will need to add the following to the sheet.json editor in the game settings:\n{ \u0026#34;advanced\u0026#34;: true, \u0026#34;advancedPort\u0026#34;: 7620 }\rUseful Commands The following set of commands can come in handy when working with this sheet:\nFor Hot reloading and building CSS files, use the following command: npm run watch-scss\rFor linting, use the following command: npm run lint\rFor formatting with Prettier, use the following command: npm run format\r","date":"2024-05-07","id":18,"permalink":"/beacon-docs/docs/tutorials/beginner-beacon-sheet/","summary":"Prerequisites To set this sheet up properly, make sure that you have the following tools installed:\nVue.js Vite SCSS Figure 1: Quickstart sheet","tags":[],"title":"Beginner Beacon Sheet"},{"content":"Prerequisites To set this sheet up properly, make sure that you have the following tools installed:\nVue.js Vite SCSS Figure 1: Quickstart sheet\nUse the following steps to get started:\nInstall the Beacon SDK: Run the following command. npm i @roll20-official/beacon-sdk\rInstall dependencies: Install the dependencies for the project. npm install\rStart the Vite server: After installing the project\u0026rsquo;s dependencies, you\u0026rsquo;ll need to start the Vite server. There are two ways to do this: a. Offline Development: This method will run the Vite server with the default port and environment set to development.\nnpm run dev\rOnce this code executes successfully, you can access the Vite server at http://localhost:5173.\nThis method is useful when you do not have access to the Roll20 website or would like to work on parts of your project that do not depend on a connection to the VTT or Roll20 Characters, such as working on styling, mocking up the environment, building Vue components, testing functionality, etc.\nIn development mode, you cannot save or access existing character data or use the Beacon SDK functions that depend on VTT or Roll20 Characters functionality, such as dice rolling and token manipulation.\nb. Sandbox Development: This method will run the Vite server with the port set to 7620 and the environment set to staging mode.\nnpm run sandbox\rThis command will build the SCSS files and then run the Vite server. This will set the server up for connecting to a VTT custom sheet sandbox as well as through the sandbox in Roll20 Characters.\nTo test your changes in the VTT custom sheet sandbox, you will need to add the following to the sheet.json editor in the game settings:\n{ \u0026#34;advanced\u0026#34;: true, \u0026#34;advancedPort\u0026#34;: 7620 }\rUseful Commands The following set of commands can come in handy when working with this sheet:\nFor Hot reloading and building CSS files, use the following command: npm run watch-scss\rFor linting, use the following command: npm run lint\rFor formatting with Prettier, use the following command: npm run format\r","date":"2024-04-07","id":19,"permalink":"/beacon-docs/docs/quick/beginner-beacon-sheet/","summary":"Prerequisites To set this sheet up properly, make sure that you have the following tools installed:\nVue.js Vite SCSS Figure 1: Quickstart sheet","tags":[],"title":"Beginner Beacon Sheet"},{"content":"Prerequisites To set this sheet up properly, make sure that you have the following:\nVue framework \u0026amp; Routing Multiple Data Stores Complex Roll Templates Rich Sheet Actions TypeScript Vite SCSS Ability to run Unit \u0026amp; End-to-End Tests Figure 1: Advanced sheet\nThis sheet uses the same steps listed in the . Immediately after implementing those three steps, you\u0026rsquo;ll add the following step:\nRun a CI check: This will run several checks to ensure your code is as optimal as possible, including formatting, linting, type checking, unit tests, and end-to-end tests. npm run ci-check\rYou can think of this command as a sanity check you can leverage when pushing a big release for your sheet!\nUseful Commands The following set of commands can come in handy when working with this sheet:\nFor Hot reloading and building CSS files, use the following command: npm run watch-scss\rFor linting, use the following command: npm run lint\rFor formatting with Prettier, use the following command: npm run format\rFor type checking with TypeScript, use the following command: npm run type-check\rFor running unit tests with Vitest, use the following command: npm run test:unit\rTo open up and develop local end-to-end tests with Cypress, use the following command: npm run test:e2e:open:local\rFor running local end-to-end tests with Cypress, use the following command: npm run test:e2e:local\rTo run CDN-hosted end-to-end tests with Cypress, use the following command: npm run test:e2e\r","date":"2024-03-07","id":20,"permalink":"/beacon-docs/docs/quick/advanced-beacon-sheet/","summary":"Prerequisites To set this sheet up properly, make sure that you have the following:\nVue framework \u0026amp; Routing Multiple Data Stores Complex Roll Templates Rich Sheet Actions TypeScript Vite SCSS Ability to run Unit \u0026amp; End-to-End Tests Figure 1: Advanced sheet","tags":[],"title":"Advanced Beacon Sheet"},{"content":"We appreciate your interest in contributing to the Beacon SDK project. Here are some guidelines to help you get started:\nHow to Contribute Reporting Bugs If you find a bug, please report it by opening an issue in the GitHub repository. Provide as much detail as possible to help us understand and reproduce the issue.\nSuggesting Features We welcome suggestions for new features. Please open an issue in the GitHub repository with a detailed description of the feature you would like to see and why you think it would be useful.\nCode Contributions Fork the Repository: Create a personal fork of the project on GitHub.\nClone the Fork: Clone your fork to your local machine.\ngit clone Create a Branch: Create a new branch for your work.\ngit checkout -b feature-or-bugfix-description\rMake Changes: Make your changes to the codebase. Follow the existing code style and conventions.\nRun Tests: Ensure that all tests pass before submitting your changes.\nnpm run ci-check\rCommit Changes: Commit your changes with a descriptive commit message.\ngit commit -m \u0026#34;Description of your changes\u0026#34;\rPush Changes: Push your changes to your fork.\ngit push origin feature-or-bugfix-description\rCreate a Pull Request: Open a pull request from your fork to the main repository. Provide a detailed description of your changes and why they should be merged.\nRunning Tests Unit Tests: Run unit tests with Vitest.\nnpm run test:unit\rEnd-to-End Tests: Run End-to-End tests with Cypress.\nnpm run test:e2e\rCode Style Follow the existing code style and conventions.\nUse ESLint for linting.\nnpm run lint\rFormat code with Prettier.\nnpm run format\rCommunication GitHub Issues: Use GitHub issues for bug reports, feature requests, and questions. Pull Requests: Use GitHub pull requests to submit your code contributions. Thank you for contributing to the Beacon SDK project!\n","date":"2024-02-07","id":21,"permalink":"/beacon-docs/docs/guides/contributing-guide/","summary":"We appreciate your interest in contributing to the Beacon SDK project. Here are some guidelines to help you get started:","tags":[],"title":"Contributing Guide"},{"content":"","date":"2024-02-07","id":22,"permalink":"/beacon-docs/docs/quick/release-sheet/","summary":"","tags":[],"title":"Release Sheet"},{"content":"Link to valuable, relevant resources.\n","date":"2024-02-27","id":23,"permalink":"/beacon-docs/docs/resources/","summary":"Link to valuable, relevant resources.","tags":[],"title":"Resources"},{"content":"","date":"2023-09-07","id":24,"permalink":"/beacon-docs/docs/","summary":"","tags":[],"title":"Docs"},{"content":"","date":"2023-09-07","id":25,"permalink":"/beacon-docs/privacy/","summary":"","tags":[],"title":"Privacy Policy"},{"content":"","date":"2023-09-07","id":26,"permalink":"/beacon-docs/","summary":"","tags":[],"title":"Welcome to Beacon SDK"},{"content":"","date":"0001-01-01","id":27,"permalink":"/beacon-docs/categories/","summary":"","tags":[],"title":"Categories"},{"content":"","date":"0001-01-01","id":28,"permalink":"/beacon-docs/contributors/","summary":"","tags":[],"title":"Contributors"},{"content":"","date":"0001-01-01","id":29,"permalink":"/beacon-docs/tags/","summary":"","tags":[],"title":"Tags"}]
\ No newline at end of file
+[{"content":"Well-thought-through product announcements will help increase feature awareness and engage users with new functionality. Just like sharing your public roadmap, it\u0026rsquo;s also a great way to let potential customers see that you\u0026rsquo;re constantly improving.\nFurther reading Read How to announce product updates and features ","date":"2023-09-07","id":0,"permalink":"/blog/example-post/","summary":"You can use blog posts for announcing product updates and features.","tags":[],"title":"Example Post"},{"content":"","date":"2023-09-07","id":1,"permalink":"/blog/","summary":"","tags":[],"title":"Blog"},{"content":"","date":"2024-06-07","id":2,"permalink":"/docs/guides/","summary":"","tags":[],"title":"Getting Started"},{"content":"The Beacon SDK is a toolset designed to enhance and streamline the development of virtual tabletop (VTT) character sheets and other interactive elements.\nWhether you\u0026rsquo;re a game master (GM), a developer, or a player, the Beacon SDK provides a framework to create dynamic, responsive, and fully integrated VTT experiences.\nWhat is the Beacon SDK? The Beacon SDK is a specialized software development kit for virtual tabletops.\nIt facilitates creating and managing interactive character sheets, roll templates, macros, and other VTT functionalities.\nThe SDK ensures easy communication between the VTT platform and the character sheets, allowing real-time updates and interactions.\nKey Features Character Sheets: Design and implement detailed character sheets with dynamic attributes and real-time updates. Roll Mechanics: Integrate complex roll formulas and display roll results directly within the VTT. Macros: Create and manage macros for automated actions and roll calculations. Event Handling: Utilize a comprehensive set of handlers to manage various events and interactions within the VTT. Legacy Support: Convert and integrate legacy macros and roll templates with the new Beacon architecture. Customization: Define custom actions computed properties and handle specific roll templates tailored to your game\u0026rsquo;s needs. Components Overview The Beacon SDK is composed of several key components:\nActions: Define and manage custom actions that can be triggered within the VTT. Handlers: Event handlers that process and respond to various VTT events and messages. Computed Properties: Define dynamically computed properties based on other attributes. Macro Attributes: Convert and manage legacy macro attributes for compatibility with the Beacon SDK. Rolls: Implement advanced roll mechanics and display results dynamically within the VTT. For a comprehensive overview of these components, view the components section.\nGetting Started To get started with the Beacon SDK, you must initialize the relay, set up your character sheets, and define the necessary actions, handlers, and computed properties.\nThis documentation provides detailed guides and examples to help you through each step of the process.\nBy leveraging the Beacon SDK, you can create rich, interactive, fully integrated VTT experiences that enhance gameplay and streamline game management.\nWhether adapting existing character sheets or building new ones from scratch, the Beacon SDK offers the tools and flexibility to bring your virtual tabletop to life.\n","date":"2024-05-07","id":3,"permalink":"/docs/guides/introduction/","summary":"The Beacon SDK is a toolset designed to enhance and streamline the development of virtual tabletop (VTT) character sheets and other interactive elements.","tags":[],"title":"Introduction"},{"content":"Prerequisites Before you can install the Beacon SDK, you\u0026rsquo;ll need to have Node.js installed on your machine. If you don\u0026rsquo;t have Node.js installed, use the following steps in the official Node.js documentation.\nStep 1: Accessing Beacon SDK npm i @roll20-official/beacon-sdk\rStep 2: Install \u0026amp; Import The following steps will guide you in installing the package in your application:\nAdd the package to your package.json:\nUnder the dependencies object key of your package.json, add a new string key called @roll20/beacon-sdk with the version you want to install from our version history.\nFor example:\n{ \u0026#34;@roll20/beacon-sdk\u0026#34;: \u0026#34;0.0.0\u0026#34; }\rFor more information about installing packages, refer to the NPM documentation.\nRun npm install:\nOpen a terminal in the root of your application’s folder and run the following command:\nnpm install\rFor more information about NPM commands, refer to the NPM install documentation.\nImport the necessary package contents in your application:\nThe package exports various utilities you can use in your application. For example, you will need to utilize the initRelay function from the package.\nHere\u0026rsquo;s an import statement for that function:\nimport { initRelay } from \u0026#39;@roll20/beacon-sdk\u0026#39;;\rFor more information about imports, refer to the JavaScript import documentation.\n","date":"2024-04-07","id":4,"permalink":"/docs/guides/installation/","summary":"Prerequisites Before you can install the Beacon SDK, you\u0026rsquo;ll need to have Node.js installed on your machine. If you don\u0026rsquo;t have Node.","tags":[],"title":"Installation"},{"content":"Background: The background color of the alert box.\nCharacter: An entity in the game with attributes, bio, GM notes, and a token representation.\nCharacter sheet: A digital or printed page used to track a character\u0026rsquo;s attributes, abilities, and other relevant information in a role-playing game.\nComputed Property: Properties that have both get and set methods, which can be dynamically calculated.\nConvertLegacyMacroAttributes: A function to handle mapping legacy macro attributes to the new Beacon Sheet format.\nDispatch: A set of functions enabling the sheet to send commands back to the VTT.\nGM (Game Master): The person who runs the game, controls the NPCs \u0026amp; the story, and provides challenges for the players.\nHandler: Methods that act as event handlers to process messages from the host.\nInitRelay: Function to initialize the SDK relay, setting up communication between the host and the character sheet.\nMacro: A script that automates repetitive tasks in the VTT.\nRoll Template: A predefined format for displaying the results of a dice roll.\nToken: A visual representation of a character or object on the virtual tabletop, with various properties like position, size, and attributes.\nVTT (Virtual Tabletop): An online platform that allows players to play tabletop role-playing games over the internet.\nValidationMessage: A message displayed when an input value does not meet specific criteria.\nQuantum Roll: A system that ensures the fairness and authenticity of dice rolls in the VTT by using cryptographic methods.\n","date":"2024-03-07","id":5,"permalink":"/docs/guides/glossary/","summary":"Background: The background color of the alert box.\nCharacter: An entity in the game with attributes, bio, GM notes, and a token representation.","tags":[],"title":"Glossary"},{"content":"\rQ1: What are actions in the context of the VTT?\rActions are methods executed from the VTT, often used for rolls triggered from macros or chat buttons. They are defined in the sheet\u0026rsquo;s configuration and can interact with character data. Q2: How are computed properties used in the VTT?\rComputed properties are defined attributes accessible by the host, usable in macros, and assignable to token bars. They can represent derived values or complex calculations based on character data. Q3: What is the dispatch function used for?\rThe dispatch function provides methods for sending commands from the character sheet back to the host, including updating character data, performing actions, and interacting with the VTT interface. Q4: What are roll buttons, and how do they work?\rRoll buttons are HTML elements with specific attributes that execute designated sheet actions when clicked. They can pass arguments to the action method and are commonly used for triggering rolls from the character sheet. Q5: How are legacy macro attributes handled in the VTT?\rLegacy macro attributes can be mapped to the new sheet structure using the convertLegacyMacroAttributes function. Sheet developers can define how to handle legacy attribute values to ensure compatibility with existing macros. Q6: What is the purpose of the query function?\rThe query function displays a SweetAlert prompt to users and returns the results along with any errors. It is commonly used for interactive prompts or confirmations within the VTT interface. Q7: How are tokens managed in the VTT?\rTokens represent characters or objects on the virtual tabletop. Functions like getTokens, updateTokensByCharacter, and addToTracker are used to retrieve token information, update token data, and manage tokens in the turn tracker. Q8: What is the role of the convertLegacyMacroAttributesArgs type?\rThe convertLegacyMacroAttributesArgs type defines the arguments used for handling legacy macro attributes. It includes the attribute name, character ID, and character data needed for mapping legacy attributes to the new sheet structure. ","date":"2024-01-07","id":6,"permalink":"/docs/guides/faq/","summary":"Q1: What are actions in the context of the VTT?\rActions are methods executed from the VTT, often used for rolls triggered from macros or chat buttons.","tags":[],"title":"FAQ"},{"content":"The Beacon SDK is composed of various components that allow developers to create dynamic and interactive character sheets for virtual tabletop (VTT) games.\nThese components are crucial for handling actions, computations, macros, and rolls. This overview provides a high-level summary of each section, helping you understand their roles and how they integrate within the SDK.\nActions\rActions define specific operations that can be performed by characters within the VTT. These operations can range from simple tasks like rolling a dice to more complex interactions such as casting spells or activating abilities.\nHandlers\rHandlers are event listeners that manage communication between the VTT and the character sheet. They respond to various events, such as changes in character attributes or settings, and trigger appropriate actions or updates.\nComputed\rComputed properties are dynamic values derived from other character attributes. They allow for the creation of complex, calculated attributes that automatically update when their dependencies change.\nMacro Attributes\rMacro attributes handle the conversion of legacy macro attributes to the new format used in the Beacon SDK. This ensures compatibility with older character sheets and macros, allowing for a smooth transition to the new system.\nRolls\rThe Rolls component allows for advanced dice-rolling mechanics within the VTT. It supports both simple and complex rolls, providing flexibility in how roll results are displayed and computed.\n","date":"2024-06-07","id":7,"permalink":"/docs/components/overview/","summary":"The Beacon SDK is composed of various components that allow developers to create dynamic and interactive character sheets for virtual tabletop (VTT) games.","tags":[],"title":"Overview"},{"content":"Actions are a collection of methods that can be executed from the VTT. These actions are used for any rolls that may need to be triggered outside of the sheet itself, such as from a macro or a chat button. Generally, most or all of a sheet’s rolls should be defined as actions.\nactions: { [name: string]: { method: (props: { dispatch: Dispatch, character: Character, messageId?: string, rolls?: RollResults }, ...args: string[]): void | Promise\u0026lt;void\u0026gt; } }\rActions are passed into the initRelay function in an object, where the keys are the unique names of the actions, and the values are objects containing a method property (additional metadata fields may be added to this object in the future).\nThe method receives a props object containing the following properties:\ndispatch: A Dispatch object. character: The data of the character performing the action. Currently, the action will not receive the character’s bio or GM notes, regardless of whether the player has access to those fields. messageId (optional): A unique ID for an existing chat message. It\u0026rsquo;s included in actions triggered from chat buttons to provide context for the original roll. rolls (optional): Included when action is triggered from a chat button. Contains the roll results of the original roll. These functions can also receive an unlimited number of additional arguments. This is because these actions can be triggered by plain text via a macro. However, all additional arguments must be strings. Additionally, these functions can be synchronous or asynchronous and do not return a value.\n","date":"2024-05-07","id":8,"permalink":"/docs/components/actions/","summary":"Actions are a collection of methods that can be executed from the VTT. These actions are used for any rolls that may need to be triggered outside of the sheet itself, such as from a macro or a chat button.","tags":[],"title":"Actions"},{"content":"","date":"2024-05-07","id":9,"permalink":"/docs/quick/","summary":"","tags":[],"title":"Quick Start"},{"content":"","date":"2024-04-07","id":10,"permalink":"/docs/components/","summary":"","tags":[],"title":"Components"},{"content":"Sheet authors define computed properties that are accessed by the host. These computed properties can be used as attributes in macros and are available to assign as values to token bars - if the tokenBarValue property is set to true.\ncomputed: { [name: string]: { tokenBarValue?: boolean, description?: string, get: ( props: { character: Character }, ...args: string[] ) =\u0026gt; ComputedResult, set?: ( props: { character: Character, dispatch: Dispatch }, ...args: string[] ) =\u0026gt; void | Promise\u0026lt;void\u0026gt; } }\rComputed properties are passed into the initRelay function in an object where the keys are the names of the properties, and the value should be an object containing the following:\nget (required): It receives character data along with any number of string parameters and should return the computed value. tokenBarValue (optional): A boolean indicating whether this property should be available for use in token bars. description (optional): A text value indicating what this computed summary property represents. set (optional): This method receives character data and a dispatch, along with string arguments. This method does not need to return a value. Setting tokenBarValue to true will make the property available to use as a value for token bars. To work correctly, the get function must not rely on any additional arguments and must return either a simple value (a string or number) or an object: { current: number | string, max: number | string }\rIf the set function is omitted, the value will not be editable from the token itself. If defined, set methods will receive one string argument, which is whatever the user types into the input for modifying the bar. ","date":"2024-04-07","id":11,"permalink":"/docs/components/computed/","summary":"Sheet authors define computed properties that are accessed by the host. These computed properties can be used as attributes in macros and are available to assign as values to token bars - if the tokenBarValue property is set to true.","tags":[],"title":"Computed"},{"content":"Handler functions allow the sheet to respond to messages from the host. The handlers argument requires the following methods:\nonInit The onInit function provides the initial set of data to the sheet.\nonInit(e: { character: Character, settings: { colorTheme: string, language: string, gm: boolean, owned: boolean, settingsSheet: boolean, headless: boolean, sandbox: boolean, campaignId: number, environment: string, currentUserId: string, singleSheet: boolean }, sharedSettings: {}, compendiumDropData: { pageName: string, categoryName: string, expansion: number } }, dispatch: Dispatch): void;\rThe event object contains the following:\ncharacter: The primary character for this sheet. settings: Campaign and character-specific settings. sharedSettings: Data shared between all characters in this campaign. compendiumDropData: Populated when the character sheet is created from a compendium entry such as a creature or NPC. This function may be called multiple times during development in the sheet sandbox as part of hot reloads.\nonChange onChange is called whenever a character’s data is changed on the host’s end. The event object contains a partial character with only the character’s ID and the changed data. This could be the character’s bio, GM notes, or attributes (only the changed attributes).\nonChange(e: { character: Partial\u0026lt;Character\u0026gt; }, dispatch: Dispatch): void;\ronSettingsChange onSettingsChange is called when either the VTT’s color theme is changed, or when the current player’s ownership of the primary character changes.\nonSettingsChange(e: { colorTheme: string, owned: boolean }, dispatch: Dispatch): void;\ronSharedSettingsChange onSharedSettingsChange is called when someone changes a shared setting in the VTT.\nonSharedSettingsChange({ settings: { [key: string]: any } }): void;\ronTranslationsRequest onTranslationsRequest is called before the relay is fully initialized and returns the translation JSON data corresponding to the two-letter language argument.\nonTranslationsRequest(language: string): { [key: string]: string };\ronDragOver (optional) onDragOver is called when a compendium item from the compendium tab is dragged over the iframe window containing the character sheet.\nCoordinates of the drag are provided via top and left values, and basic compendium data is passed so that a subsequent compendium request can be made via the provided dispatch. If the item is moved outside of the iframe, dragData and coordinates are null.\nonDragOver(e: { coordinates: { top: number, left: number }, dragData: { pageName: string, categoryName: string, expansionId: number } | null }, dispatch: Dispatch): void\ronDropOver (optional) onDropOver is called when a compendium item from the compendium tab is dropped over the iframe window containing the character sheet.\nCoordinates of the drop are provided via top and left values, and basic compendium data is passed so that a subsequent compendium request can be made via the provided dispatch.\nonDropOver(e: { coordinates: { top: number, left: number }, dropData: { pageName: string, categoryName: string, expansionId: number } }, dispatch: Dispatch): void\r","date":"2024-03-07","id":12,"permalink":"/docs/components/handlers/","summary":"Handler functions allow the sheet to respond to messages from the host. The handlers argument requires the following methods:\nonInit The onInit function provides the initial set of data to the sheet.","tags":[],"title":"Handlers"},{"content":"","date":"2024-02-07","id":13,"permalink":"/docs/changelog/","summary":"","tags":[],"title":"Changelog"},{"content":"When utilizing Macros within the VTT, there are instances where a legacy macro might need to be employed for a Beacon sheet.\nThis scenario commonly arises when transitioning from an existing legacy sheet to a Beacon sheet. During such transitions, it\u0026rsquo;s possible that the attributes called from the legacy macro may not align with the structure of attributes in the Beacon Sheet.\nThe convertLegacyMacroAttributes function serves as a pivotal tool, empowering Sheet Developers to determine the mapping strategy for legacy attributes to the new Beacon Sheet.\nconvertLegacyMacroAttributes This function is defined during the initial SDK initialization process and is invoked by the host when it encounters a failure in locating an attribute\u0026rsquo;s value.\nconvertLegacyMacroAttributes: (messages: convertLegacyMacroAttributesArgs) =\u0026gt; {}: any\rAdvanced sheet macros typically first search through the defined computed properties before resorting to the convertLegacyMacroAttributes function.\nThe function\u0026rsquo;s purpose is to return a value that will be substituted in the macro. However, it grants Sheet Developers the autonomy to devise their preferred approach for handling legacy attribute values.\n","date":"2024-02-07","id":14,"permalink":"/docs/components/handling-legacy-macro-attributes/","summary":"When utilizing Macros within the VTT, there are instances where a legacy macro might need to be employed for a Beacon sheet.","tags":[],"title":"Handling Legacy Macro Attributes"},{"content":"The VTT (Virtual Tabletop) has several new features that enhance the way rolls are handled and displayed. These features include attributes and elements that allow for dynamic roll results and interactivity within the VTT environment.\ndata-rollname The data-rollname attribute tells the VTT that this HTML element is displaying the result of a roll.\n\u0026lt;span data-rollname=\u0026#34;attack\u0026#34;\u0026gt;\u0026lt;/span\u0026gt;\rThe VTT will both add the Quantum Roll signature tooltip to the element and replace the contents of the element with the result from the roll.\nThis is the preferred method for displaying roll results wherever possible, that is, sending the whole roll formula to the roll server and allowing the VTT to display the result.\ndata-computed Tagging an element with both a data-rollname and a data-computed=\u0026quot;true\u0026quot; tells the VTT that this element is associated with a roll, but the results of that roll were computed by the author, as opposed to the roll server computing the result.\n\u0026lt;span data-rollname=\u0026#34;complex\u0026#34; data-computed=\u0026#34;true\u0026#34;\u0026gt;25\u0026lt;/span\u0026gt;\rThe VTT will add the Quantum Roll signature tooltip, but the content of the element will not be modified. Generally, this should only be used when the roll server does not support a particular dice mechanic.\nRoll Buttons Roll buttons are interactive elements that trigger sheet actions, such as damage rolls, when clicked. These buttons use the data-sheet-action attribute to specify the action to be executed.\n\u0026lt;button data-sheet-action=\u0026#34;damage\u0026#34; data-args=\u0026#34;arg1:arg2\u0026#34;\u0026gt;Click Me\u0026lt;/button\u0026gt;\rAdditional arguments can be provided using the data-args attribute, and the character, messageId, and original rolls will be included automatically.\n","date":"2024-01-07","id":15,"permalink":"/docs/components/rolls/","summary":"The VTT (Virtual Tabletop) has several new features that enhance the way rolls are handled and displayed. These features include attributes and elements that allow for dynamic roll results and interactivity within the VTT environment.","tags":[],"title":"Rolls"},{"content":"","date":"2024-01-07","id":16,"permalink":"/docs/tutorials/","summary":"","tags":[],"title":"Tutorials"},{"content":"Release Date: 2022-03-17\nNew Features Initial release of the Beacon SDK. Support for Vue.js framework. Setup with Vite for rapid development. Basic and advanced sheet examples. Improvements Detailed comments added to example files for better understanding. Support for complex roll templates and rich sheet actions. Bug Fixes N/A (initial release). Version 2.0.0 Release Date: 2023-03-17\nNew Features SCSS support for styling. Integration with Roll20 and VTT. Mock Relay for offline development. Improvements TypeScript integration for type checking and improved development experience. Unit testing with Vitest. End-to-End testing with Cypress. Bug Fixes N/A (initial release). ","date":"2024-01-07","id":17,"permalink":"/docs/changelog/version-1.0.0/","summary":"Release Date: 2022-03-17\nNew Features Initial release of the Beacon SDK. Support for Vue.js framework. Setup with Vite for rapid development.","tags":[],"title":"Version 1.0.0"},{"content":"Prerequisites To set this sheet up properly, make sure that you have the following tools installed:\nVue.js Vite SCSS Figure 1: Quickstart sheet\nUse the following steps to get started:\nInstall the Beacon SDK: Run the following command. npm i @roll20-official/beacon-sdk\rInstall dependencies: Install the dependencies for the project. npm install\rStart the Vite server: After installing the project\u0026rsquo;s dependencies, you\u0026rsquo;ll need to start the Vite server. There are two ways to do this: a. Offline Development: This method will run the Vite server with the default port and environment set to development.\nnpm run dev\rOnce this code executes successfully, you can access the Vite server at http://localhost:5173.\nThis method is useful when you do not have access to the Roll20 website or would like to work on parts of your project that do not depend on a connection to the VTT or Roll20 Characters, such as working on styling, mocking up the environment, building Vue components, testing functionality, etc.\n::: info In development mode, you cannot save or access existing character data or use the Beacon SDK functions that depend on VTT or Roll20 Characters functionality, such as dice rolling and token manipulation. :::\nb. Sandbox Development: This method will run the Vite server with the port set to 7620 and the environment set to staging mode.\nnpm run sandbox\rThis command will build the SCSS files and then run the Vite server. This will set the server up for connecting to a VTT custom sheet sandbox as well as through the sandbox in Roll20 Characters.\nTo test your changes in the VTT custom sheet sandbox, you will need to add the following to the sheet.json editor in the game settings:\n{ \u0026#34;advanced\u0026#34;: true, \u0026#34;advancedPort\u0026#34;: 7620 }\rUseful Commands The following set of commands can come in handy when working with this sheet:\nFor Hot reloading and building CSS files, use the following command: npm run watch-scss\rFor linting, use the following command: npm run lint\rFor formatting with Prettier, use the following command: npm run format\r","date":"2024-05-07","id":18,"permalink":"/docs/tutorials/beginner-beacon-sheet/","summary":"Prerequisites To set this sheet up properly, make sure that you have the following tools installed:\nVue.js Vite SCSS Figure 1: Quickstart sheet","tags":[],"title":"Beginner Beacon Sheet"},{"content":"Prerequisites To set this sheet up properly, make sure that you have the following tools installed:\nVue.js Vite SCSS Figure 1: Quickstart sheet\nUse the following steps to get started:\nInstall the Beacon SDK: Run the following command. npm i @roll20-official/beacon-sdk\rInstall dependencies: Install the dependencies for the project. npm install\rStart the Vite server: After installing the project\u0026rsquo;s dependencies, you\u0026rsquo;ll need to start the Vite server. There are two ways to do this: a. Offline Development: This method will run the Vite server with the default port and environment set to development.\nnpm run dev\rOnce this code executes successfully, you can access the Vite server at http://localhost:5173.\nThis method is useful when you do not have access to the Roll20 website or would like to work on parts of your project that do not depend on a connection to the VTT or Roll20 Characters, such as working on styling, mocking up the environment, building Vue components, testing functionality, etc.\nIn development mode, you cannot save or access existing character data or use the Beacon SDK functions that depend on VTT or Roll20 Characters functionality, such as dice rolling and token manipulation.\nb. Sandbox Development: This method will run the Vite server with the port set to 7620 and the environment set to staging mode.\nnpm run sandbox\rThis command will build the SCSS files and then run the Vite server. This will set the server up for connecting to a VTT custom sheet sandbox as well as through the sandbox in Roll20 Characters.\nTo test your changes in the VTT custom sheet sandbox, you will need to add the following to the sheet.json editor in the game settings:\n{ \u0026#34;advanced\u0026#34;: true, \u0026#34;advancedPort\u0026#34;: 7620 }\rUseful Commands The following set of commands can come in handy when working with this sheet:\nFor Hot reloading and building CSS files, use the following command: npm run watch-scss\rFor linting, use the following command: npm run lint\rFor formatting with Prettier, use the following command: npm run format\r","date":"2024-04-07","id":19,"permalink":"/docs/quick/beginner-beacon-sheet/","summary":"Prerequisites To set this sheet up properly, make sure that you have the following tools installed:\nVue.js Vite SCSS Figure 1: Quickstart sheet","tags":[],"title":"Beginner Beacon Sheet"},{"content":"Prerequisites To set this sheet up properly, make sure that you have the following:\nVue framework \u0026amp; Routing Multiple Data Stores Complex Roll Templates Rich Sheet Actions TypeScript Vite SCSS Ability to run Unit \u0026amp; End-to-End Tests Figure 1: Advanced sheet\nThis sheet uses the same steps listed in the . Immediately after implementing those three steps, you\u0026rsquo;ll add the following step:\nRun a CI check: This will run several checks to ensure your code is as optimal as possible, including formatting, linting, type checking, unit tests, and end-to-end tests. npm run ci-check\rYou can think of this command as a sanity check you can leverage when pushing a big release for your sheet!\nUseful Commands The following set of commands can come in handy when working with this sheet:\nFor Hot reloading and building CSS files, use the following command: npm run watch-scss\rFor linting, use the following command: npm run lint\rFor formatting with Prettier, use the following command: npm run format\rFor type checking with TypeScript, use the following command: npm run type-check\rFor running unit tests with Vitest, use the following command: npm run test:unit\rTo open up and develop local end-to-end tests with Cypress, use the following command: npm run test:e2e:open:local\rFor running local end-to-end tests with Cypress, use the following command: npm run test:e2e:local\rTo run CDN-hosted end-to-end tests with Cypress, use the following command: npm run test:e2e\r","date":"2024-03-07","id":20,"permalink":"/docs/quick/advanced-beacon-sheet/","summary":"Prerequisites To set this sheet up properly, make sure that you have the following:\nVue framework \u0026amp; Routing Multiple Data Stores Complex Roll Templates Rich Sheet Actions TypeScript Vite SCSS Ability to run Unit \u0026amp; End-to-End Tests Figure 1: Advanced sheet","tags":[],"title":"Advanced Beacon Sheet"},{"content":"We appreciate your interest in contributing to the Beacon SDK project. Here are some guidelines to help you get started:\nHow to Contribute Reporting Bugs If you find a bug, please report it by opening an issue in the GitHub repository. Provide as much detail as possible to help us understand and reproduce the issue.\nSuggesting Features We welcome suggestions for new features. Please open an issue in the GitHub repository with a detailed description of the feature you would like to see and why you think it would be useful.\nCode Contributions Fork the Repository: Create a personal fork of the project on GitHub.\nClone the Fork: Clone your fork to your local machine.\ngit clone Create a Branch: Create a new branch for your work.\ngit checkout -b feature-or-bugfix-description\rMake Changes: Make your changes to the codebase. Follow the existing code style and conventions.\nRun Tests: Ensure that all tests pass before submitting your changes.\nnpm run ci-check\rCommit Changes: Commit your changes with a descriptive commit message.\ngit commit -m \u0026#34;Description of your changes\u0026#34;\rPush Changes: Push your changes to your fork.\ngit push origin feature-or-bugfix-description\rCreate a Pull Request: Open a pull request from your fork to the main repository. Provide a detailed description of your changes and why they should be merged.\nRunning Tests Unit Tests: Run unit tests with Vitest.\nnpm run test:unit\rEnd-to-End Tests: Run End-to-End tests with Cypress.\nnpm run test:e2e\rCode Style Follow the existing code style and conventions.\nUse ESLint for linting.\nnpm run lint\rFormat code with Prettier.\nnpm run format\rCommunication GitHub Issues: Use GitHub issues for bug reports, feature requests, and questions. Pull Requests: Use GitHub pull requests to submit your code contributions. Thank you for contributing to the Beacon SDK project!\n","date":"2024-02-07","id":21,"permalink":"/docs/guides/contributing-guide/","summary":"We appreciate your interest in contributing to the Beacon SDK project. Here are some guidelines to help you get started:","tags":[],"title":"Contributing Guide"},{"content":"","date":"2024-02-07","id":22,"permalink":"/docs/quick/release-sheet/","summary":"","tags":[],"title":"Release Sheet"},{"content":"Link to valuable, relevant resources.\n","date":"2024-02-27","id":23,"permalink":"/docs/resources/","summary":"Link to valuable, relevant resources.","tags":[],"title":"Resources"},{"content":"","date":"2023-09-07","id":24,"permalink":"/docs/","summary":"","tags":[],"title":"Docs"},{"content":"","date":"2023-09-07","id":25,"permalink":"/privacy/","summary":"","tags":[],"title":"Privacy Policy"},{"content":"","date":"2023-09-07","id":26,"permalink":"/","summary":"","tags":[],"title":"Welcome to Beacon SDK"},{"content":"","date":"0001-01-01","id":27,"permalink":"/categories/","summary":"","tags":[],"title":"Categories"},{"content":"","date":"0001-01-01","id":28,"permalink":"/contributors/","summary":"","tags":[],"title":"Contributors"},{"content":"","date":"0001-01-01","id":29,"permalink":"/tags/","summary":"","tags":[],"title":"Tags"}]
\ No newline at end of file
diff --git a/public/sitemap.xml b/public/sitemap.xml
index 17e3d7d..679ffea 100644
--- a/public/sitemap.xml
+++ b/public/sitemap.xml
@@ -2,150 +2,150 @@
- http://localhost:1313/beacon-docs/blog/example-post/
+ //localhost:1313/blog/example-post/2023-09-07T16:27:22+02:00monthly0.5
- http://localhost:1313/beacon-docs/blog/
+ //localhost:1313/blog/2023-09-07T16:21:44+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/guides/
+ //localhost:1313/docs/guides/2023-09-07T16:06:50+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/guides/introduction/
+ //localhost:1313/docs/guides/introduction/2024-01-07T16:04:48+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/guides/installation/
+ //localhost:1313/docs/guides/installation/2024-02-07T16:04:48+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/guides/glossary/
+ //localhost:1313/docs/guides/glossary/2024-02-07T16:04:48+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/guides/faq/
+ //localhost:1313/docs/guides/faq/2024-02-07T16:04:48+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/components/overview/
+ //localhost:1313/docs/components/overview/2023-09-07T16:12:37+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/components/actions/
+ //localhost:1313/docs/components/actions/2023-09-07T16:12:37+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/quick/
+ //localhost:1313/docs/quick/2023-09-07T16:12:37+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/components/
+ //localhost:1313/docs/components/2023-09-07T16:12:37+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/components/computed/
+ //localhost:1313/docs/components/computed/2023-09-07T16:12:37+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/components/handlers/
+ //localhost:1313/docs/components/handlers/2023-09-07T16:12:37+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/changelog/
+ //localhost:1313/docs/changelog/2023-09-07T16:12:37+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/components/handling-legacy-macro-attributes/
+ //localhost:1313/docs/components/handling-legacy-macro-attributes/2023-09-07T16:12:37+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/components/rolls/
+ //localhost:1313/docs/components/rolls/2023-09-07T16:12:37+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/tutorials/
+ //localhost:1313/docs/tutorials/2023-09-07T16:12:37+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/changelog/version-1.0.0/
+ //localhost:1313/docs/changelog/version-1.0.0/2023-09-07T16:12:37+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/tutorials/beginner-beacon-sheet/
+ //localhost:1313/docs/tutorials/beginner-beacon-sheet/2024-05-07T16:13:18+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/quick/beginner-beacon-sheet/
+ //localhost:1313/docs/quick/beginner-beacon-sheet/2024-05-07T16:13:18+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/quick/advanced-beacon-sheet/
+ //localhost:1313/docs/quick/advanced-beacon-sheet/2024-09-07T16:13:18+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/guides/contributing-guide/
+ //localhost:1313/docs/guides/contributing-guide/2024-09-07T16:13:18+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/quick/release-sheet/
+ //localhost:1313/docs/quick/release-sheet/2024-09-07T16:13:18+02:00monthly0.5
- http://localhost:1313/beacon-docs/docs/resources/
+ //localhost:1313/docs/resources/2024-02-27T09:30:56+01:00monthly0.5
- http://localhost:1313/beacon-docs/docs/
+ //localhost:1313/docs/2023-09-07T16:12:03+02:00monthly0.5
- http://localhost:1313/beacon-docs/privacy/
+ //localhost:1313/privacy/2023-09-07T17:19:07+02:00monthly0.5
- http://localhost:1313/beacon-docs/
+ //localhost:1313/2023-09-07T16:33:54+02:00monthly0.5
- http://localhost:1313/beacon-docs/categories/
+ //localhost:1313/categories/monthly0.5
- http://localhost:1313/beacon-docs/contributors/
+ //localhost:1313/contributors/monthly0.5
- http://localhost:1313/beacon-docs/tags/
+ //localhost:1313/tags/monthly0.5
diff --git a/public/tags/index.html b/public/tags/index.html
index 262d3ca..ac1afe6 100644
--- a/public/tags/index.html
+++ b/public/tags/index.html
@@ -1,55 +1,55 @@
-
+
-
-
-
+
+
+
-
+
-
-
+
+
Tags | Beacon SDK
-
+
-
+
-
+
-
+
-
+
@@ -60,7 +60,7 @@
"itemListElement": [
{
"@type": "ListItem",
- "item": "http://localhost:1313/beacon-docs/",
+ "item": "//localhost:1313/",
"name": "Welcome to Beacon Sdk",
"position": 1
},
@@ -85,7 +85,7 @@