development_blog #53
BIN
src/assets/images/blog/current_applications.png
Normal file
After Width: | Height: | Size: 159 KiB |
BIN
src/assets/images/blog/current_call.png
Normal file
After Width: | Height: | Size: 1.6 MiB |
BIN
src/assets/images/blog/current_model.png
Normal file
After Width: | Height: | Size: 501 KiB |
BIN
src/assets/images/blog/current_network.png
Normal file
After Width: | Height: | Size: 406 KiB |
BIN
src/assets/images/blog/how_to_test_the_grid_part_two.png
Normal file
After Width: | Height: | Size: 784 KiB |
BIN
src/assets/images/blog/navigating_levels.png
Normal file
After Width: | Height: | Size: 269 KiB |
BIN
src/assets/images/blog/testing_cycle.png
Normal file
After Width: | Height: | Size: 45 KiB |
BIN
src/assets/images/blog/testing_main.png
Normal file
After Width: | Height: | Size: 633 KiB |
BIN
src/assets/images/blog/testing_roadmap.jpg
Normal file
After Width: | Height: | Size: 45 KiB |
BIN
src/assets/images/blog/the_farming_community.png
Normal file
After Width: | Height: | Size: 556 KiB |
BIN
src/assets/images/blog/three_layers.png
Normal file
After Width: | Height: | Size: 338 KiB |
BIN
src/assets/images/blog/threefold_applications.png
Normal file
After Width: | Height: | Size: 58 KiB |
BIN
src/assets/images/blog/threefold_call.png
Normal file
After Width: | Height: | Size: 622 KiB |
BIN
src/assets/images/blog/threefold_network.png
Normal file
After Width: | Height: | Size: 173 KiB |
@ -4,28 +4,31 @@ import { Icon } from 'astro-icon/components';
|
||||
export interface Props {
|
||||
title?: string;
|
||||
content?: string;
|
||||
link?: string;
|
||||
linkpath?: string;
|
||||
linktitle?: string;
|
||||
}
|
||||
|
||||
const {
|
||||
title = await Astro.slots.render('title'),
|
||||
content = await Astro.slots.render('content'),
|
||||
linktitle = await Astro.slots.render('linktitle'),
|
||||
linkpath = await Astro.slots.render('linkpath'),
|
||||
} = Astro.props;
|
||||
|
||||
---
|
||||
|
||||
<section class="bg-blue-50 dark:bg-slate-800 not-prose">
|
||||
<div class="max-w-6xl mx-auto px-4 sm:px-6 py-4 text-md text-center font-medium">
|
||||
<span class="font-bold">
|
||||
<Icon name="tabler:info-square" class="w-5 h-5 inline-block align-text-bottom" /> {title}</span
|
||||
> {content}
|
||||
</div>
|
||||
<a
|
||||
target="_blank"
|
||||
class="ltr:ml-auto rtl:mr-auto ml-auto bg-contain inline-block"
|
||||
title="{linktitle}."
|
||||
href="{link}"
|
||||
>
|
||||
{content}
|
||||
<a
|
||||
href={linkpath}
|
||||
target="_blank"
|
||||
class="text-blue-500 ltr:ml-auto rtl:mr-auto ml-auto bg-contain inline-block"
|
||||
title=""
|
||||
>
|
||||
{linktitle}
|
||||
</a>
|
||||
</div>
|
||||
</section>
|
||||
|
@ -1,207 +0,0 @@
|
||||
---
|
||||
publishDate: 2023-07-17T00:00:00Z
|
||||
title: AstroWind template in depth
|
||||
excerpt: While easy to get started, Astrowind is quite complex internally. This page provides documentation on some of the more intricate parts.
|
||||
image: https://images.unsplash.com/photo-1534307671554-9a6d81f4d629?ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D&auto=format&fit=crop&w=1651&q=80
|
||||
category: Documentation
|
||||
tags:
|
||||
- astro
|
||||
- tailwind css
|
||||
- front-end
|
||||
metadata:
|
||||
canonical: https://astrowind.vercel.app/astrowind-template-in-depth
|
||||
---
|
||||
|
||||
import DListItem from '~/components/ui/DListItem.astro';
|
||||
import ToggleTheme from '~/components/common/ToggleTheme.astro';
|
||||
|
||||
## Overview
|
||||
|
||||
It can be a somewhat daunting task trying to get a handle on _AstroWind_ internals, and particularly various points of usage.
|
||||
|
||||
This page outlines and clarifies some of the techniques found in _AstroWind_. Use it as a guide for further modification, or an instructional for techniques to use in your own endeavors.
|
||||
|
||||
## Styling
|
||||
|
||||
As the name suggests, _AstroWind_ relies on _TailWind_ for styling. Furthermore, _AstroWind_ defines custom low level style settings which are incorporated into _TailWind_ seamlessly, and which provides consistency for higher level styling constructs, as well as enabling dark mode.
|
||||
|
||||
The styling mechanism consists of the following files (all paths are prefixed with `/src/` ):
|
||||
|
||||
<DListItem dt="assets/styles/tailwind.css">
|
||||
This file is essentially an extension of _TailWind's_ base.css. High-level component styles are defined here. Note
|
||||
also styling on elements selected by 'attribute' selectors at the bottom of the files, particularly those selected by
|
||||
'data' attributes.
|
||||
</DListItem>
|
||||
<DListItem dt="components/CustomStyles.astro">
|
||||
Defines custom colors and fonts. For these to take effect in the 'base.css' file, they need to be loaded in the html
|
||||
header section. See next.
|
||||
</DListItem>
|
||||
<DListItem dt="layouts/Layout.astro">
|
||||
This layout is used for all of the pages rendered by _AstroWind_. The contents of _tailwind.css_ and
|
||||
_CustomStyles.astro_ component, described above, is injected into the html header.
|
||||
</DListItem>
|
||||
|
||||
### Dark Mode
|
||||
|
||||
_Dark Mode_ is triggered by the little 'sunlight' icon:<ToggleTheme/>in the page header. It is defined in the _components/common/ToggleTheme.astro_, but the event is attached and the action defined in _components/common/BasicScripts.astro_ in the following snippet:
|
||||
|
||||
```javascript
|
||||
attachEvent('[data-aw-toggle-color-scheme]', 'click', function () {
|
||||
if (defaultTheme.endsWith(':only')) {
|
||||
return;
|
||||
}
|
||||
document.documentElement.classList.toggle('dark');
|
||||
localStorage.theme = document.documentElement.classList.contains('dark') ? 'dark' : 'light';
|
||||
});
|
||||
```
|
||||
|
||||
Note that this is a client event. _BasicScripts.astro_ defines several other client-side functionality as well as this one.
|
||||
|
||||
## Advanced Slot Usage
|
||||
|
||||
_slots_ are part of the component implementation, which is a common concept among many frameworks, including _Astrojs_. The typical slot definition in a component looks like this:
|
||||
|
||||
```astro
|
||||
---
|
||||
// (file: MyComponent.astro)
|
||||
const { title } = Astro.props;
|
||||
export interface Props {
|
||||
title: string;
|
||||
}
|
||||
---
|
||||
|
||||
<div>
|
||||
<h2>{title}</h2>
|
||||
<slot />
|
||||
<!-- slot contents injected here -->
|
||||
<div></div>
|
||||
</div>
|
||||
```
|
||||
|
||||
And in usage elsewhere:
|
||||
|
||||
```astro
|
||||
import MyComponent from "~/components/MyComponent"; ...
|
||||
<MyComponent someArg="A Slot example">
|
||||
<p>This content will be displayed in the slot</p>
|
||||
</MyComponent>
|
||||
```
|
||||
|
||||
### Alternate usage
|
||||
|
||||
There's another way we can use slots, useful particularly when a component can have markdown content is as follows (study carefully...):
|
||||
|
||||
```astro
|
||||
---
|
||||
// (file: MyComponent.astro)
|
||||
|
||||
const { title } = Astro.props;
|
||||
export interface Props {
|
||||
title: string;
|
||||
}
|
||||
const content: string = await Astro.props.render('default');
|
||||
---
|
||||
|
||||
// renders the html to the 'content' variable
|
||||
<div>
|
||||
<h2>{title}</h2>
|
||||
<div set:html={content} />
|
||||
<!-- slot contents injected here -->
|
||||
<div></div>
|
||||
</div>
|
||||
```
|
||||
|
||||
Whoa!! What's going on here?
|
||||
|
||||
Notice there is no slot definition in the html portion of the component. Instead, what we do is have _Astro_ render the slot content (here, the 'default' content, but you can also render named slots) into a variable, and then use that content in a _div_ (for instance).
|
||||
|
||||
So, if the usage is in a markdown file, like so:
|
||||
|
||||
```mdx
|
||||
import MyComponent from '../../components/MyComponent';
|
||||
|
||||
# Using the above component in a .mdx file (that can take components)
|
||||
|
||||
{' '}
|
||||
|
||||
<MyComponent title="This is a slot implementor">### Here is some markdown content - With a bullet item.</MyComponent>
|
||||
```
|
||||
|
||||
_MyComponent_ renders the markdown to html and then injects it into the div.
|
||||
|
||||
This actually has a big advantage -- consider that with the normal usage you don't have access to the slot contents: _Astro_ just plops the content into the _<slot/>_ tag. Using this method, however, allows you to access the content and further manipulate it before it gets inserted into the html.
|
||||
|
||||
This allows a great deal of flexibility in component design.
|
||||
|
||||
### Yet Another Step
|
||||
|
||||
Now, we get to the techniques used in _AstroWind_, we'll use the _pages/index.astro_ file to illustrate.
|
||||
|
||||
You'll note that the index file imports a lot of components, each one roughly analagous to a panel in the index page. Each of these components, in turn, is instantiated sequentially throughout the page. But, you'll notice that some of them use this kind of construct (we'll use the last section, _CallToAction_, as it is most illustrative of the technique):
|
||||
|
||||
```astro
|
||||
<CallToAction
|
||||
callToAction={{
|
||||
text: 'Get template',
|
||||
href: 'https://github.com/onwidget/astrowind',
|
||||
icon: 'tabler:download',
|
||||
}}
|
||||
>
|
||||
<Fragment slot="title">
|
||||
Astro + <br class="block sm:hidden" /><span class="sm:whitespace-nowrap">Tailwind CSS</span>
|
||||
</Fragment>
|
||||
|
||||
<Fragment slot="subtitle">
|
||||
Be very surprised by these huge fake numbers you are seeing on this page. <br class="hidden md:inline" />Don't waste
|
||||
more time! :P
|
||||
</Fragment>
|
||||
</CallToAction>
|
||||
```
|
||||
|
||||
Some things to note, here:
|
||||
|
||||
<DListItem dt="The <em>callToAction</em> argument">
|
||||
This argument is actually being passed a javascript object -- not a string. (However, in the TS definition, it could
|
||||
be a string...)
|
||||
</DListItem>
|
||||
<DListItem dt="There are several <em>Fragment</em> children">
|
||||
Furthermore, these <Fragment/> elements each have a _slot="(value)"_ specifier.
|
||||
</DListItem>
|
||||
|
||||
The latter seems odd, because <Fragment/> is a built-in component over which you have no control, and doesn't have a provision for rendering slots, <em>per se</em>.
|
||||
|
||||
The answer lies in a paragraph in the _Astro_ docs, slots section, which states:
|
||||
|
||||
> Use a `slot="my-slot"` attribute on the child element that you want to pass through to a matching slot `name="my-slot" />` placeholder in your component.
|
||||
|
||||
That's pretty concise and a bit of a head-scratcher to read, but basically what it says is that:
|
||||
|
||||
1. Given a component that defines a slot:
|
||||
1. you can reference a slot from a child element of that component and,
|
||||
1. provide content to the parent component's slot from the child by naming the slot in the child with a `slot="<slot-name>"` property assignment, where the _slot-name_ is the parent's slot.
|
||||
|
||||
So, in the example above, the _CallToAction_ component defines the _subtitle_ slot, and the following _<Fragment slot="subtitle">_ populates the slot with the following content:
|
||||
|
||||
```astro
|
||||
<Fragment slot="subtitle">
|
||||
Be very surprised by these huge fake numbers you are seeing on this page. <br class="hidden md:inline" />Don't waste
|
||||
more time! :P
|
||||
</Fragment>
|
||||
```
|
||||
|
||||
And, the _CallToAction_ component defines and renders it thusly:
|
||||
|
||||
```astro
|
||||
---
|
||||
//...
|
||||
const { subtitle = await Astro.slots.render('subtitle') } = Astro.props;
|
||||
---
|
||||
|
||||
//...
|
||||
{subtitle && <p class="text-xl text-muted dark:text-slate-400" set:html={subtitle} />}
|
||||
//...
|
||||
```
|
||||
|
||||
There's a lot to wrap your head around, here.
|
||||
|
||||
Notice first that _subtitle_ is defined as a prop/argument, but it's being processed as a slot. Interestingly, prop args and slots seem to be somewhat interchangeable: if the subtitle was just a string, it would simply take that assignment. The main difference is that if you render them independently, you have to call the render with an _await_ modifier.
|
@ -1,51 +0,0 @@
|
||||
---
|
||||
publishDate: 2023-08-12T00:00:00Z
|
||||
author: John Smith
|
||||
title: Get started with AstroWind to create a website using Astro and Tailwind CSS
|
||||
excerpt: Start your web journey with AstroWind – harness Astro and Tailwind CSS for a stunning site. Explore our guide now.
|
||||
image: https://images.unsplash.com/photo-1516996087931-5ae405802f9f?ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D&auto=format&fit=crop&w=2070&q=80
|
||||
category: Tutorials
|
||||
tags:
|
||||
- astro
|
||||
- tailwind css
|
||||
metadata:
|
||||
canonical: https://astrowind.vercel.app/get-started-website-with-astro-tailwind-css
|
||||
---
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
|
||||
|
||||
## Nostra torquent consequat volutpat aliquet neque
|
||||
|
||||
Lorem ipsum dolor sit amet consectetur adipiscing elit proin, aenean litora volutpat urna egestas magnis arcu non, cras ut cursus et sed morbi lectus. Integer faucibus sagittis eu nunc urna aliquet a laoreet torquent, suspendisse penatibus nulla sollicitudin congue rutrum dictum. Ornare mi habitasse fermentum phasellus dui et morbi litora sodales dictum id erat, nibh purus class ligula aenean lectus venenatis euismod cras torquent ac. Senectus sagittis conubia hendrerit at egestas porta venenatis nisi metus gravida tempor, aenean facilisis nisl ante facilisi lacus integer hac iaculis purus. Scelerisque libero torquent egestas curae tellus viverra inceptos imperdiet urna, porta suspendisse interdum primis odio morbi tempor commodo dictumst, suscipit ornare habitasse semper feugiat cras quisque lobortis.
|
||||
|
||||
Iaculis arcu commodo dis proin vitae himenaeos, ante tristique potenti magna ligula, sagittis libero fermentum ullamcorper sociis. Sem eros non arcu natoque fringilla lacus vestibulum lacinia integer mus viverra in proin, sagittis fusce tortor erat enim rutrum vulputate curae laoreet class diam. Inceptos convallis ac nisi natoque nam quisque magnis ut nullam fringilla curae, luctus lacus purus habitant erat magna molestie class habitasse metus, nibh lobortis tortor curabitur neque phasellus feugiat netus morbi parturient. Neque malesuada mauris justo himenaeos pharetra, ullamcorper enim ligula a nulla consequat, eget vivamus velit ridiculus.
|
||||
|
||||
## Praesent tellus ad sapien erat or
|
||||
|
||||
- Quam orci nostra mi nulla, hac a.
|
||||
|
||||
- Interdum iaculis quis tellus sociis orci nulla, quam rutrum conubia tortor primis.
|
||||
|
||||
- Non felis sem placerat aenean duis, ornare turpis nostra.
|
||||
|
||||
- Habitasse duis sociis sagittis cursus, ante dictumst commodo.
|
||||
|
||||
Duis maecenas massa habitasse inceptos imperdiet scelerisque at condimentum ultrices, nam dui leo enim taciti varius cras habitant pretium rhoncus, ut hac euismod nostra metus sagittis mi aenean. Quam eleifend aliquet litora eget a tempor, ultricies integer vestibulum non felis sodales, eros diam massa libero iaculis.
|
||||
|
||||
Nisl ligula ante magnis himenaeos pellentesque orci cras integer urna ut convallis, id phasellus libero est nunc ultrices eget blandit massa ac hac, morbi vulputate quisque tellus feugiat conubia luctus tincidunt curae fermentum. Venenatis dictumst tincidunt senectus vivamus duis dis sociis taciti porta primis, rhoncus ridiculus rutrum curae mattis ullamcorper ac sagittis nascetur curabitur erat, faucibus placerat vulputate eu at habitasse nulla nisl interdum. Varius turpis dignissim montes ac ante tristique quis parturient hendrerit faucibus, consequat auctor penatibus suspendisse rutrum erat nulla inceptos est justo, etiam mollis mauris facilisi cras sociosqu eu sapien sed.
|
||||
|
||||
Blandit aptent conubia mollis mauris habitasse suspendisse torquent aenean, ac primis auctor congue cursus mi posuere molestie, velit elementum per feugiat libero dictumst phasellus. Convallis mollis taciti condimentum praesent id porttitor ac dictumst at, sed in eu eleifend vehicula fermentum lectus litora venenatis, gravida hac molestie cum sociosqu mus viverra torquent. Congue est fusce habitasse ridiculus integer suscipit platea volutpat, inceptos varius elementum pellentesque malesuada interdum magnis. Hac lacus eget enim purus massa commodo nec lectus natoque fames arcu, mattis class quam ut neque dui cras quis diam orci sed velit, erat morbi eros suscipit sagittis laoreet vivamus torquent nulla turpis.
|
||||
|
||||
Ridiculus velit suscipit consequat auctor interdum magna gravida dictumst libero ut habitasse, sollicitudin vehicula suspendisse leo erat tristique at platea sagittis proin dignissim, id ornare scelerisque et urna maecenas congue tincidunt dictum malesuada. Dui vulputate accumsan scelerisque ridiculus dictum quisque et nam hac, tempus ultricies curabitur proin netus diam vivamus. Vestibulum ante ac auctor mi urna risus lacinia vulputate justo orci sociis dui semper, commodo morbi enim vivamus neque sem pellentesque velit donec hac metus odio. Tempor ultrices himenaeos massa sollicitudin mus conubia scelerisque cubilia, nascetur potenti mauris convallis et lectus gravida egestas sociis, erat eros ultricies aptent congue tortor ornare.
|
||||
|
||||
Pretium aliquet sodales aliquam tincidunt litora lectus, erat dui nibh diam mus, sed hendrerit condimentum senectus arcu. Arcu a nibh auctor dapibus eros turpis tempus commodo, libero hendrerit dictum interdum mus class sed scelerisque, sapien dictumst enim magna molestie habitant donec. Fringilla dui sed curabitur commodo varius est vel, viverra primis habitant sapien montes mattis dignissim, gravida cubilia laoreet tempus aliquet senectus. Sociosqu purus praesent porttitor curae sollicitudin accumsan feugiat maecenas donec quis lacus, suscipit taciti convallis odio morbi eros nibh bibendum nunc orci. Magna cras nullam aliquam metus nibh sagittis facilisi tortor nec, mus varius curae ridiculus fames congue interdum erat urna, neque odio lobortis mi mattis diam cubilia arcu.
|
||||
|
||||
Laoreet fusce nec class porttitor mus proin aenean, velit vestibulum feugiat porta egestas sapien posuere, conubia nisi tempus varius hendrerit tortor. Congue aliquam scelerisque neque vivamus habitasse semper mauris pellentesque accumsan posuere, suspendisse lectus gravida erat sagittis arcu praesent mus ornare. Habitasse nibh nam morbi mollis senectus erat risus, cum sollicitudin class platea congue mattis venenatis, luctus aenean parturient hendrerit malesuada ante. Mus auctor tincidunt consequat massa tortor nulla luctus habitasse vestibulum quis velit, laoreet sagittis cum facilisi in sem tellus leo vulputate vehicula bibendum orci, felis nisl blandit lacus convallis congue turpis magna facilisis condimentum.
|
||||
|
||||
Dictumst pellentesque urna donec sociis suscipit montes consequat, commodo quam habitasse senectus fringilla maecenas, inceptos magna tristique eu nullam nam. Maecenas orci nibh hac eu tristique ut penatibus ultrices ante, pellentesque cubilia pharetra dis facilisis aliquam praesent malesuada vivamus, commodo cras velit convallis molestie nec tellus augue. Etiam ut convallis risus id dapibus platea laoreet accumsan, habitant et aenean netus inceptos iaculis per, mauris curae at ligula odio ad eu. Mauris erat tempor interdum sapien commodo per nullam tortor, fusce facilisis vehicula egestas dui nulla conubia ut fames, fringilla et tincidunt penatibus facilisi at mollis.
|
||||
|
||||
Fermentum sociosqu litora primis sollicitudin fusce diam consequat vehicula per lobortis et, viverra sodales magna rutrum sed mollis faucibus molestie purus montes est, risus nostra congue venenatis lectus enim torquent eros dis dapibus. Dui suscipit scelerisque massa ligula euismod accumsan augue, magna vel lacus ante nullam senectus commodo, viverra cubilia eros eget penatibus tempor. Mattis mauris hac felis semper dui sociis faucibus mollis ornare pretium aliquam velit nisl, quis litora sem at vel duis rutrum imperdiet natoque viverra himenaeos tempor.
|
||||
|
||||
Integer eu tristique purus luctus vivamus porttitor vel nisl, tortor malesuada augue vulputate diam velit pellentesque sodales, duis phasellus vestibulum fermentum leo facilisi porta. Hac porttitor cum dapibus volutpat quisque odio taciti nulla senectus mollis curae, accumsan suscipit cubilia tempor ligula in venenatis justo leo erat, magna tincidunt nullam lacinia luctus malesuada non vivamus praesent pharetra. Non quam felis montes pretium volutpat suspendisse lacus, torquent magna dictumst orci libero porta, feugiat taciti cras ridiculus aenean rutrum. Tellus nostra tincidunt hac in ligula mi vulputate venenatis pellentesque urna dui, at luctus tristique quisque vel a dignissim scelerisque platea pretium, suspendisse ante phasellus porttitor quis aliquam malesuada etiam enim nullam.
|
||||
|
||||
Hendrerit taciti litora nec facilisis diam vehicula magnis potenti, parturient velit egestas nisl lobortis tincidunt rutrum cursus, fusce senectus mi massa primis mattis rhoncus. Accumsan est ac varius consequat vulputate, ligula cursus euismod sagittis inceptos scelerisque, lacus malesuada torquent dictumst. Volutpat morbi metus urna rhoncus nunc tempor molestie, congue curabitur quis interdum posuere. Mollis viverra velit tortor mus netus nunc molestie metus, sem massa himenaeos luctus feugiat taciti iaculis fames porttitor, leo arcu consequat gravida dapibus pulvinar elementum.
|
@ -1,64 +0,0 @@
|
||||
---
|
||||
publishDate: 2023-08-06T00:00:00Z
|
||||
title: How to customize AstroWind template to suit your branding
|
||||
excerpt: Personalize AstroWind template for your brand. Our guide unlocks seamless customization steps for a unique online presence.
|
||||
image: https://images.unsplash.com/photo-1546984575-757f4f7c13cf?ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D&auto=format&fit=crop&w=2070&q=80
|
||||
tags:
|
||||
- astro
|
||||
- tailwind css
|
||||
- theme
|
||||
metadata:
|
||||
canonical: https://astrowind.vercel.app/how-to-customize-astrowind-to-your-brand
|
||||
---
|
||||
|
||||
## Congue justo vulputate nascetur convallis varius orci fringilla nulla pharetr
|
||||
|
||||
Lorem ipsum dolor sit amet consectetur adipiscing elit, augue malesuada natoque in ad erat aliquam facilisi, lacus rhoncus mattis nostra et a. Mauris malesuada rutrum dis libero egestas mus vulputate, fermentum ad morbi phasellus faucibus tellus leo urna, blandit ullamcorper diam imperdiet dictumst litora. Fringilla eros malesuada lobortis mi odio metus leo, blandit imperdiet augue fames aliquam ultricies tortor massa, duis magnis hendrerit id magna sociosqu. Aptent mi imperdiet id sapien suscipit ut netus turpis, lacinia ac porttitor potenti dui taciti at egestas, fermentum neque nascetur sodales tortor nunc congue.
|
||||
|
||||
Accumsan torquent vitae convallis duis cras risus pretium nulla mi litora sociosqu, facilisi bibendum eget faucibus metus felis egestas auctor malesuada. Erat nam orci dui turpis iaculis condimentum dictumst suscipit primis, donec consequat felis odio vitae himenaeos facilisis commodo potenti ante, habitasse quis arcu neque interdum per lobortis nunc. Ultricies lobortis ullamcorper sagittis et sollicitudin sociis sed dignissim posuere, nisi pharetra erat varius id aenean lacinia commodo morbi primis, ornare diam proin nunc volutpat nec dui egestas.
|
||||
|
||||
## Mauris velit laoreet vitae cursus augue
|
||||
|
||||
- Massa egestas consequat nisl id volutpat, varius neque aenean.
|
||||
|
||||
- Venenatis tincidunt eros pretium viverra lacinia convallis, turpis orci condimentum fusce.
|
||||
|
||||
- Pellentesque in aliquet nisi gravida netus, commodo aptent volutpat.
|
||||
|
||||
- Nisi rutrum eros euismod, parturient ullamcorper mattis a, dapibus vestibulum.
|
||||
|
||||
Senectus fermentum tristique egestas bibendum per dictumst purus pharetra cras dictum pulvinar, vitae nec eros montes dis quis nullam duis netus litora, feugiat cubilia mollis porttitor velit ligula metus ante risus eu.
|
||||
|
||||
Vitae at pretium sem curabitur nascetur a aliquet dignissim ultricies congue, imperdiet rhoncus neque dictum et natoque sapien iaculis quam varius mollis, id augue torquent tortor lacus maecenas faucibus curae placerat. Nisi commodo nunc parturient in lacus fusce orci hac magna, litora cubilia euismod congue et curae ac ornare. Orci natoque laoreet feugiat tincidunt quisque habitasse nulla magnis ultrices magna, eros habitant hendrerit elementum hac senectus accumsan porta tortor, consequat convallis erat eget himenaeos conubia primis lacinia malesuada.
|
||||
|
||||
Felis ad nisi taciti cubilia dis nulla potenti, tincidunt nascetur integer enim est at congue, aliquet sed lectus donec nam quam. Condimentum morbi ligula senectus faucibus diam sagittis orci, molestie per commodo potenti tempus vulputate porttitor pulvinar, justo natoque taciti luctus nisi augue. Ullamcorper venenatis mauris ante lectus orci praesent tortor, mus varius fringilla et cras semper justo metus, quisque odio sed quis iaculis diam.
|
||||
|
||||
Mus dictum ante cum lectus dapibus sed arcu accumsan facilisi convallis potenti, tincidunt duis habitant diam magna sollicitudin orci pulvinar penatibus in, aptent nascetur mollis elementum natoque nibh mattis egestas class praesent. Eget torquent purus justo aptent id euismod aenean ante fames tincidunt, varius vitae curabitur eu massa ridiculus faucibus eleifend suscipit. Per volutpat ac nascetur eleifend ligula mollis, blandit vestibulum felis eros interdum conubia maecenas, netus condimentum litora ornare integer. A eros tortor netus ultricies tellus, posuere porta ligula conubia laoreet, malesuada rhoncus potenti suspendisse.
|
||||
|
||||
Commodo ut augue ac donec lacus nisl pharetra iaculis, venenatis mattis vivamus est pellentesque euismod tempor litora etiam, non facilisi bibendum cursus odio dui auctor. Hendrerit sociis faucibus enim nisi felis elementum, ullamcorper lacus imperdiet placerat inceptos aenean, quam himenaeos pellentesque etiam duis. Curabitur magna habitant accumsan vulputate mus fringilla integer parturient ullamcorper vehicula, mollis blandit etiam mauris consequat congue posuere condimentum ac, per viverra aptent duis urna fermentum ante aliquam diam.
|
||||
|
||||
Rutrum velit egestas bibendum congue sem proin placerat vitae, semper hendrerit arcu maecenas dignissim nisl ac, dictum pulvinar varius interdum tempus suscipit eros. Ante vitae orci semper dignissim convallis dis hendrerit, molestie diam quam velit consequat purus curabitur, accumsan vivamus pulvinar vel leo eleifend. Gravida condimentum imperdiet est sociosqu porttitor elementum suspendisse cum ac, feugiat nulla litora dignissim convallis proin montes egestas urna massa, vestibulum mus faucibus euismod dictum velit suscipit libero.
|
||||
|
||||
Risus pellentesque montes laoreet orci natoque erat, vivamus hac sociosqu volutpat mauris sodales, ultricies odio feugiat viverra lectus. Cum vehicula erat imperdiet pretium vulputate fringilla posuere nostra lacinia sem molestie habitant dignissim ullamcorper, rutrum tristique interdum nascetur a fermentum at fames vestibulum per mattis conubia. Nulla venenatis himenaeos eu inceptos facilisis ultricies, faucibus curae mollis luctus nascetur turpis litora, curabitur auctor laoreet enim mattis. Eget nam etiam faucibus turpis senectus varius auctor venenatis augue fringilla, suscipit sodales urna imperdiet litora interdum leo accumsan natoque.
|
||||
|
||||
Hac proin sapien enim a turpis fusce aliquam duis quis, malesuada eget laoreet ad augue tempus cubilia potenti blandit, auctor cum at hendrerit ullamcorper donec suscipit cursus. Ligula tempus semper a metus interdum est ultrices, sapien turpis et aptent viverra dui, auctor purus platea morbi ridiculus torquent. Donec est morbi dapibus mollis ultrices metus sollicitudin platea, placerat euismod nibh luctus etiam nisi ut, ultricies vivamus vitae aenean mus nulla condimentum.
|
||||
|
||||
Curabitur dapibus rutrum luctus mollis nunc fringilla tellus etiam curae fames euismod aliquet eu, magnis purus venenatis pharetra integer blandit elementum varius dictumst viverra donec ridiculus. Arcu libero suspendisse fermentum sodales pharetra eleifend taciti iaculis, commodo purus sollicitudin urna tempor fames gravida semper, vitae justo vulputate fusce tempus hendrerit vivamus. Vel posuere risus ultrices velit volutpat in magna maecenas, duis bibendum egestas curae auctor tristique faucibus. Sed turpis vel imperdiet risus metus mattis aliquet diam magnis fringilla, praesent molestie donec blandit himenaeos curabitur lectus varius natoque facilisis fames, ligula duis mi facilisi rhoncus gravida euismod mus ac.
|
||||
|
||||
Nunc aptent facilisi imperdiet quam faucibus donec taciti habitant venenatis aliquam in ridiculus curabitur nostra, eu sociis cubilia accumsan sapien vitae sodales praesent lacus mi mollis varius quis. Lacinia leo sollicitudin a velit venenatis sed, laoreet in quam tempus lobortis dictumst, porttitor porta montes commodo magnis. Malesuada erat consequat varius lobortis ornare cursus nibh velit, ultrices rutrum dignissim dictum elementum dis volutpat risus at, ante ridiculus mi tempus tellus senectus duis.
|
||||
|
||||
Donec dapibus est aliquam cum dictum potenti diam, fusce himenaeos molestie phasellus massa eros nam pulvinar, eget sociosqu sapien duis natoque nunc. Justo donec natoque mus at tempus curae ornare, aenean congue fames mauris sociosqu mattis orci, quam accumsan erat nunc senectus massa. Cum dis vestibulum litora fames mattis lacinia ligula, habitasse viverra suspendisse faucibus consequat primis, magna risus arcu vel commodo facilisis.
|
||||
|
||||
Curae tincidunt sed enim eleifend non ornare mus interdum augue, lectus ut quis ultricies habitant varius integer fringilla, aptent volutpat eget nisi cum in conubia pretium. Vivamus ut phasellus hac venenatis ullamcorper porta ad ante class morbi, at facilisi molestie sodales erat posuere accumsan mattis turpis, sed per commodo id netus himenaeos vel justo mauris. Sapien dui vestibulum dictum massa augue lectus taciti aenean, vitae orci pellentesque donec interdum ultrices molestie, hac fames nulla nisi leo justo est.
|
||||
|
||||
Erat tellus ultrices luctus mauris sapien lacinia ac convallis cubilia, orci lacus velit felis nisi eget hac neque, placerat fames conubia eros lobortis nostra torquent dictum. Ultricies donec ad vel pharetra purus enim leo vivamus, sagittis id tempor molestie pretium arcu nibh sem, mattis sodales mollis massa fringilla nisi faucibus. Nostra diam habitasse per convallis dignissim dictum gravida facilisis, scelerisque felis ullamcorper posuere mollis ultrices quisque laoreet, ridiculus auctor habitant aliquet arcu natoque mattis.
|
||||
|
||||
Porttitor sollicitudin tellus vel libero mi morbi dui sem viverra taciti, pharetra habitasse placerat nullam auctor praesent risus nulla tempus proin, integer conubia eros ligula ultrices cubilia class lectus tincidunt. Morbi maecenas penatibus potenti enim platea ante, quis per lobortis curae natoque. Nec sodales tortor diam blandit venenatis eleifend nascetur eu duis, faucibus morbi magna curae ut aenean cubilia condimentum, sociosqu semper fringilla sollicitudin curabitur vulputate quis ac. Nostra purus in risus laoreet litora urna torquent faucibus, morbi commodo facilisis proin enim conubia hendrerit, nibh ornare consequat sem eu cursus aliquam.
|
||||
|
||||
Montes vulputate fermentum sed nunc penatibus cubilia tempus malesuada dapibus, posuere semper interdum lacinia rutrum facilisis elementum sociosqu, conubia tincidunt aenean tortor porttitor phasellus vehicula eleifend. Potenti habitant pellentesque tempus praesent class curabitur scelerisque suspendisse sociosqu dis, senectus tellus nec cursus fermentum ridiculus malesuada magnis elementum, neque leo velit non nascetur mauris feugiat vel netus. Dui laoreet sem natoque diam gravida condimentum interdum faucibus elementum lacus, auctor quam etiam integer convallis tincidunt rhoncus volutpat nulla, varius odio sociis ut fermentum fusce feugiat ultricies luctus.
|
||||
|
||||
Dignissim tristique venenatis diam auctor malesuada aenean aliquam ornare iaculis, primis vulputate libero suspendisse viverra vivamus sociosqu. Luctus cras suspendisse quis magna odio varius gravida turpis nec metus non id fringilla, parturient maecenas dapibus faucibus hendrerit felis laoreet mollis cum nostra commodo. Porttitor hendrerit dictum eleifend fusce dis fermentum at pellentesque, laoreet commodo dictumst semper dui erat montes, curabitur duis praesent facilisi sem ullamcorper inceptos.
|
||||
|
||||
Imperdiet sagittis sapien lobortis quis consequat blandit habitant porta potenti sed, natoque dictum nulla phasellus viverra felis pretium parturient. Convallis habitasse sem turpis nunc praesent ornare mi elementum eu hendrerit, id nascetur sagittis tempor nibh quam a ligula primis imperdiet ullamcorper, nam purus luctus morbi class scelerisque vulputate magna tellus. Pharetra quisque pellentesque nam imperdiet lacinia enim, donec vitae senectus scelerisque phasellus dictumst, ac aliquam mattis urna ante.
|
||||
|
||||
Habitant praesent pulvinar scelerisque per phasellus lobortis velit, magnis odio himenaeos primis curabitur senectus, nascetur ullamcorper convallis nunc placerat nisl. Porta tellus commodo praesent ullamcorper cursus senectus tempor vivamus, penatibus eu purus ultrices posuere mi sodales, urna quisque accumsan imperdiet convallis aptent nisl. Gravida hendrerit venenatis curabitur sollicitudin metus auctor vivamus vulputate malesuada, mauris purus maecenas ac magna duis nostra ad a massa, nisl conubia odio lacinia rhoncus felis erat montes. Nostra eros proin mi venenatis enim semper ad magnis netus, in vestibulum ornare ac fusce aliquet aptent non condimentum faucibus, tempor arcu potenti blandit magna consequat luctus nam.
|
72
src/content/post/how-to-test-the-grid-part-one.md
Normal file
@ -0,0 +1,72 @@
|
||||
---
|
||||
publishDate: 2024-05-03T00:00:00Z
|
||||
author: Bernadette Amanda Caster
|
||||
title: ThreeFold Grid Testing - Ensuring Quality for Users
|
||||
excerpt: Learn about the testing process on the ThreeFold Grid, covering four networks and utilizing both manual and automated tests for stability and reliability.
|
||||
image: ~/assets/images/blog/testing_main.png
|
||||
category: farming
|
||||
tags:
|
||||
- technology
|
||||
- threefold_cloud
|
||||
- community
|
||||
---
|
||||
|
||||
Hi there and welcome to ThreeFold Grid Testing: Part One!
|
||||
|
||||
</br>
|
||||
|
||||
In this blog, we will introduce you to the overall cycle of testing on the TFGrid. Before releasing anything to the mainnet, TF engineers test three different networks: Devnet, Qanet, and Testnet. Testing also continues on the Mainnet even after the release of the updates. Today, we will go through the major steps of this process.
|
||||
|
||||
### **But first – why is testing important?**
|
||||
|
||||
Testing upgrades as they're developed ensures we have a stable operation of the TFGrid that is constantly optimal for our community. It lets us see what works well and what still needs fixing. By the time our community gets these upgrades, they've been tested many times to make sure they're top-notch.
|
||||
|
||||
</br>
|
||||
|
||||
When it comes to testing the developments on the ThreeFold Grid, we need to be careful, especially when we're doing separate tests from the different networks. If we don't focus on testing the developments independently, testing can become a lot slower and more complicated.
|
||||
|
||||
</br>
|
||||
|
||||
**Different networks for testing:** We test on 3 different networks before we release anything on Mainnet.
|
||||
|
||||
![Image](~/assets/images/blog/testing_roadmap.jpg)
|
||||
|
||||
</br>
|
||||
|
||||
### **Testing all Networks sequentially**
|
||||
|
||||
Our journey through these networks follows a well-defined path.
|
||||
|
||||
</br>
|
||||
|
||||
First, verification starts on Devnet with the dev team leading the validation process. Once the development team approves, we release the grid to the Qanet for further examination.
|
||||
|
||||
</br>
|
||||
|
||||
The QA teams conduct iterative test runs within Qanet, leading to a Bug Assessment Meeting to address reported issues. If the release is deemed ready for deployment, it moves to Testnet for an extended observation period.
|
||||
|
||||
</br>
|
||||
|
||||
Following two weeks of rigorous testing on Testnet releases advance to Mainnet once a community vote approves a Grid Enhancement Proposal, indicating readiness for widespread adoption. As the release enters Mainnet, QA teams begin new test iterations to ensure a smooth transition for user accessibility.
|
||||
|
||||
![Image](~/assets/images/blog/testing_cycle.png)
|
||||
|
||||
</br>
|
||||
|
||||
Testing is done both manually and automated:
|
||||
|
||||
</br>
|
||||
|
||||
**Manual testing:** At the core of our testing process is the thorough manual inspection of components using the advanced [Testlodge](https://manual.grid.tf/knowledge_base/collaboration/testing/testlodge.html) tool.
|
||||
|
||||
</br>
|
||||
|
||||
**Automation Testing:** We also run Automated scripts on GitHub actions daily; to give us an early indication about the TFGrid.
|
||||
|
||||
</br>
|
||||
|
||||
We will go through these two types of testing further in part two.
|
||||
|
||||
### **Conclusion**
|
||||
|
||||
The testing journey within the ThreeFold Grid is intentionally and necessarily thorough, a delicate balance between manual precision and automated finesse, all designed to provide a strong and reliable cloud infrastructure for our users. Next time, stay tuned for more updates on how we conduct these tests and how they help us improve the grid's reliability. [Join us](https://t.me/threefoldtesting) as we strive for excellence and continue to advance in the world of decentralized technology.
|
94
src/content/post/how_to_test_the_grid_part_two.md
Normal file
@ -0,0 +1,94 @@
|
||||
---
|
||||
publishDate: 2024-05-09T00:00:00Z
|
||||
author: Bernadette Amanda Caster
|
||||
title: ThreeFold Grid Testing - Overview of Manual and Automation Testing
|
||||
excerpt: Go deeper in the exploration of testing the ThreeFold Grid. Learn about two types of testing which combine to ensure a strong and dependable grid.
|
||||
image: ~/assets/images/blog/how_to_test_the_grid_part_two.png
|
||||
category: farming
|
||||
tags:
|
||||
- technology
|
||||
- threefold_grid
|
||||
metadata:
|
||||
canonical: https://astrowind.vercel.app/get-started-website-with-astro-tailwind-css
|
||||
---
|
||||
|
||||
In our [last post](https://www.threefold.io/blog/how-to-test-the-grid-part-one/), we started to explore what it means to test the ThreeFold Grid by highlighting the key processes and the benefits or reasons. Now, we continue our discovery path through the detailed testing process. In this post, we go deeper into two different ways of testing: Manual and Automation. Each is important, combining to ensure a strong and dependable TF Grid.
|
||||
|
||||
### **Manual Testing**
|
||||
|
||||
The thorough [manual inspection](https://manual.grid.tf/knowledge_base/collaboration/testing/testing_readme.html?highlight=manual%20testing#manual-testing) of components using the [Testlodge tool](https://manual.grid.tf/knowledge_base/collaboration/testing/testlodge.html) is at the core of our testing process. This tool acts as our guide, leading us through an array of test cases customized for each grid component. We guarantee comprehensive coverage of all grid components by organizing tests manually in specific test suites.
|
||||
|
||||
<br/>
|
||||
|
||||
When a release candidate arrives from the development phase, our manual test executions come into play. Through meticulous examination, we confirm the smooth operation of each component. Any inconsistencies found during testing are promptly recorded using GitHub issues, facilitating quick resolution in future iterations.
|
||||
|
||||
<br/>
|
||||
|
||||
Components such as Dashboard & Deployments, Mycelium, TF-Robot, Terraform, TF-Grid-Client, TF-Grid-Proxy, TF chain, Caprover, Kubernetes, and Farmerbot are examples of what undergoes our scrutiny.
|
||||
|
||||
### **Why Manual Testing is Important:**
|
||||
|
||||
Any new changes added to the grid should first undergo manual testing before going through automation testing. The fundamental principle of testing is that “100% automation is not possible” which makes manual testing necessary.
|
||||
|
||||
<br/>
|
||||
|
||||
The main idea behind manual testing is to make sure that the grid is free of errors and that it is operating following the stated functional requirements in the manual and documentation. Additionally, it ensures that developers fix reported faults and that testers retest them.
|
||||
|
||||
<br/>
|
||||
|
||||
Also, manual testing simulates the real-time behavior of the end user and how they think when they use our TF Grid solution, which allows us to do better UX design to meet everyone's expectations.
|
||||
|
||||
<br/>
|
||||
|
||||
![Image](~/assets/images/blog/navigating_levels.png)
|
||||
|
||||
### **Automation Testing**
|
||||
|
||||
[Automation scripts](https://manual.grid.tf/knowledge_base/collaboration/testing/testing_readme.html#automation-testing) are essential in strengthening our testing capabilities and our manual efforts. By utilizing [GitHub actions](https://github.com/threefoldtech/tfgrid-sdk-ts/actions), we run automated scripts daily to gain early insights into the health of the TF Grid. Our in-house automation tool, [TF-Robot](https://manual.grid.tf/documentation/developers/tfrobot/tfrobot.html?highlight=TFRo#), leads the deployment process on the grid with exceptional efficiency.
|
||||
|
||||
<br/>
|
||||
|
||||
TF-Robot is a cornerstone of automation, streamlining the deployment of various virtual machines across the ThreeFold Grid. With its capacity to manage large-scale deployments and offer multiple retries for unsuccessful attempts, TF-Robot enables users to navigate the grid seamlessly. Additionally, we leverage its functionalities to ensure the viability of registered nodes by deploying on active nodes regularly to confirm their suitability for deployment.
|
||||
|
||||
<br/>
|
||||
|
||||
We use GitHub Actions to run our automated tests. These tests – ranging from testing solution deployments, to the status / health of all nodes, to the dashboard UI – are triggered by certain behaviors or activities:
|
||||
|
||||
<br/>
|
||||
|
||||
- Any code change triggers certain tests
|
||||
- Tests also run during code reviews
|
||||
- Some tests run every day, like the Grid Client Nightly and Grid Client Tests
|
||||
- Other tests run every 6 hours, like Mass Deployments
|
||||
|
||||
### **Why Automation Testing is Important:**
|
||||
|
||||
Automation testing speeds up the testing process significantly compared to manual testing. Automated tests can run anytime, including nights and weekends, allowing for continuous testing and faster development cycles. This reduces testing time and labor costs, making it a cost-effective approach in the long run.
|
||||
Automation helps identify issues and defects in the software early in the development process, making them easier and less expensive to fix. Automated test scripts are reusable and can be used throughout different phases of development, even if there are changes in the software's user interface.
|
||||
|
||||
<br/>
|
||||
|
||||
Sometimes, a node may be misconfigured or have defective hardware. In our automation testing, we run tests like Mass Deployer or TF-Robot, which loop over all online nodes and attempt deployments on them to detect problematic nodes or misconfigured ones early.
|
||||
|
||||
<br/>
|
||||
|
||||
Additionally, nightly test runs for different test suites (dashboard UI, TS client) can detect incorrect code deployments early and alert developers to fix the pushed code that may affect unexpected parts of the project.
|
||||
|
||||
### **How to Report an Error/Issue/Bug Found While Testing:**
|
||||
|
||||
All errors found during testing are reported [on GitHub](https://github.com/threefoldtech/tfgrid-sdk-ts/issues). Based on findings, the repository has two templates to choose from: Bug Report and Feature Request. Follow these steps:
|
||||
|
||||
<br/>
|
||||
|
||||
1. Click on the provided GitHub link.
|
||||
2. Choose "New Issue."
|
||||
3. Select either of the templates and fill it out accordingly.
|
||||
4. Click on "Submit."
|
||||
|
||||
<br/>
|
||||
|
||||
One of our developers will then work on resolving the issue. We have already fixed over 1,200 issues to date.
|
||||
|
||||
<br/>
|
||||
|
||||
Testing is a key aspect of maintaining a reliable cloud infrastructure. Because testing is such a thorough process, we can catch and correct bugs before they make their way to mainnet, our “production” environment. A big thanks to all those who have contributed to testing the grid to date, and we invite anyone to [join the testing community](https://t.me/threefoldtesting) and take part in ensuring a smooth and reliable ThreeFold Grid.
|
@ -1,152 +1,151 @@
|
||||
---
|
||||
publishDate: 2023-07-15T00:00:00Z
|
||||
title: 'Mastering Landing Pages: Practical Guide for 2023'
|
||||
excerpt: Ever clicked on an ad and found yourself on a page that seemed to really want you to do something? Congratulations, you've landed on a Landing Page!
|
||||
image: https://images.unsplash.com/photo-1561069934-eee225952461?ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D&auto=format&fit=crop&w=2070&q=80
|
||||
publishDate: 2024-03-04T00:00:00Z
|
||||
title: 'The Building Blocks of the Internet'
|
||||
author: Emilie Ouwerx
|
||||
excerpt: Learn about the layers of the Internet to understand how digital information is processed, stored, and accessed.
|
||||
image: ~/assets/images/blog/three_layers.png
|
||||
tags:
|
||||
- landing-pages
|
||||
- front-end
|
||||
- resources
|
||||
- threefold_grid
|
||||
- peer_to_pee
|
||||
- technology
|
||||
metadata:
|
||||
canonical: https://astrowind.vercel.app/landing
|
||||
---
|
||||
|
||||
In the vast digital landscape, standing out is more than a desire—it's a necessity. Enter the world of Landing Pages, the unsung heroes of digital marketing. With the power of the AstroWind template, developed using Astro and Tailwind CSS, crafting these pages becomes even more intuitive. Let's dive deep into understanding, creating, and optimizing them.
|
||||
Just as the Earth is made up of layers—from the crust to the core — so too is the Internet, with three key layers: compute & storage, network, and applications. Distinguishing these layers helps us to understand how digital information is currently processed, stored, and accessed across the globe and how ThreeFold technology can transform this model. ThreeFold can be likened to tectonic forces, reshaping the digital landscape by introducing improved ways for these layers to interact. Let’s break down these three layers, their current challenges, and ThreeFold’s approach to each of them.
|
||||
|
||||
## Landing Pages Unveiled
|
||||
### **Compute & Storage**
|
||||
|
||||
A **Landing Page** is a standalone web page, distinct from your main website. Crafted with a singular objective: to convert visitors into actionable leads or sales. It's where a visitor "lands" post-clicking on a marketing link or ad.
|
||||
**What it is:**
|
||||
|
||||
Imagine clicking on an ad for a limited-time discount on a popular shoe brand. This action guides you to a page that showcases the discounted shoes, featuring a clear "Buy Now" button. That's a Landing Page in action, focusing your attention solely on the offer.
|
||||
<br>
|
||||
|
||||
## The Power of Precision
|
||||
Compute is responsible for processing data. It runs programs and applications by leveraging computational resources like CPUs (Central Processing Units) and GPUs (Graphics Processing Units). It handles the calculations, logic, and running of software that users depend on. Compute resources are provided by servers located in centralized data centers and cloud platforms.
|
||||
|
||||
Unlike a homepage brimming with diverse content, a Landing Page is laser-focused. It eliminates potential distractions like excessive navigation, ensuring the visitor's attention remains undivided. The result? Higher conversion rates and a more streamlined user experience.
|
||||
<br>
|
||||
|
||||
![Target](https://images.unsplash.com/photo-1596008194705-2091cd6764d4?ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D&auto=format&fit=crop&w=1639&q=80)
|
||||
Storage is about saving and retrieving data. It provides a persistent way to store data so that it can be accessed in the future. This encompasses various types of storage media, such as hard drives (HDDs), solid-state drives (SSDs), and distributed storage systems that span across multiple locations. Storage ensures that data is kept safe and available for when it's needed, either for immediate use by applications or for long-term retention.
|
||||
|
||||
Think of a Landing Page as a digital salesperson. Just as a salesperson would pitch a product without distractions, a Landing Page promotes an offer without unnecessary links or information. It's like walking into a store with a single product on display, making your choice straightforward.
|
||||
<br>
|
||||
|
||||
## Why Landing Pages Matter
|
||||
**The problem with the current model:**
|
||||
|
||||
In today's digital rush, hoping customers stumble upon you is a strategy of the past. Landing Pages are the future. They:
|
||||
<br>
|
||||
|
||||
- **Guide Traffic**: Directing visitors seamlessly through the sales funnel.
|
||||
- **Boost ROI**: Maximizing returns on marketing investments.
|
||||
- **Personalize User Experience**: Tailoring content to specific audience segments.
|
||||
A key problem with the current compute & storage layer lies in its centralized structure, which creates vulnerabilities, scalability challenges, and performance issues. Relying on centralized data centers and cloud platforms leads to single points of failure, which increases the risk of outages and cyberattacks, thus heightening concerns about service disruption and data security. Scaling this centralized infrastructure to meet increasing demand is costly and not straightforward, while latency issues hinder real-time data processing.
|
||||
|
||||
For instance, if you're launching a new fitness app. A well-crafted Landing Page can target individuals interested in health and wellness, offering them a free trial. This targeted approach ensures that those genuinely interested in fitness are the ones you're engaging with.
|
||||
<br>
|
||||
|
||||
## Crafting the Perfect Landing Page
|
||||
The concentration of the compute & storage within data centers primarily located in Europe, North America, or China raises significant concerns. This geographical bias in Internet infrastructure keeps data, jobs, and economic benefits centralized in certain regions, putting developing areas at a disadvantage and raising concerns around data sovereignty and autonomy.
|
||||
|
||||
Every element of your Landing Page should resonate with its core objective. Here's what a high-converting Landing Page entails:
|
||||
<br>
|
||||
|
||||
- **Benefit-Centric Headline**: Your headline should instantly convey the value proposition.
|
||||
- **Engaging Imagery**: Visuals that complement and enhance the content.
|
||||
- **Compelling Copy**: Clear, concise, and persuasive text that speaks directly to the visitor's needs.
|
||||
- **Clear Call-to-Action (CTA)**: A standout button or link urging the visitor to take action.
|
||||
- **Minimalist Design**: A clutter-free layout that emphasizes the offer. For example, using a Tailwind CSS web template like AstroWind.
|
||||
- **Trust Indicators**: Endorsements, reviews, and badges that bolster credibility.
|
||||
For example, when two people in Zanzibar undertake a video call, their call data is sent to a data center in Europe via costly fiber optics, wasting resources and diminishing performance. This scenario represents a broader problem affecting various locations and use cases. This inefficient and inequitable system can be changed.
|
||||
|
||||
Imagine browsing online for a writing course. You land on a page with a captivating headline: "Unlock the Writer Within." Below, there's an engaging image of a person writing, followed by persuasive text and a bright "Enroll Now" button. This Landing Page has effectively used its elements to entice you to sign up.
|
||||
<br>
|
||||
|
||||
## Homepage vs. Landing Page
|
||||
![Image](~/assets/images/blog/current_call.png)
|
||||
|
||||
While both are pivotal, they serve distinct roles:
|
||||
<br>
|
||||
|
||||
- **Homepage**: Offers a panoramic view of your brand, catering to diverse visitor intents.
|
||||
- **Landing Page**: Zeros in on a single, specific action, be it signing up, purchasing, or downloading.
|
||||
**The ThreeFold model:**
|
||||
|
||||
Consider a popular online store. Their homepage might display various product categories, from electronics to clothing. However, if they’re promoting a summer sale, the Landing Page would focus solely on summer products. This focused approach urges visitors to take action, encouraging them to "Shop the Summer Sale Now!"
|
||||
<br>
|
||||
|
||||
## The Art of Optimization
|
||||
ThreeFold decentralizes compute & storage by distributing it across a global network of independent nodes rather than concentrating it in large data centers. Autonomous technology allows us to remove most human involvement from the equation. This approach allows anyone, regardless of technical know-how, to contribute compute & storage to the network or utilize it for their own applications. In essence, the compute & storage layer becomes co-owned, allowing anyone to become a cloud provider.
|
||||
|
||||
The digital realm is ever-evolving. Regular tweaks based on analytics can ensure your Landing Page remains a conversion powerhouse. Embrace A/B testing to compare different versions and refine for optimal results.
|
||||
<br>
|
||||
|
||||
Let's say you have a Landing Page for a new skincare product. Version A uses an image of the product, while Version B showcases a video review. A/B testing might reveal that Version B, with the video, has a 20% higher conversion rate. Such insights can be invaluable for future campaigns.
|
||||
ThreeFold’s autonomous technology efficiently allocates compute resources, increasing performance and reliability while reducing energy consumption. The distributed storage system fragments data and stores it securely across multiple locations, ensuring that data is always recoverable. Data security is also enhanced as there is no central repository for attackers to target. In this decentralized model, individuals' data remains within their country's borders, safeguarding their information from being exploited as a commodity by external entities. Storing data closer to the end user reduces latency and improves access speeds.
|
||||
|
||||
## Landing Pages in Action
|
||||
<br>
|
||||
|
||||
Landing Pages are versatile tools in your marketing toolkit. They play a role in various scenarios: promoting a product launch, capturing emails for a newsletter, or driving event registrations. They’re not just about capturing leads but nurturing and converting them.
|
||||
Let's revisit the scenario of a video call between two individuals in Zanzibar. With ThreeFold technology, call data will be sent directly between local ThreeFold nodes. These nodes are deployed locally by people and organizations, avoiding centralized ownership by major tech corporations. Instead of relying on data centers thousands of miles away, our decentralized infrastructure significantly shortens the connection distance. The pair in Zanzibar can now communicate peer-to-peer, reducing bandwidth needs by up to 10 times while boosting security.
|
||||
|
||||
Presented below are several prevalent types of Landing Pages. Each link offers a prime example of its respective type. Additionally, we carefully craft each link in the form of a comprehensive guide.
|
||||
<br>
|
||||
|
||||
This approach ensures that you observe the best practices in action. Also, it enables you to acquire a step-by-step understanding of how to skillfully create each type.
|
||||
![Image](~/assets/images/blog/threefold_call.png)
|
||||
|
||||
### [Lead Generation Landing Page](landing/lead-generation)
|
||||
<br>
|
||||
|
||||
**Purpose**: Designed primarily to capture user data, such as email addresses or contact details.
|
||||
### **Network**
|
||||
|
||||
**Content**: Usually includes a form where users can input their details. It also highlights what they'll get in return, such as an eBook, a webinar, or a free trial.
|
||||
**What it is:**
|
||||
|
||||
**Focus**: Enticing visitors to provide their personal details by offering something valuable in return.
|
||||
<br>
|
||||
|
||||
**Key Differentiator**: Unlike “Click-through Landing Pages,” which guide users to another step, these directly gather user data.
|
||||
The purpose of the network layer of the Internet is to send data packets from their source (point A) to their destination (point B) across multiple networks. Data packets are small pieces of information which include the data being sent and details like where it's coming from and where it's going. They can be thought of as small parcels of data that travel through the Internet. These parcels can take different paths to reach their destination and once they arrive they are put back together to form the original data.
|
||||
|
||||
**Example**: A digital marketing agency offering a free SEO audit in exchange for business contact details.
|
||||
<br>
|
||||
|
||||
### [Long-form Sales Landing Page](landing/sales)
|
||||
The network operates on protocols like IP (Internet Protocol), which assigns unique addresses to devices on the Internet to ensure data reaches the correct location. The network layer handles the path selection and directs data packets through various routers and networks to reach its destination. This layer enables communication between devices in different networks, ensuring efficient delivery across the vast expanse of the Internet.
|
||||
|
||||
**Purpose**: Primarily designed to sell, aiming to persuade and convert visitors into customers.
|
||||
<br>
|
||||
|
||||
**Content**: Extensive, providing a wealth of information including product details, benefits, user stories, success stories, guarantees, and bonuses.
|
||||
**The problem with the current model:**
|
||||
|
||||
**Focus**: Utilizes a narrative to present a problem and offer the product or service as the solution. The aim is to emotionally connect with the visitor.
|
||||
<br>
|
||||
|
||||
**Key Differentiator**: While 'Click-through Landing Pages' warm up the visitor for a bigger commitment. 'Long-form Sales Landing Pages' aim to close the sale directly on the page.
|
||||
The current model of the network layer relies heavily on traditional routing protocols and infrastructure, which often lead to inefficiencies and vulnerabilities. Centralized routing mechanisms may result in suboptimal path selection, leading to longer latency and decreased network performance. As highlighted in the picture below, the path that these data packets take in the current system can be very complex and ineffective. The reliance on a centralized architecture makes the network susceptible to single points of failure and cyberattacks. Traditional networks lack inherent privacy and security measures, leaving data vulnerable to interception and unauthorized access during transmission. The lack of scalability, reliability, and security of the current network model highlights the need for a new approach.
|
||||
|
||||
**Example**: A weight loss program detailing a person's journey and the challenges they've faced. It also highlights how the program assisted them and why it's an ideal solution for others.
|
||||
<br>
|
||||
|
||||
### [Click-through Landing Page](landing/click-through)
|
||||
![Image](~/assets/images/blog/current_network.png)
|
||||
|
||||
**Purpose**: Acts as a middle step, warming up visitors for a bigger commitment.
|
||||
Credit: Lazario Gamio, 2015, [The Washington Post](https://www.washingtonpost.com/graphics/national/security-of-the-internet/bgp/)
|
||||
|
||||
**Content**: Provides essential details and benefits of an offer, urging visitors to click through to another page.
|
||||
<br>
|
||||
|
||||
**Focus**: To lead visitors to the final conversion point, be it a checkout page or a sign-up form.
|
||||
**The ThreeFold model:**
|
||||
|
||||
**Key Differentiator**: Unlike "Subscription Landing Pages" that aim for a recurring commitment, these lead to a one-time action.
|
||||
<br>
|
||||
|
||||
**Example**: An online store showcasing a new product's benefits, leading visitors to the purchase page.
|
||||
ThreeFold is disrupting the network layer through its new Mycelium technology, a true peer-to-peer mesh network. It is the only overlay network in the world capable of taking locality into consideration, routing decisions based on proximity between individuals, and selecting the quickest route possible. This addresses the current system’s suboptimal path selection as visualized above. In this new model data packets take the quickest route from point A to point B. Mycelium also ensures end-to-end encryption for all traffic, enhancing data privacy and security. This new 'always-on' network offers continuous connectivity and seamless access to resources, even in the face of network disruptions or outages.
|
||||
|
||||
### [Product Details Landing Page](landing/product)
|
||||
<br>
|
||||
|
||||
**Purpose**: Designed to inform by providing specific details about a product or service.
|
||||
![Image](~/assets/images/blog/threefold_network.png)
|
||||
|
||||
**Content**: Focuses on features, specifications, and benefits. May include high-quality images, detailed descriptions, demo videos, and user reviews.
|
||||
Credit: Haseeb Qureshi, 2019, [Nakamoto](https://nakamoto.com/p2p-networking/)
|
||||
|
||||
**Focus**: Presents the product or service transparently and attractively.
|
||||
<br>
|
||||
|
||||
**Key Differentiator**: While 'Long-form Sales Landing Pages' aim to persuade through narratives and overcoming objections. 'Product Details Landing Pages' focus on presenting the product or service in a clear and detailed manner.
|
||||
### **Applications**
|
||||
|
||||
**Example**: A tech website detailing a new laptop's specifications, unique features, comparisons with previous models, and user reviews.
|
||||
**What it is:**
|
||||
|
||||
### [Coming Soon or Pre-Launch Landing Page](landing/pre-launch)
|
||||
<br>
|
||||
|
||||
**Purpose**: Creates excitement for an upcoming product, service, or event.
|
||||
At the top of the Internet stack are applications — the user-facing software that provides the services and experiences we interact with daily. Applications range from web browsers and social media to more complex systems like blockchain platforms and decentralized apps (dApps). They are the interface through which users interact with the digital world.
|
||||
|
||||
**Content**: Often includes a countdown timer, teaser content, and an option to sign up for notifications.
|
||||
<br>
|
||||
|
||||
**Focus**: To generate buzz and capture early interest.
|
||||
**The problem with the current model:**
|
||||
|
||||
**Key Differentiator**: Unlike other landing pages that present available offers, these promote something not yet accessible.
|
||||
<br>
|
||||
|
||||
**Example**: A game developer teasing their upcoming game release with sneak peeks and an option for early access.
|
||||
The problem with the current model is the lack of control over our digital identities. Currently, users are scattered across numerous platforms, each hosting their data separately. This means that individuals exist in multiple instances online, with their personal information spread across different servers and databases controlled by different applications (visualized in the picture below). This fragmentation not only leads to redundancy but also raises concerns about security, privacy, and control over personal data. Users are forced to trust multiple third-party applications with their sensitive information, often without transparency or control over how their data is used or shared. The centralized nature of these applications exposes users to risks such as data breaches, unauthorized access, and exploitation of personal information for targeted advertising or other purposes. In the existing system, users are at the mercy of application providers, who dictate the terms of service and privacy policies. This asymmetry in power dynamics leaves users with limited options to protect their privacy or exercise control over their data.
|
||||
|
||||
### [Subscription Landing Page](landing/subscription)
|
||||
<br>
|
||||
|
||||
**Purpose**: Encourages visitors to subscribe to a service, newsletter, or recurring product.
|
||||
![Image](~/assets/images/blog/current_applications.png)
|
||||
|
||||
**Content**: Highlights the benefits of subscribing, often offering special deals or exclusive content for subscribers.
|
||||
<br>
|
||||
|
||||
**Focus**: To secure a long-term commitment from the visitor.
|
||||
**The ThreeFold model:**
|
||||
|
||||
**Key Differentiator**: Unlike "Click-through Landing Pages" that lead to a one-time action, these aim for a recurring commitment.
|
||||
<br>
|
||||
|
||||
**Example**: A magazine promoting its monthly subscription, detailing exclusive articles and special subscriber-only benefits.
|
||||
ThreeFold delivers a decentralized and user-centric approach to the application layer, empowering users and developers. By providing access to decentralized compute, storage, and networking resources, ThreeFold facilitates the development and deployment of decentralized applications (dApps) within its ecosystem. Unlike traditional centralized applications, which rely on proprietary infrastructure and are subject to the control of centralized entities, dApps built on ThreeFold operate within a decentralized environment increasing security and privacy. Users have greater autonomy and control over their digital identities and data. Instead of being scattered across numerous platforms with data hosted separately, users have one digital identity. This reduces fragmentation and eliminates the need to trust multiple third-party applications with sensitive information. In the ThreeFold model, applications are designed to serve the users rather than the other way round.
|
||||
|
||||
## Conclusion
|
||||
<br>
|
||||
|
||||
In the digital marketing symphony, Landing Pages become the crescendo. They capture attention, evoke action, and drive results. As we move forward, an essential task is to optimize, maintain relevance, and create high-converting Landing Pages. These factors collectively hold the key to achieving digital success.
|
||||
![Image](~/assets/images/blog/threefold_applications.png)
|
||||
|
||||
Imagine a world where every online interaction gets personalized and directed. This showcases the potential of Landing Pages. For startups seeking traction or established brands introducing new products, Landing Pages can serve as the catalyst. They possess the power to spur digital growth and boost engagement.
|
||||
<br>
|
||||
|
||||
### **Conclusion**
|
||||
|
||||
Understanding the Internet’s three layers is key to grasping the current digital landscape and envisioning the transformative potential of ThreeFold's technology. Just as tectonic forces reshape our physical world, ThreeFold is disrupting the layers of the digital world. By decentralizing compute & storage, ThreeFold eliminates the vulnerabilities in centralized models, fostering efficiency and security. Through Mycelium, ThreeFold is rewriting the rules of connectivity, ensuring resilience and security. At the application layer, ThreeFold empowers users, shifting the paradigm to user empowerment. It's a new dawn for the Internet, one where connectivity is inclusive, efficient, and equitable, and ThreeFold is leading the charge. Let’s seize the opportunity to shape an Internet that thrives locally, serves globally, and empowers universally.
|
||||
|
||||
<br>
|
||||
|
@ -1,204 +0,0 @@
|
||||
---
|
||||
publishDate: 2023-01-02T00:00:00Z
|
||||
title: Markdown elements demo post
|
||||
excerpt: Sint sit cillum pariatur eiusmod nulla pariatur ipsum. Sit laborum anim qui mollit tempor pariatur nisi minim dolor.
|
||||
tags:
|
||||
- markdown
|
||||
- blog
|
||||
- Astro
|
||||
---
|
||||
|
||||
import Logo from '~/components/Logo.astro';
|
||||
import { YouTube, Tweet, Vimeo } from 'astro-embed';
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
|
||||
|
||||
## <a name="Headings"></a>Headings
|
||||
|
||||
Sint sit cillum pariatur eiusmod nulla pariatur ipsum. Sit laborum anim qui mollit tempor pariatur nisi minim dolor. Aliquip et adipisicing sit sit fugiat commodo id sunt. Nostrud enim ad commodo incididunt cupidatat in ullamco ullamco Lorem cupidatat velit enim et Lorem. Ut laborum cillum laboris fugiat culpa sint irure do reprehenderit culpa occaecat. Exercitation esse mollit tempor magna aliqua in occaecat aliquip veniam reprehenderit nisi dolor in laboris dolore velit.
|
||||
|
||||
## Heading two
|
||||
|
||||
Aute officia nulla deserunt do deserunt cillum velit magna. Officia veniam culpa anim minim dolore labore pariatur voluptate id ad est duis quis velit dolor pariatur enim. Incididunt enim excepteur do veniam consequat culpa do voluptate dolor fugiat ad adipisicing sit. Labore officia est adipisicing dolore proident eiusmod exercitation deserunt ullamco anim do occaecat velit. Elit dolor consectetur proident sunt aliquip est do tempor quis aliqua culpa aute. Duis in tempor exercitation pariatur et adipisicing mollit irure tempor ut enim esse commodo laboris proident. Do excepteur laborum anim esse aliquip eu sit id Lorem incididunt elit irure ea nulla dolor et. Nulla amet fugiat qui minim deserunt enim eu cupidatat aute officia do velit ea reprehenderit.
|
||||
|
||||
### Heading three
|
||||
|
||||
Voluptate cupidatat cillum elit quis ipsum eu voluptate fugiat consectetur enim. Quis ut voluptate culpa ex anim aute consectetur dolore proident voluptate exercitation eiusmod. Esse in do anim magna minim culpa sint. Adipisicing ipsum consectetur proident ullamco magna sit amet aliqua aute fugiat laborum exercitation duis et.
|
||||
|
||||
#### Heading four
|
||||
|
||||
Commodo fugiat aliqua minim quis pariatur mollit id tempor. Non occaecat minim esse enim aliqua adipisicing nostrud duis consequat eu adipisicing qui. Minim aliquip sit excepteur ipsum consequat laborum pariatur excepteur. Veniam fugiat et amet ad elit anim laborum duis mollit occaecat et et ipsum et reprehenderit. Occaecat aliquip dolore adipisicing sint labore occaecat officia fugiat. Quis adipisicing exercitation exercitation eu amet est laboris sunt nostrud ipsum reprehenderit ullamco. Enim sint ut consectetur id anim aute voluptate exercitation mollit dolore magna magna est Lorem. Ut adipisicing adipisicing aliqua ullamco voluptate labore nisi tempor esse magna incididunt.
|
||||
|
||||
##### Heading five
|
||||
|
||||
Veniam enim esse amet veniam deserunt laboris amet enim consequat. Minim nostrud deserunt cillum consectetur commodo eu enim nostrud ullamco occaecat excepteur. Aliquip et ut est commodo enim dolor amet sint excepteur. Amet ad laboris laborum deserunt sint sunt aliqua commodo ex duis deserunt enim est ex labore ut. Duis incididunt velit adipisicing non incididunt adipisicing adipisicing. Ad irure duis nisi tempor eu dolor fugiat magna et consequat tempor eu ex dolore. Mollit esse nisi qui culpa ut nisi ex proident culpa cupidatat cillum culpa occaecat anim. Ut officia sit ea nisi ea excepteur nostrud ipsum et nulla.
|
||||
|
||||
###### Heading six
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
|
||||
|
||||
[[Top]](#top)
|
||||
|
||||
## <a name="Paragraphs"></a>Paragraphs
|
||||
|
||||
Incididunt ex adipisicing ea ullamco consectetur in voluptate proident fugiat tempor deserunt reprehenderit ullamco id dolore laborum. Do laboris laboris minim incididunt qui consectetur exercitation adipisicing dolore et magna consequat magna anim sunt. Officia fugiat Lorem sunt pariatur incididunt Lorem reprehenderit proident irure. Dolore ipsum aliqua mollit ad officia fugiat sit eu aliquip cupidatat ipsum duis laborum laborum fugiat esse. Voluptate anim ex dolore deserunt ea ex eiusmod irure. Occaecat excepteur aliqua exercitation aliquip dolor esse eu eu.
|
||||
|
||||
Officia dolore laborum aute incididunt commodo nisi velit est est elit et dolore elit exercitation. Enim aliquip magna id ipsum aliquip consectetur ad nulla quis. Incididunt pariatur dolor consectetur cillum enim velit cupidatat laborum quis ex.
|
||||
|
||||
Officia irure in non voluptate adipisicing sit amet tempor duis dolore deserunt enim ut. Reprehenderit incididunt in ad anim et deserunt deserunt Lorem laborum quis. Enim aute anim labore proident laboris voluptate elit excepteur in. Ex labore nulla velit officia ullamco Lorem Lorem id do. Dolore ullamco ipsum magna dolor pariatur voluptate ipsum id occaecat ipsum. Dolore tempor quis duis commodo quis quis enim.
|
||||
|
||||
[[Top]](#top)
|
||||
|
||||
## <a name="Blockquotes"></a>Blockquotes
|
||||
|
||||
Ad nisi laborum aute cupidatat magna deserunt eu id laboris id. Aliquip nulla cupidatat sint ex Lorem mollit laborum dolor amet est ut esse aute. Nostrud ex consequat id incididunt proident ipsum minim duis aliqua ut ex et ad quis. Laborum sint esse cillum anim nulla cillum consectetur aliqua sit. Nisi excepteur cillum labore amet excepteur commodo enim occaecat consequat ipsum proident exercitation duis id in.
|
||||
|
||||
> Ipsum et cupidatat mollit exercitation enim duis sunt irure aliqua reprehenderit mollit. Pariatur Lorem pariatur laboris do culpa do elit irure. Eiusmod amet nulla voluptate velit culpa et aliqua ad reprehenderit sit ut.
|
||||
|
||||
Labore ea magna Lorem consequat aliquip consectetur cillum duis dolore. Et veniam dolor qui incididunt minim amet laboris sit. Dolore ad esse commodo et dolore amet est velit ut nisi ea. Excepteur ea nulla commodo dolore anim dolore adipisicing eiusmod labore id enim esse quis mollit deserunt est. Minim ea culpa voluptate nostrud commodo proident in duis aliquip minim.
|
||||
|
||||
> Qui est sit et reprehenderit aute est esse enim aliqua id aliquip ea anim. Pariatur sint reprehenderit mollit velit voluptate enim consectetur sint enim. Quis exercitation proident elit non id qui culpa dolore esse aliquip consequat.
|
||||
|
||||
Ipsum excepteur cupidatat sunt minim ad eiusmod tempor sit.
|
||||
|
||||
> Deserunt excepteur adipisicing culpa pariatur cillum laboris ullamco nisi fugiat cillum officia. In cupidatat nulla aliquip tempor ad Lorem Lorem quis voluptate officia consectetur pariatur ex in est duis. Mollit id esse est elit exercitation voluptate nostrud nisi laborum magna dolore dolore tempor in est consectetur.
|
||||
|
||||
Adipisicing voluptate ipsum culpa voluptate id aute laboris labore esse fugiat veniam ullamco occaecat do ut. Tempor et esse reprehenderit veniam proident ipsum irure sit ullamco et labore ea excepteur nulla labore ut. Ex aute minim quis tempor in eu id id irure ea nostrud dolor esse.
|
||||
|
||||
[[Top]](#top)
|
||||
|
||||
## <a name="Lists"></a>Lists
|
||||
|
||||
### Ordered List
|
||||
|
||||
1. Longan
|
||||
2. Lychee
|
||||
3. Excepteur ad cupidatat do elit laborum amet cillum reprehenderit consequat quis.
|
||||
Deserunt officia esse aliquip consectetur duis ut labore laborum commodo aliquip aliquip velit pariatur dolore.
|
||||
4. Marionberry
|
||||
5. Melon
|
||||
- Cantaloupe
|
||||
- Honeydew
|
||||
- Watermelon
|
||||
6. Miracle fruit
|
||||
7. Mulberry
|
||||
|
||||
### Unordered List
|
||||
|
||||
- Olive
|
||||
- Orange
|
||||
- Blood orange
|
||||
- Clementine
|
||||
- Papaya
|
||||
- Ut aute ipsum occaecat nisi culpa Lorem id occaecat cupidatat id id magna laboris ad duis. Fugiat cillum dolore veniam nostrud proident sint consectetur eiusmod irure adipisicing.
|
||||
- Passionfruit
|
||||
|
||||
[[Top]](#top)
|
||||
|
||||
## <a name="Horizontal"></a>Horizontal rule
|
||||
|
||||
In dolore velit aliquip labore mollit minim tempor veniam eu veniam ad in sint aliquip mollit mollit. Ex occaecat non deserunt elit laborum sunt tempor sint consequat culpa culpa qui sit. Irure ad commodo eu voluptate mollit cillum cupidatat veniam proident amet minim reprehenderit.
|
||||
|
||||
---
|
||||
|
||||
In laboris eiusmod reprehenderit aliquip sit proident occaecat. Non sit labore anim elit veniam Lorem minim commodo eiusmod irure do minim nisi. Dolor amet cillum excepteur consequat sint non sint.
|
||||
|
||||
[[Top]](#top)
|
||||
|
||||
## <a name="Table"></a>Table
|
||||
|
||||
Duis sunt ut pariatur reprehenderit mollit mollit magna dolore in pariatur nulla commodo sit dolor ad fugiat. Laboris amet ea occaecat duis eu enim exercitation deserunt ea laborum occaecat reprehenderit. Et incididunt dolor commodo consequat mollit nisi proident non pariatur in et incididunt id. Eu ut et Lorem ea ex magna minim ipsum ipsum do.
|
||||
|
||||
| Table Heading 1 | Table Heading 2 | Center align | Right align | Table Heading 5 |
|
||||
| :-------------- | :-------------- | :----------: | ----------: | :-------------- |
|
||||
| Item 1 | Item 2 | Item 3 | Item 4 | Item 5 |
|
||||
| Item 1 | Item 2 | Item 3 | Item 4 | Item 5 |
|
||||
| Item 1 | Item 2 | Item 3 | Item 4 | Item 5 |
|
||||
| Item 1 | Item 2 | Item 3 | Item 4 | Item 5 |
|
||||
| Item 1 | Item 2 | Item 3 | Item 4 | Item 5 |
|
||||
|
||||
Minim id consequat adipisicing cupidatat laborum culpa veniam non consectetur et duis pariatur reprehenderit eu ex consectetur. Sunt nisi qui eiusmod ut cillum laborum Lorem officia aliquip laboris ullamco nostrud laboris non irure laboris. Cillum dolore labore Lorem deserunt mollit voluptate esse incididunt ex dolor.
|
||||
|
||||
[[Top]](#top)
|
||||
|
||||
## <a name="Code"></a>Code
|
||||
|
||||
### Inline code
|
||||
|
||||
Ad amet irure est magna id mollit Lorem in do duis enim. Excepteur velit nisi magna ea pariatur pariatur ullamco fugiat deserunt sint non sint. Duis duis est `code in text` velit velit aute culpa ex quis pariatur pariatur laborum aute pariatur duis tempor sunt ad. Irure magna voluptate dolore consectetur consectetur irure esse. Anim magna `<strong>in culpa qui officia</strong>` dolor eiusmod esse amet aute cupidatat aliqua do id voluptate cupidatat reprehenderit amet labore deserunt.
|
||||
|
||||
### Highlighted
|
||||
|
||||
Et fugiat ad nisi amet magna labore do cillum fugiat occaecat cillum Lorem proident. In sint dolor ullamco ad do adipisicing amet id excepteur Lorem aliquip sit irure veniam laborum duis cillum. Aliqua occaecat minim cillum deserunt magna sunt laboris do do irure ea nostrud consequat ut voluptate ex.
|
||||
|
||||
```go
|
||||
package main
|
||||
|
||||
import (
|
||||
"fmt"
|
||||
"net/http"
|
||||
)
|
||||
|
||||
func handler(w http.ResponseWriter, r *http.Request) {
|
||||
fmt.Fprintf(w, "Hi there, I love %s!", r.URL.Path[1:])
|
||||
}
|
||||
|
||||
func main() {
|
||||
http.HandleFunc("/", handler)
|
||||
http.ListenAndServe(":8080", nil)
|
||||
}
|
||||
```
|
||||
|
||||
Ex amet id ex aliquip id do laborum excepteur exercitation elit sint commodo occaecat nostrud est. Nostrud pariatur esse veniam laborum non sint magna sit laboris minim in id. Aliqua pariatur pariatur excepteur adipisicing irure culpa consequat commodo et ex id ad.
|
||||
|
||||
[[Top]](#top)
|
||||
|
||||
## <a name="Inline"></a>Inline elements
|
||||
|
||||
Sint ea anim ipsum ad commodo cupidatat do **exercitation** incididunt et minim ad labore sunt. Minim deserunt labore laboris velit nulla incididunt ipsum nulla. Ullamco ad laborum ea qui et anim in laboris exercitation tempor sit officia laborum reprehenderit culpa velit quis. **Consequat commodo** reprehenderit duis [irure](#!) esse esse exercitation minim enim Lorem dolore duis irure. Nisi Lorem reprehenderit ea amet excepteur dolor excepteur magna labore proident voluptate ipsum. Reprehenderit ex esse deserunt aliqua ea officia mollit Lorem nulla magna enim. Et ad ipsum labore enim ipsum **cupidatat consequat**. Commodo non ea cupidatat magna deserunt dolore ipsum velit nulla elit veniam nulla eiusmod proident officia.
|
||||
|
||||
![Super wide](https://images.unsplash.com/photo-1710170601257-242514895755?q=80&w=2832&auto=format&fit=crop&ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D)
|
||||
|
||||
_Proident sit veniam in est proident officia adipisicing_ ea tempor cillum non cillum velit deserunt. Voluptate laborum incididunt sit consectetur Lorem irure incididunt voluptate nostrud. Commodo ut eiusmod tempor cupidatat esse enim minim ex anim consequat. Mollit sint culpa qui laboris quis consectetur ad sint esse. Amet anim anim minim ullamco et duis non irure. Sit tempor adipisicing ea laboris `culpa ex duis sint` anim aute reprehenderit id eu ea. Aute [excepteur proident](#!) Lorem minim adipisicing nostrud mollit ad ut voluptate do nulla esse occaecat aliqua sint anim.
|
||||
|
||||
![Not so big](https://placehold.co/600x400/000000/FFFFFF/png)
|
||||
|
||||
Incididunt in culpa cupidatat mollit cillum qui proident sit. In cillum aliquip incididunt voluptate magna amet cupidatat cillum pariatur sint aliqua est _enim **anim** voluptate_. Magna aliquip proident incididunt id duis pariatur eiusmod incididunt commodo culpa dolore sit. Culpa do nostrud elit ad exercitation anim pariatur non minim nisi **adipisicing sunt _officia_**. Do deserunt magna mollit Lorem commodo ipsum do cupidatat mollit enim ut elit veniam ea voluptate.
|
||||
|
||||
Reprehenderit non eu quis in ad elit esse qui aute id [incididunt](#!) dolore cillum. Esse laboris consequat dolor anim exercitation tempor aliqua deserunt velit magna laboris. Culpa culpa minim duis amet mollit do quis amet commodo nulla irure.
|
||||
|
||||
[[Top]](#top)
|
||||
|
||||
## MDX
|
||||
|
||||
```js
|
||||
---
|
||||
publishDate: 'Aug 02 2022'
|
||||
title: 'Markdown elements demo post'
|
||||
---
|
||||
import Logo from "~/components/Logo.astro";
|
||||
|
||||
## MDX
|
||||
|
||||
<Logo />
|
||||
```
|
||||
|
||||
<div style="border:1px dashed;padding: 10px 5px">
|
||||
<Logo />
|
||||
</div>
|
||||
|
||||
## Astro Embed
|
||||
|
||||
### Youtube
|
||||
|
||||
<YouTube id="y9n6HkftavM" />
|
||||
|
||||
### Tweet
|
||||
|
||||
<Tweet id="https://twitter.com/Steve8708/status/1598713161339015173" />
|
||||
|
||||
### Vimeo
|
||||
|
||||
<Vimeo id="178430038" />
|
||||
|
||||
[[Top]](#top)
|
92
src/content/post/the_farming_communit.md
Normal file
@ -0,0 +1,92 @@
|
||||
---
|
||||
publishDate: 2024-04-26T00:00:00Z
|
||||
title: Spotlight on the ThreeFold Farming Community
|
||||
excerpt: ThreeFold Farmers provide decentralized cloud capacity, shape the grid's future, and share resources to build a fair and connected world.
|
||||
image: ~/assets/images/blog/the_farming_community.png
|
||||
category: farming
|
||||
tags:
|
||||
- technology
|
||||
- threefold_cloud
|
||||
- community
|
||||
metadata:
|
||||
canonical: https://astrowind.vercel.app/how-to-customize-astrowind-to-your-brand
|
||||
---
|
||||
|
||||
The ThreeFold community consists of many different roles creating a whole [ecosystem](https://www.threefold.io/blog/tf-ecosystem-comes-alive/) that contributes to the growth of the ThreeFold Grid and makes it more reliable and stable. Today, we're spotlighting the farming community, the backbone of the ThreeFold Grid.
|
||||
|
||||
### **Who are the farmers and what exactly do these farmers do?**
|
||||
|
||||
Think of a ThreeFold Farmer as a digital pioneer who connects their capacity to the ThreeFold Grid, becoming a cloud service provider. They come from all corners of the globe, driven by a common goal: to contribute to the growth of ThreeFold’s decentralized cloud infrastructure.
|
||||
Currently, we boast approximately 950 farmers running an impressive ±2500 nodes. This translates to a whopping capacity of:
|
||||
|
||||
<br>
|
||||
|
||||
- Cores: 64,290
|
||||
- RAM: 434.85 TB
|
||||
- SSD: 8.46 PB
|
||||
- HDD: 20 PB
|
||||
|
||||
</br>
|
||||
|
||||
The farming community keeps the digital gears turning. Whether they purchase a 3Node from the marketplace or build their nodes, they're providing essential capacity to the ThreeFold Grid. In return for their contributions, they're rewarded with ThreeFold Tokens (TFTs), the currency of the ThreeFold ecosystem.
|
||||
|
||||
</br>
|
||||
|
||||
Farmers are rewarded based on their uptime—the number of hours, minutes, and seconds their node has been online. This data is meticulously tracked by ThreeFold's blockchain, TFChain, and used to determine their monthly rewards. However, we're always evolving and we just passed a vote on the ThreeFold DAO where we decided that, in the future, farmers would be rewarded based on their utilization.
|
||||
|
||||
</br>
|
||||
|
||||
ThreeFold Farmers not only provide capacity but also take the opportunity of ThreeFold being an open-source project to develop scripts and tools like a [Python script for minting](https://forum.threefold.io/t/farm-earnings-data-capture-made-easy/4251), a telegram for [liquidity pool USDC/TFT](https://t.me/threefold/42257/54497), and Telegram channels for their local community where English is not their primary language so that they can get help when they need it, and much more.
|
||||
|
||||
</br>
|
||||
|
||||
The ThreeFold farming community is an integral part of our [decentralized autonomous organization (DAO)](https://manual.grid.tf/documentation/dashboard/tfchain/tf_dao.html). A farmer's participation in the DAO discussions and proposals is pivotal as we chart the course for the grid's evolution, from our current version 3.14 release and beyond. Together, we're actively building the grid's future, thanks to our dedicated farmers' collaborative efforts. Join us, share your ideas, and let's shape the future of the ThreeFold Grid together.
|
||||
|
||||
### **The Future of the Farming Community**
|
||||
|
||||
#### **The TF Cooperative**
|
||||
|
||||
ThreeFold is transitioning the management of TF Grid to a cooperative, empowering all of us to work toward our common goals more effectively. This shift represents a step towards a more collaborative and inclusive future for the TFGrid. As we enter the commercialization phase of the project, a cooperative model also brings a trusted form of decentralized governance and will enable us to bring more reliability to the grid.
|
||||
|
||||
</br>
|
||||
|
||||
The formation of the ThreeFold Cooperative (TF COOP) brings several planned changes for farmers and their interaction with the TFGrid:
|
||||
|
||||
<br>
|
||||
|
||||
- **Democratic Governance**: TF COOP introduces a system where farmers can vote on decisions based on their TFT holdings (1 TFT = 1 vote), giving them a voice in the cooperative's direction.
|
||||
- **Farming Rewards**: Farmers will continue to earn rewards based on the quality of their nodes and network uptime. This encourages high standards and benefits both farmers and users.
|
||||
- **Compliance**: Farmers must follow KYC/AML (Know Your Customer/Anti-Money Laundering) rules for transparency and accountability.
|
||||
- **Service Level Agreements (SLAs)**: Larger farmers may sign formal contracts with DMCC or TF COOP, providing stability and predictability.
|
||||
- **Capacity Resale and Utilization Rewards**: TF COOP will resell capacity and distribute profits. Farmers receive 50% of the revenue from their node utilization.
|
||||
- **Node Information and Transparency**: Farmers can benefit from tracking more node data in the explorer, helping potential users select quality nodes.
|
||||
- **Governance Involvement**: Farmers, as cooperative members, can impact management and operations, aligning their interests with the TFGrid's success.
|
||||
|
||||
#### **Farming Pool**
|
||||
|
||||
[Farming Pools](https://www.threefold.io/blog/farming-pools/) are a new feature planned for version 4.0 that helps improve trust and quality in our network. Farmers join these pools and agree to standards like uptime and response time. They can set their prices for services like storage and computing power. By staking tokens, farmers commit to these standards and risk losing some of their stakes if they don't meet their promises. This keeps the network reliable and fair while allowing farmers more control over their services.
|
||||
|
||||
</br>
|
||||
|
||||
These pools can also act as hubs for supporting farmers with training and help them understand if their nodes are working well. Sales of preconfigured hardware is an additional optional function of the pools, while all pools operate as a business that takes a margin on the farming rewards of the farmers belonging to the pool. Beyond support, the added value for the farmers is that pools ensure a level of service and quality that can attract users and bring additional revenues to the farmers, including the potential of active marketing of the pool's capacity.
|
||||
|
||||
### **Conclusion**
|
||||
|
||||
The farming community plays a key role in the smooth operation and growth of the ThreeFold Grid. These farmers shape the grid's future by offering the capacity for a more decentralized digital world. Their work goes beyond earning rewards, as they contribute nodes to a global network and share resources and tools that strengthen the community, which will be showcased in our upcoming blogs. Thanks to their efforts, the grid is thriving and paving the way for a fairer, more connected world.
|
||||
|
||||
#### Get involved:
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
|
||||
Join our [farmer's chat](https://t.me/threefoldfarmers) to talk with the community</li>
|
||||
|
||||
<li>
|
||||
|
||||
[Learn](https://manual.grid.tf/) about expanding the grid or adding on top of it.</li>
|
||||
|
||||
<li>
|
||||
|
||||
[Stay updated](https://t.me/threefoldnews) with news and community discussions.</li>
|
||||
|
||||
</ul>
|
@ -1,62 +0,0 @@
|
||||
---
|
||||
publishDate: 2023-08-09T00:00:00Z
|
||||
title: Useful tools and resources to create a professional website
|
||||
excerpt: Explore vital tools and resources for a sleek website. From design to functionality, our guide elevates your online presence.
|
||||
image: https://images.unsplash.com/photo-1637144113536-9c6e917be447?ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D&auto=format&fit=crop&w=1674&q=80
|
||||
tags:
|
||||
- front-end
|
||||
- tools
|
||||
- resources
|
||||
---
|
||||
|
||||
## Magna nunc senectus torquent per fusce sapien ligula tempus cra
|
||||
|
||||
Lorem ipsum dolor sit amet consectetur adipiscing, elit fusce imperdiet gravida velit massa, ligula aenean suscipit sociis lacinia. Sapien scelerisque rutrum sem accumsan orci imperdiet aliquam inceptos aliquet tempus ornare, netus nostra nam nunc platea pulvinar urna et suscipit pellentesque, aenean congue sociis non tellus quis proin etiam venenatis pretium. Nibh senectus lacinia volutpat nostra taciti ac posuere, dictum ultricies dictumst luctus in vehicula, mus molestie venenatis penatibus ridiculus elementum. Phasellus sollicitudin dignissim parturient tempor cubilia erat massa eleifend dapibus, condimentum cras tortor eu sem dictumst non. Faucibus neque est malesuada nostra luctus maecenas at condimentum, arcu eros vulputate curabitur blandit mollis volutpat, lectus leo dictumst duis semper tempor hendrerit. Egestas scelerisque fusce torquent cubilia consequat conubia lacus et mollis, condimentum taciti elementum sapien risus vulputate est.
|
||||
|
||||
Tristique eleifend enim praesent mollis sem leo, molestie dictum penatibus sodales consequat ligula nulla, platea feugiat aptent sapien turpis. Mollis mus ac taciti maecenas pretium hendrerit proin accumsan, mattis dictumst netus nunc facilisi morbi cursus euismod quis, a commodo nulla integer varius enim vehicula. Consequat mi risus vulputate ullamcorper sociosqu pretium molestie cursus, parturient viverra non tempor tellus convallis vitae eleifend mus, bibendum pellentesque imperdiet vivamus nunc phasellus iaculis. Volutpat est ac dictumst eleifend maecenas torquent quam hac, mollis aliquam mattis euismod ornare risus fringilla proin nisi, sem fermentum primis ultrices varius etiam id. Posuere nunc mus curabitur condimentum lobortis euismod donec tincidunt ridiculus, tristique senectus cum taciti quam blandit leo malesuada, sociis nullam cras litora sem laoreet sed nec.
|
||||
|
||||
## Magna lacus tortor luctus platea co
|
||||
|
||||
- Luctus molestie taciti aliquam dictumst imperdiet, donec torquent nisi.
|
||||
|
||||
- Montes cursus habitant risus platea senectus, lectus sagittis mi.
|
||||
|
||||
- Eleifend facilisi quam ultricies, accumsan aliquet euismod velit, sem tortor.
|
||||
|
||||
- Senectus nisl potenti congue sociosqu at, porttitor habitant vivamus.
|
||||
|
||||
Nostra dictum porta consequat quisque diam nisl iaculis velit varius, placerat curabitur risus commodo condimentum morbi eros dictumst phasellus, tempor duis libero ultrices est rhoncus mattis nam. Quisque lectus massa lobortis nulla enim, praesent eu ut elementum. Felis placerat nibh donec erat platea rutrum taciti cursus, elementum metus semper feugiat risus tellus nulla, aliquam hendrerit faucibus inceptos commodo justo porta.
|
||||
|
||||
Cursus imperdiet montes natoque potenti suscipit facilisi porta mollis posuere consequat, aliquam turpis tortor libero viverra rhoncus accumsan inceptos blandit convallis diam, penatibus ut pretium in duis leo auctor proin quisque. Sollicitudin inceptos quam molestie sociis habitasse class sapien vivamus facilisis, consequat ante vehicula velit tempor cum rutrum magnis, eget semper quisque turpis pretium praesent per faucibus. Ullamcorper blandit taciti primis sed pharetra inceptos duis, eu nisi ac fringilla tellus accumsan iaculis, morbi integer at purus hac est. Elementum hac lacus per in posuere erat ad, egestas dapibus malesuada suscipit nunc interdum, mi risus auctor pretium lectus massa. Condimentum nullam molestie tincidunt sodales luctus parturient est et congue hendrerit vel vulputate iaculis, curabitur sollicitudin quisque magna nostra nisl nam massa viverra donec neque class.
|
||||
|
||||
Euismod tempus potenti interdum fusce placerat habitant, taciti turpis faucibus curabitur tempor felis porta, sed aenean mi arcu magnis. Pellentesque tincidunt aptent eget nisi convallis lobortis sapien, habitasse sollicitudin proin vehicula ridiculus duis congue, himenaeos lectus vitae nulla taciti ante. Enim commodo non taciti ultricies donec iaculis aliquet interdum, dictumst a pulvinar lacus cursus fames praesent cras ad, rutrum nostra dis accumsan primis euismod sagittis. Eu habitant euismod mattis at congue fusce ad commodo litora himenaeos aenean, porta lobortis suscipit pulvinar magna facilisi nullam ante non senectus, urna volutpat sodales vitae varius lectus tincidunt montes rutrum vulputate. Enim cum habitant morbi maecenas nisl imperdiet a egestas velit, gravida laoreet hendrerit rutrum molestie fames sapien euismod turpis metus, faucibus class sed primis leo nam malesuada fermentum.
|
||||
|
||||
Semper etiam tellus a risus lobortis dictumst sem massa eros, eget curae gravida accumsan hac parturient nulla fringilla convallis, condimentum torquent placerat mauris conubia augue mattis leo. Dictum tincidunt quis risus volutpat netus mi suscipit parturient suspendisse vestibulum, ad lacus dictumst luctus nec fusce ultricies vivamus. Dui sociis nulla suscipit gravida mi arcu netus, vitae mus donec dapibus nascetur id ante urna, egestas viverra auctor sodales litora enim rutrum, sapien molestie imperdiet ut massa elementum. Aptent ante risus erat malesuada nec porta, ligula nascetur dictum nunc turpis natoque, tristique conubia netus arcu a.
|
||||
|
||||
Nam scelerisque ridiculus suspendisse viverra conubia et fermentum nascetur turpis quisque, vestibulum cubilia curae per feugiat lectus rhoncus suscipit neque. Urna habitasse mus hac fringilla rutrum sodales, nullam aliquam porttitor quis vehicula arcu class, in felis placerat mattis vestibulum habitant, mauris eros dapibus penatibus viverra. Senectus tristique molestie scelerisque quisque mus augue facilisi massa, ac viverra dapibus vehicula nostra vel nam, posuere montes parturient auctor eu ultrices natoque. Quam fringilla volutpat morbi in per aliquet laoreet a maecenas, lacus velit mauris purus ultricies sociosqu pulvinar netus sodales, convallis placerat turpis tellus nullam libero leo aptent. Praesent lacus ultricies per ligula taciti aenean conubia parturient, feugiat sodales viverra urna cubilia etiam nibh curabitur congue, tristique nisl at elementum dis natoque commodo.
|
||||
|
||||
Sagittis erat velit integer cursus congue viverra, conubia himenaeos egestas ultricies praesent, hac litora mattis non venenatis. Duis libero morbi curae potenti litora vitae sed etiam consequat magna ultricies, magnis fermentum vehicula feugiat tortor ad quis orci rhoncus per porta, ante mi gravida dis nostra tempor lobortis aenean convallis molestie. Ligula fusce blandit ac accumsan magnis rutrum nostra velit maecenas, netus lobortis himenaeos purus justo sapien posuere libero, cum etiam urna mi ultrices est sociis tortor. Neque inceptos quisque vestibulum tempor phasellus id himenaeos magna suspendisse a in nunc cursus, morbi dignissim ornare non auctor massa iaculis mus nec elementum ultricies maecenas. Scelerisque maecenas ultrices integer gravida dis cursus, sed at semper libero iaculis varius, justo augue nec tincidunt suspendisse.
|
||||
|
||||
Rutrum augue natoque felis non vestibulum nam duis, quam praesent taciti himenaeos class vel dis rhoncus, dapibus pulvinar etiam ridiculus curae nibh blandit, scelerisque cursus nostra pretium suspendisse vehicula. Etiam sem metus eleifend suscipit felis suspendisse ut, velit fames habitant semper placerat fusce cras, nunc venenatis platea aenean euismod libero. In eu eget pellentesque libero egestas suspendisse quis tristique torquent nulla, magnis dis malesuada purus quam platea aliquet tortor odio. Accumsan nostra augue lobortis elementum justo sociosqu posuere aptent est, nisl metus conubia tellus sollicitudin lacus inceptos. Morbi mauris aenean malesuada arcu fusce libero venenatis commodo iaculis litora dis, erat parturient class sed facilisi mus a nec dictum.
|
||||
|
||||
Senectus platea dapibus volutpat dictum pharetra cursus netus cras, arcu sociis ornare potenti porttitor tempus sollicitudin, ullamcorper duis nam convallis sapien pretium conubia. Mi metus vivamus cum id semper fringilla senectus scelerisque pretium placerat sociis rhoncus pulvinar porttitor accumsan, curae ligula fermentum mus hendrerit ridiculus condimentum per suscipit rutrum sociosqu odio pellentesque suspendisse. Dui massa nulla suscipit duis metus mollis pellentesque, scelerisque posuere interdum ligula cum dignissim sed, placerat ante ultrices mi netus augue. Eu porttitor malesuada diam morbi torquent egestas magnis tempus metus imperdiet nisl, ad sociis lectus neque mauris gravida habitant primis lobortis. Phasellus mattis nulla fames parturient pharetra pretium egestas, diam rhoncus placerat lectus maecenas dictumst sed cum, justo non ac volutpat morbi enim.
|
||||
|
||||
Justo fringilla morbi netus habitasse varius primis eu magna, tristique accumsan mus enim lectus cubilia convallis auctor, nunc imperdiet erat mollis rutrum vel turpis. Justo purus laoreet eros turpis interdum et ridiculus torquent integer nunc, himenaeos eu tellus proin scelerisque tincidunt congue posuere ultricies vestibulum auctor, aliquet semper varius placerat imperdiet non nisl cubilia fermentum. Feugiat nisl himenaeos cum metus mi est ac, euismod elementum velit tempus dictum mauris, bibendum faucibus cubilia phasellus nulla ornare. Etiam justo venenatis varius laoreet sociis montes dignissim, elementum ligula malesuada euismod praesent magnis auctor, eleifend class egestas a vestibulum blandit. Scelerisque potenti facilisis torquent mollis nisi felis et sed, aptent tortor platea non quisque nec accumsan inceptos, velit molestie nunc enim cubilia egestas per.
|
||||
|
||||
Ultrices morbi et potenti eros aenean condimentum magnis est felis porta, dictumst taciti inceptos etiam ultricies cubilia hac torquent tempor vulputate, sodales erat semper vestibulum dignissim sociis viverra suscipit sagittis. Justo non auctor penatibus iaculis sed in volutpat pretium feugiat lectus rutrum, curabitur sociosqu sapien semper a laoreet augue primis fringilla dui. Fringilla iaculis blandit feugiat euismod congue morbi erat eros, mi dis egestas facilisi volutpat risus cras porta, orci vivamus turpis conubia est commodo torquent. Lectus euismod maecenas potenti in ac natoque sed ullamcorper ridiculus, diam fringilla condimentum eget convallis hendrerit varius pellentesque. Feugiat cras nullam tristique leo nisl dignissim lacinia aenean vivamus potenti consequat, vulputate curabitur sed risus mus suspendisse litora sollicitudin tempor.
|
||||
|
||||
Egestas hac arcu dapibus placerat proin aptent a pellentesque posuere, in condimentum fames facilisi maecenas semper nisl mus, sodales donec elementum praesent enim ac dictum ridiculus. Justo in nibh luctus vitae etiam nisl ac quisque fringilla, habitasse sociosqu curae inceptos semper ut mi hac, congue volutpat himenaeos sed augue morbi tellus nec. Congue libero posuere varius eleifend tristique nascetur integer ullamcorper, est leo vitae mi erat enim augue urna magnis, elementum ultricies pulvinar blandit arcu malesuada duis. Cubilia nulla vel et integer sed pellentesque gravida felis pulvinar mollis ultricies mi, montes suspendisse vestibulum aliquet dui in magna nunc ridiculus aliquam elementum. Justo erat montes enim felis eu sed vivamus faucibus imperdiet ac luctus vulputate, cursus accumsan blandit et mus sodales conubia cubilia phasellus leo.
|
||||
|
||||
Velit in felis penatibus semper laoreet libero tristique condimentum sem montes suscipit, morbi habitant gravida tellus quisque neque torquent lobortis interdum. Ridiculus sollicitudin suscipit semper quam eleifend at, neque tincidunt magnis penatibus dui orci, praesent vulputate himenaeos feugiat vel. Habitasse senectus a sodales dapibus nulla auctor sagittis nullam molestie, imperdiet volutpat quam odio facilisis nostra magnis dictumst, sociis cum erat facilisi dignissim urna lacus magna. Primis porttitor nullam quis vestibulum mi dictumst magna dapibus taciti magnis inceptos fames, purus etiam auctor metus bibendum felis accumsan id aliquet suscipit imperdiet. Pellentesque sem velit nulla consequat vehicula cubilia curabitur, platea curae natoque tristique nullam litora, nascetur imperdiet habitant tincidunt suspendisse sociis.
|
||||
|
||||
Platea cum auctor eget consequat elementum lacinia ad aliquet orci, imperdiet nibh penatibus ac dictum rutrum mollis ante cursus, volutpat scelerisque velit ornare in vivamus pharetra blandit. Cum mattis interdum in diam purus sapien lacinia gravida, semper montes vestibulum rhoncus auctor morbi dictum. Mus semper erat mollis taciti sapien ultrices accumsan ante magna eros at commodo, malesuada diam nullam massa curabitur lobortis felis interdum nisi duis pellentesque. Accumsan faucibus tristique augue enim hac ante feugiat, porttitor phasellus condimentum nulla maecenas dignissim at platea, facilisis nam donec primis habitasse ac. Nec convallis ridiculus potenti primis faucibus erat eget metus mollis, luctus ac fusce condimentum orci suscipit volutpat malesuada mi, velit feugiat pharetra sem turpis est accumsan porta, ligula torquent lacus tristique a senectus tortor dignissim.
|
||||
|
||||
Pharetra eleifend vivamus potenti congue proin himenaeos, fusce mi venenatis natoque montes, suscipit commodo porta magnis mattis. Et lobortis mollis libero quis himenaeos felis dis porta, donec iaculis mattis cursus accumsan pulvinar mus etiam, habitasse leo taciti vitae suscipit suspendisse bibendum. Sodales at ante dictumst nostra est risus senectus semper morbi facilisis neque tempus, venenatis penatibus fusce mattis phasellus velit diam iaculis hac tortor class, orci ridiculus varius dis odio cras rutrum porttitor facilisi massa parturient. Augue facilisi nam proin at elementum massa, tellus vestibulum mattis tortor porta, cubilia sodales orci congue vel. Rhoncus nec quam iaculis sapien risus suspendisse dictum tincidunt, vivamus lobortis blandit metus ullamcorper torquent.
|
||||
|
||||
Ante fermentum hac tincidunt nam sodales vestibulum pellentesque ut nulla habitasse, ornare diam facilisis aptent facilisi penatibus arcu congue lacus, lectus fringilla per primis dapibus eu imperdiet erat dictumst. Pulvinar eu ad mauris nulla ac sed nisl ullamcorper natoque etiam fames, platea aliquam dis netus odio dignissim tincidunt quam blandit laoreet, at mollis ridiculus molestie lacus metus nullam suspendisse nibh duis. Suspendisse congue vestibulum fringilla ridiculus tristique sagittis sociosqu integer, volutpat lacinia pulvinar felis aliquam pharetra faucibus dictumst ad, fusce dignissim cursus mauris eget nostra lectus. Lacinia egestas iaculis scelerisque odio gravida ullamcorper, at arcu ligula ornare parturient phasellus laoreet, augue convallis platea tortor aenean.
|
||||
|
||||
Interdum fames lobortis sollicitudin aliquet mus aptent netus, penatibus consequat pulvinar velit enim curae accumsan, maecenas litora mi rutrum sagittis tincidunt. Lacinia malesuada id netus suscipit sapien sociosqu orci habitasse turpis, feugiat donec placerat sed quam hendrerit pellentesque. Erat accumsan ligula id sapien turpis mus nulla lobortis consequat nec, urna habitasse ultrices aliquet vulputate est suspendisse gravida senectus odio, vehicula fusce proin in sed tempor vitae convallis molestie. Nascetur semper feugiat velit hendrerit lacinia nunc, risus quis congue nullam himenaeos commodo porttitor, natoque facilisi ad maecenas faucibus. Dictum id sodales interdum accumsan habitant natoque class parturient mi venenatis aenean, est nam tortor donec lobortis non vehicula magnis lacinia. Feugiat vitae morbi litora vehicula in a, nam ad ultrices auctor sollicitudin, ullamcorper fringilla hendrerit placerat faucibus.
|
||||
|
||||
Nulla nisi ac placerat duis semper mus cursus interdum netus vestibulum, tortor praesent proin nec rhoncus magnis commodo blandit himenaeos purus, volutpat id montes scelerisque suspendisse risus nisl erat dui. Senectus et habitant dis nulla velit faucibus venenatis sapien, dapibus etiam metus eget magnis feugiat tristique. Augue montes elementum pulvinar mollis pellentesque diam cursus tristique vel cubilia erat mus, congue curae sagittis dui quis fusce tortor consequat taciti natoque. Praesent montes erat feugiat sed euismod condimentum potenti malesuada nec, mi vitae suspendisse aptent senectus eleifend faucibus pulvinar scelerisque, augue ornare accumsan pretium magna eu iaculis metus. Suscipit accumsan massa vitae platea ad duis rhoncus fermentum vulputate, interdum pretium metus per aptent enim in facilisis eros, sollicitudin consequat iaculis erat dictumst quisque leo sociis.
|
||||
|
||||
Tempor etiam potenti auctor est ut habitant ac nisl ultrices pulvinar, sem primis tempus lacus aliquam consequat fringilla tristique. Consequat cum rhoncus massa sociis blandit rutrum nisi quam cras vitae fusce, sociosqu erat penatibus convallis fames accumsan eros himenaeos pulvinar sagittis, habitasse primis integer odio nascetur in montes faucibus semper potenti. Diam aliquam fringilla risus phasellus habitasse aenean eu erat, netus nulla pellentesque ut morbi torquent pharetra semper, sed etiam primis in conubia hendrerit velit. Ornare magna dictum purus metus sociosqu pulvinar sed, quam faucibus posuere pretium senectus interdum. Ornare sodales in litora nascetur sociosqu senectus auctor, cras arcu fusce ac inceptos integer tempor aliquam, tristique imperdiet metus hendrerit erat eleifend.
|
@ -15,8 +15,8 @@ export const headerData = {
|
||||
href: getPermalink('/about'),
|
||||
},
|
||||
{
|
||||
text: 'Contact',
|
||||
href: getPermalink('/contact'),
|
||||
text: 'Blog',
|
||||
href: getPermalink('/blog'),
|
||||
},
|
||||
],
|
||||
actions: [{ text: 'Get INCA Nodes', href: 'https://csnkyhwp8b4.typeform.com/to/SnfEE9pj', target: '_blank' }],
|
||||
@ -44,6 +44,7 @@ export const footerData = {
|
||||
title: 'Communication',
|
||||
links: [
|
||||
{ text: 'Contact Us', href: '/contact' },
|
||||
{ text: 'INCA Blog', href: '/blog' },
|
||||
{ text: 'Reach Support', href: 'https://threefoldfaq.crisp.help/en/' },
|
||||
{ text: 'ThreeFold Chat', href: 'https://t.me/threefold' },
|
||||
],
|
||||
|
@ -38,9 +38,9 @@ const metadata = {
|
||||
<Layout metadata={metadata}>
|
||||
<section class="px-6 sm:px-6 py-12 sm:py-16 lg:py-20 mx-auto max-w-4xl">
|
||||
<Headline
|
||||
subtitle="A statically generated blog example with news, tutorials, resources and other interesting content related to AstroWind"
|
||||
subtitle="Read our blog to learn more about Project INCA!"
|
||||
>
|
||||
The Blog
|
||||
Project INCA Blog
|
||||
</Headline>
|
||||
<BlogList posts={page.data} />
|
||||
<Pagination prevUrl={page.url.prev} nextUrl={page.url.next} />
|
||||
|
@ -27,7 +27,7 @@ const metadata = {
|
||||
}}
|
||||
>
|
||||
<Fragment slot="title">
|
||||
Project Internet Capacity <br>is the culmulation of years <br>of work by ThreeFold
|
||||
Project Internet Capacity <br>is the culmination of years <br>of work by ThreeFold
|
||||
</Fragment>
|
||||
|
||||
<Fragment slot="subtitle">
|
||||
|
@ -69,8 +69,8 @@ const metadata = {
|
||||
<Features
|
||||
id="technology"
|
||||
tagline="Purpose"
|
||||
title="Layer 0 for DePIN"
|
||||
subtitle="Project INCA aims to be a Layer 0 for the DePIN community. DePIN projects can run on our decentralized cloud infrastructure, gaining access to a sovereign, decentralized, and reliable storage, network, and compute layer."
|
||||
title="Base Layer for DePIN"
|
||||
subtitle="Project INCA aims to be a base layer for the DePIN community. DePIN projects can run on our decentralized cloud infrastructure, gaining access to a sovereign, decentralized, and reliable storage, network, and compute layer."
|
||||
items={[
|
||||
{
|
||||
title: 'Zero-OS',
|
||||
@ -81,7 +81,7 @@ const metadata = {
|
||||
{
|
||||
title: 'Web2/Web3 + AI Compatible',
|
||||
description:
|
||||
'Compatible with Web2, Web3 and AI: everything can run on our layer 0 infrastructure cloud. If it runs on Linux, it runs on the grid!',
|
||||
'Compatible with Web2, Web3 and AI: everything can run on our base layer infrastructure cloud. If it runs on Linux, it runs on the grid!',
|
||||
icon: 'tabler:world-www',
|
||||
},
|
||||
{
|
||||
@ -176,7 +176,7 @@ const metadata = {
|
||||
|
||||
<Content
|
||||
isReversed
|
||||
tagline="In a nutsell"
|
||||
tagline="In a nutshell"
|
||||
title="What it means to be a truly <br>decentralized and autonomous <br>cloud for everyone"
|
||||
items={[
|
||||
{
|
||||
|
@ -4,7 +4,7 @@ import Hero from '~/components/widgets/Hero.astro';
|
||||
import Layout from '~/layouts/PageLayout.astro';
|
||||
import Content from '~/components/widgets/Content.astro';
|
||||
import CallToAction from '~/components/widgets/CallToAction.astro';
|
||||
import AutonomousCloud from './autonomouscloud_engine.astro'
|
||||
import AutonomousCloud from './autonomouscloud_engine.astro';
|
||||
import Note from '~/components/widgets/Note.astro';
|
||||
|
||||
// import Features3 from '~/components/widgets/Features3.astro';
|
||||
@ -12,7 +12,6 @@ import Note from '~/components/widgets/Note.astro';
|
||||
// import Steps2 from '~/components/widgets/Steps2.astro';
|
||||
// import Steps from '~/components/widgets/Steps.astro';
|
||||
|
||||
|
||||
const metadata = {
|
||||
title: 'Technology',
|
||||
};
|
||||
@ -21,25 +20,23 @@ const metadata = {
|
||||
<Layout metadata={metadata}>
|
||||
<!-- Hero Widget ******************* -->
|
||||
|
||||
<Hero
|
||||
tagline="Technology"
|
||||
>
|
||||
<Hero tagline="Technology">
|
||||
<Fragment slot="title">
|
||||
Our technology enables<br>
|
||||
Our technology enables<br />
|
||||
a planetary-scale grid
|
||||
<br> of interconnected nodes
|
||||
|
||||
<br /> of interconnected nodes
|
||||
</Fragment>
|
||||
|
||||
<Fragment slot="subtitle">
|
||||
<br><br>Over years of research and development, together with the community we've built out a worldwide peer-to-peer
|
||||
and energy-efficient network of interconnected nodes with endless possibilities. We are at the start of a journey to millions of nodes.
|
||||
<br><br>Mycelium Network allows for the shorter distance to be made at all time,
|
||||
Zero-OS allows for self-healing and autonomous cloud services,
|
||||
Quantum Safe File System ensures data is never lost and our blockchain
|
||||
<br /><br />Over years of research and development, together with the community we've built out a worldwide
|
||||
peer-to-peer and energy-efficient network of interconnected nodes with endless possibilities. We are at the start
|
||||
of a journey to millions of nodes.
|
||||
<br /><br />Mycelium Network allows for the shorter distance to be made at all time, Zero-OS allows for
|
||||
self-healing and autonomous cloud services, Quantum Safe File System ensures data is never lost and our blockchain
|
||||
TFChain makes sure transactions are fair and objective.
|
||||
<br> <br>Our stack can be the foundational layer for most web2 and web3 projects out there.
|
||||
<br><br> Let's together create the <i>Unbreakable Internet</i>.
|
||||
<br />
|
||||
<br />Our stack can be the foundational layer for most web2 and web3 projects out there.
|
||||
<br /><br /> Let's together create the <i>Unbreakable Internet</i>.
|
||||
</Fragment>
|
||||
</Hero>
|
||||
|
||||
@ -71,14 +68,14 @@ const metadata = {
|
||||
<Fragment slot="content">
|
||||
<h2 class="text-2xl font-bold tracking-tight dark:text-white sm:text-3xl mb-2">Zero-OS</h2>
|
||||
<p>
|
||||
Zero-OS is a custom made stateless and lightweight operating system designed to host anything that runs on Linux,
|
||||
in a more decentralized way without giving up all required control and visbility.
|
||||
<br><br>
|
||||
Zero-OS is a custom made stateless and lightweight operating system designed to host anything that runs on
|
||||
Linux, in a more decentralized way without giving up all required control and visbility.
|
||||
<br /><br />
|
||||
Zero-OS is the engine of the ThreeFold Grid.
|
||||
<br>Zero-OS is compatible with almost all computer hardware.
|
||||
<br><br>
|
||||
Zero-OS allows anyone to become a hosting service provider without being a cloud expert.
|
||||
The operating system works fully autonomous and does not require interventions.
|
||||
<br />Zero-OS is compatible with almost all computer hardware.
|
||||
<br /><br />
|
||||
Zero-OS allows anyone to become a hosting service provider without being a cloud expert. The operating system works
|
||||
fully autonomous and does not require interventions.
|
||||
</p>
|
||||
</Fragment>
|
||||
|
||||
@ -87,7 +84,6 @@ const metadata = {
|
||||
</Fragment>
|
||||
</Content>
|
||||
|
||||
|
||||
<Content
|
||||
id="mycelium"
|
||||
columns={3}
|
||||
@ -114,12 +110,13 @@ const metadata = {
|
||||
<Fragment slot="content">
|
||||
<h2 class="text-2xl font-bold tracking-tight dark:text-white sm:text-3xl mb-2">Mycelium</h2>
|
||||
<p>
|
||||
Mycelium is the result of 10 years of trial and error on our search for a more efficient network system for facilitating faster more reliable communication between machines and people.
|
||||
<br><br>Our goal was to create a network system capable of identifying and following
|
||||
the fastest path, stay up and running even in challenging conditions (e.g. fiber cuts), and secure all traffic.
|
||||
<br><br>With Mycelium, data traverses the most efficient routes, utilizing any available internet connection,
|
||||
including peer-to-peer network systems like mesh wireless.
|
||||
All traffic is end-to-end encrypted, effectively preventing man-in-the-middle attacks.
|
||||
Mycelium is the result of 10 years of trial and error on our search for a more efficient network system for
|
||||
facilitating faster more reliable communication between machines and people.
|
||||
<br /><br />Our goal was to create a network system capable of identifying and following the fastest path, stay
|
||||
up and running even in challenging conditions (e.g. fiber cuts), and secure all traffic.
|
||||
<br /><br />With Mycelium, data traverses the most efficient routes, utilizing any available internet
|
||||
connection, including peer-to-peer network systems like mesh wireless. All traffic is end-to-end encrypted,
|
||||
effectively preventing man-in-the-middle attacks.
|
||||
</p>
|
||||
</Fragment>
|
||||
|
||||
@ -128,7 +125,6 @@ const metadata = {
|
||||
</Fragment>
|
||||
</Content>
|
||||
|
||||
|
||||
<Content
|
||||
isReversed
|
||||
id="qsfs"
|
||||
@ -153,17 +149,16 @@ const metadata = {
|
||||
loading: 'eager',
|
||||
}}
|
||||
>
|
||||
|
||||
<AutonomousCloud/>
|
||||
<AutonomousCloud />
|
||||
|
||||
<Fragment slot="content">
|
||||
<h2 class="text-2xl font-bold tracking-tight dark:text-white sm:text-3xl mb-2">Quantum-Safe Storage</h2>
|
||||
<p>
|
||||
The Quantum-Safe Storage System is a decentralized, globally distributed data storage system.
|
||||
<br><br>The benefits are incredible: Up to 10x more efficient (power and usage of hardware).
|
||||
Super reliable, data can not be lost or corrupted. Safe, private and scalable.
|
||||
<br><br>Sovereign, data is close to you in the country of your choice.
|
||||
Truly peer-to-peer, by everyone for everyone
|
||||
<br /><br />The benefits are incredible: Up to 10x more efficient (power and usage of hardware). Super reliable,
|
||||
data can not be lost or corrupted. Safe, private and scalable.
|
||||
<br /><br />Sovereign, data is close to you in the country of your choice. Truly peer-to-peer, by everyone for
|
||||
everyone
|
||||
</p>
|
||||
</Fragment>
|
||||
|
||||
@ -200,10 +195,11 @@ const metadata = {
|
||||
<Fragment slot="content">
|
||||
<h2 class="text-2xl font-bold tracking-tight dark:text-white sm:text-3xl mb-2">Smart Contract for IT</h2>
|
||||
<p>
|
||||
The ThreeFold Grid allows for the deterministic deployment of IT workloads involving multiple parties,
|
||||
ensuring that your intended workload becomes operational without the possibility of alteration during the process.
|
||||
<br><br>
|
||||
It's possible to achieve full transparency and reproducibility for any required deployment in relation to AI, Edge Cloud, Web2 and Web3.
|
||||
The ThreeFold Grid allows for the deterministic deployment of IT workloads involving multiple parties, ensuring
|
||||
that your intended workload becomes operational without the possibility of alteration during the process.
|
||||
<br /><br />
|
||||
It's possible to achieve full transparency and reproducibility for any required deployment in relation to AI, Edge
|
||||
Cloud, Web2 and Web3.
|
||||
</p>
|
||||
</Fragment>
|
||||
|
||||
@ -225,9 +221,9 @@ const metadata = {
|
||||
>
|
||||
<Fragment slot="title">Start building today.</Fragment>
|
||||
<Fragment slot="subtitle">
|
||||
The ThreeFold Grid is operational in its 3e generation, <br>check out our manual, let us know what we can improve on and lets build together.
|
||||
The ThreeFold Grid is operational in its 3e generation, <br />check out our manual, let us know what we can
|
||||
improve on and lets build together.
|
||||
</Fragment>
|
||||
|
||||
</CallToAction>
|
||||
|
||||
<!-- Features2 Widget ************** -->
|
||||
@ -239,13 +235,14 @@ const metadata = {
|
||||
items={[
|
||||
{
|
||||
title: 'Wordpress',
|
||||
description: "WordPress is a free and open-source content management system (CMS) powering nearly half of the Internet that allows users to create and manage digital content.",
|
||||
description:
|
||||
'WordPress is a free and open-source content management system (CMS) powering nearly half of the Internet that allows users to create and manage digital content.',
|
||||
icon: 'tabler:brand-wordpress',
|
||||
},
|
||||
{
|
||||
title: 'Nextcloud',
|
||||
description:
|
||||
"Nextcloud is a suite of client-server software for creating and using file hosting services. Nextcloud provides functionality similar to Dropbox, Office 365 or Google Drive.",
|
||||
'Nextcloud is a suite of client-server software for creating and using file hosting services. Nextcloud provides functionality similar to Dropbox, Office 365 or Google Drive.',
|
||||
icon: 'tabler:cloud',
|
||||
},
|
||||
{
|
||||
@ -257,7 +254,7 @@ const metadata = {
|
||||
{
|
||||
title: 'Kubernetes',
|
||||
description:
|
||||
"Kubernetes is the standard container orchestration tool. On the grid, Kubernetes clusters can be deployed out of the box enabling powerful architectures and deployments.",
|
||||
'Kubernetes is the standard container orchestration tool. On the grid, Kubernetes clusters can be deployed out of the box enabling powerful architectures and deployments.',
|
||||
icon: 'tabler:box',
|
||||
},
|
||||
{
|
||||
@ -268,12 +265,14 @@ const metadata = {
|
||||
},
|
||||
{
|
||||
title: 'AI and Machine Learning',
|
||||
description: 'The grid comes built int with GPU functionalities. Access the latest GPUs on the grid and deploy AI workloads. With Nvidia and AMD GPU support, the grid can run the best hardware on the market.',
|
||||
description:
|
||||
'The grid comes built int with GPU functionalities. Access the latest GPUs on the grid and deploy AI workloads. With Nvidia and AMD GPU support, the grid can run the best hardware on the market.',
|
||||
icon: 'tabler:ai',
|
||||
},
|
||||
{
|
||||
title: 'Casperlabs',
|
||||
description: 'Casper Network is a blockchain protocol built from the ground up to remain true to core Web3 principles. It powers scalable, secure & decentralized blockchain solutions.',
|
||||
description:
|
||||
'Casper Network is a blockchain protocol built from the ground up to remain true to core Web3 principles. It powers scalable, secure & decentralized blockchain solutions.',
|
||||
icon: 'tabler:webhook',
|
||||
},
|
||||
{
|
||||
@ -284,12 +283,14 @@ const metadata = {
|
||||
},
|
||||
{
|
||||
title: 'Subsquid',
|
||||
description: "Subsquid is an innovative decentralized data lake and query engine designed to provide developers with performant and permissionless access to data, aiming to build a neutral and open internet. ",
|
||||
description:
|
||||
'Subsquid is an innovative decentralized data lake and query engine designed to provide developers with performant and permissionless access to data, aiming to build a neutral and open internet. ',
|
||||
icon: 'tabler:database-leak',
|
||||
},
|
||||
{
|
||||
title: 'Node Pilot',
|
||||
description: 'Node Pilot is a simple Linux executable that allows users to easily deploy, manage, and monetize crypto nodes. It provides a seamless Docker integration with enterprise-level security.',
|
||||
description:
|
||||
'Node Pilot is a simple Linux executable that allows users to easily deploy, manage, and monetize crypto nodes. It provides a seamless Docker integration with enterprise-level security.',
|
||||
icon: 'tabler:coins',
|
||||
},
|
||||
{
|
||||
@ -300,7 +301,8 @@ const metadata = {
|
||||
},
|
||||
{
|
||||
title: 'Discourse',
|
||||
description: "Discourse is the 100% open source discussion platform built for the next decade of the Internet. Use it as a mailing list, discussion forum, long-form chat room, and more!",
|
||||
description:
|
||||
'Discourse is the 100% open source discussion platform built for the next decade of the Internet. Use it as a mailing list, discussion forum, long-form chat room, and more!',
|
||||
icon: 'tabler:bubble-text',
|
||||
},
|
||||
]}
|
||||
@ -312,6 +314,13 @@ const metadata = {
|
||||
|
||||
<!-- CallToAction Widget *********** -->
|
||||
|
||||
<Note
|
||||
content="Start building today see our manual"
|
||||
title="MANUAL –"
|
||||
linkpath="https://manual.grid.tf"
|
||||
linktitle="https://manual.grid.tf"
|
||||
/>
|
||||
|
||||
<CallToAction
|
||||
actions={[
|
||||
{
|
||||
@ -326,7 +335,8 @@ const metadata = {
|
||||
<Fragment slot="title">Expand the Grid with Us</Fragment>
|
||||
|
||||
<Fragment slot="subtitle">
|
||||
We have the technology for a planetary-scale alternative<br> to mainstream cloud and current monopolistic markets.<br><br>INCA is the Unbreakable Internet.
|
||||
We have the technology for a planetary-scale alternative<br /> to mainstream cloud and current monopolistic markets.<br
|
||||
/><br />INCA is the Unbreakable Internet.
|
||||
</Fragment>
|
||||
</CallToAction>
|
||||
</Layout>
|
||||
|