diff --git a/app/components/ecosystem.js b/app/components/ecosystem.js
index 3b83a2f..3dd2b52 100644
--- a/app/components/ecosystem.js
+++ b/app/components/ecosystem.js
@@ -1,11 +1,5 @@
"use strict";
-
-
-// P A C K A G E
-
-import Component from "choo/component";
-
// V A R I A B L E S
const APPLICATIONS = require("./ecosystem/module-applications");
@@ -16,13 +10,7 @@ const LIGHTHOUSE = require("./ecosystem/submodule-lighthouse");
const REFLECTOR = require("./ecosystem/submodule-reflector");
const WALLET = require("./ecosystem/submodule-wallet");
-
-
-// P R O G R A M
-
-Ecosystem.prototype = Object.create(Component.prototype);
-
-Ecosystem.prototype.createElement = () => {
+export default function () {
return `
`;
};
-
-
-
-// E X P O R T
-
-module.exports = exports = Ecosystem;
-
-
-
-// H E L P E R S
-
-function Ecosystem() {
- if (!(this instanceof Ecosystem)) return new Ecosystem();
- Component.call(this);
-}
diff --git a/app/components/feature-links.js b/app/components/feature-links.js
index b406f4a..c1b565a 100644
--- a/app/components/feature-links.js
+++ b/app/components/feature-links.js
@@ -1,11 +1,5 @@
"use strict";
-
-
-// P A C K A G E
-
-import Component from "choo/component";
-
// V A R I A B L E
const links = [ // TODO: Update images
@@ -45,13 +39,7 @@ const links = [ // TODO: Update images
}
];
-
-
-// P R O G R A M
-
-FeaturedLinks.prototype = Object.create(Component.prototype);
-
-FeaturedLinks.prototype.createElement = () => {
+export default function () {
const renderedLinks = [];
let imageLink = "";
@@ -65,21 +53,6 @@ FeaturedLinks.prototype.createElement = () => {
`;
};
-
-
-// E X P O R T
-
-module.exports = exports = FeaturedLinks;
-
-
-
-// H E L P E R S
-
-function FeaturedLinks() {
- if (!(this instanceof FeaturedLinks)) return new FeaturedLinks();
- Component.call(this);
-}
-
function returnLinkTemplate(url, title, image) {
return `
diff --git a/app/views/redirect.js b/app/views/redirect.js
index 67b164b..4244f13 100644
--- a/app/views/redirect.js
+++ b/app/views/redirect.js
@@ -145,13 +145,8 @@ function partialFinder(markdownBody) {
if (fileExistsTest) {
const partialFunction = require(path.join(__dirname, "..", `./components/${filename}.js`));
-
- if (filename === "ecosystem" || filename === "feature-links") {
- const neatPartial = new partialFunction;
- markdownBody = markdownBody.replace(partial, neatPartial.render());
- }
-
- else if (filename === "glossary-toc") markdownBody = markdownBody.replace(partial, partialFunction);
+
+ if (filename === "glossary-toc") markdownBody = markdownBody.replace(partial, partialFunction);
else markdownBody = markdownBody.replace(partial, partialFunction.default());
}
diff --git a/documents/glossary.md b/documents/glossary.md
index ed0e586..03fed37 100644
--- a/documents/glossary.md
+++ b/documents/glossary.md
@@ -36,9 +36,9 @@ Chainquery provides a SQLized view of the LBRY blockchain. The model of Chainque
Informal name for a portion of a *transaction output* that is returned to a sender as a "change" after spending that output. Since *transaction outputs* cannot be partially spent, one can spend 1 BTC out of 3 BTC output only be creating two new outputs: a "payment" output with 1 BTC sent to a payee address, and a "change" output with remaining 2 BTC (minus *transaction fees*) sent to the payer's addresses.
-### Channel Claim Signature
+### Channel Claim / Signature
-Creating a channel claim certificate allows you to group and identify claims based on an identity. A certificate is used to sign the claims and ensure uniqueness along with the claim ID. See [channel signing](https://lbry.tech/resources/signing-claim) for more information
+Creating a channel claim certificate allows you to group and identify claims based on an identity. A certificate is used to sign the claims and ensure uniqueness along with the claim ID. See [channel signing](https://github.com/lbryio/lbryschema/blob/master/docs/signing.md) for more information
### Claim
@@ -48,10 +48,6 @@ A claim (ClaimTrie) is the data structure which LBRY uses to store claims to nam
When creating a channel claim or publishing content onto the LBRY blockchain, a small amount (or more) LBC must be deposited to reserve the name space in the claimtrie. See our [naming documentation](https://lbry.io/faq/naming) for more information.
-### Claim Sequence
-
-The claim sequence provides a way to tell which order a claim was created at a particular claim name and enables claim resolutions via this modifier. If someone had the first claim at lbry://one, you could always reference your claim as lbry://one:1. See [URI documentation](https://lbry.tech/resources/uri) for more details.
-
### Claim Support
A special type of transaction that includes claim information, a LBC address and a LBC value. Supports to one's own address increase the bid value of a claim and can be revoked anytime. Supports to an outside address also increase the value, but can only be revoked by the receiver (tip mechanism).
diff --git a/documents/resources/schema.md b/documents/resources/schema.md
index d7c946d..af38a02 100644
--- a/documents/resources/schema.md
+++ b/documents/resources/schema.md
@@ -1,15 +1,8 @@
# Schema
-The schema defines the structure of the data that is stored in claims in the LBRY blockchain. It has several goals:
-
-- **Extensibility**. The schema could grow to encompass thousands of fields for dozens of types of content. It should be easy to modify the schema while maintaining backward compatibility. Blockchain data is permanent and cannot be migrated, so any selected data structure will have to be maintained forever.
-- **Compactness**. Blockchain space is expensive. Data should be stored as compactly as possible.
-- **Cross-language Interop**. These definitions will be used by many projects written in different languages.
-
-
## [Claim](https://github.com/lbryio/lbryschema/blob/master/lbryschema/proto/claim.proto)
-A `Claim` is the toplevel schema for everything that is published to the blockchain.
+A `Claim` is the toplevel schema for everything that is published to the LBRY blockchain.
```protobuf
message Claim {