Additional spacing for tea-cli page

This commit is contained in:
Thomas Smith 2022-10-18 20:08:37 -04:00
parent 65b16b1190
commit fcafa6c94c

View file

@ -180,31 +180,31 @@
<section>
<div class="container two-boxes">
<div class="row">
<div class="row one-box-down">
<h3>The new foundation of the internet.</h3>
</div>
<div class="row">
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12">
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12 one-box-down">
<h4>teaxyz/cmd</h4>
<p>Homebrew was a massive success for 5 reasons, a big one was “viral contribution” this is a new form of viral contribution. tea is a packaging primitive. We are making it super easy and viral for people to create new tools on top of tea and to satisfy that “I'm a part of this” urge that open source vitality plays up.</p>
</div>
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12">
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12 one-box-down">
<h4>executable markdown</h4>
<p>Markdown has become the ultimate documentation file format (white paper is written in it). Every project has comprehensive readmes. Every dev team documents their internal workspaces with markdown. Were iterating the format by making it able to execute itself.</p>
</div>
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12">
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12 one-box-down">
<h4>universal interpreter</h4>
<p>Making a PM or tool that uses other packages sucks RN. This has led to self contained ecosystems where people make a packaging tool (eg. npm) and then everybody can only use tools within that ecosystem because everything else is too much friction. tea changes this.</p>
</div>
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12">
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12 one-box-down">
<h4>virtual environment</h4>
<p>devshops and open source projects need specific versions of tools and they need the whole team to be on those tools. Currently you either cross your fingers or use Docker. Docker sucks and slows down dev and hinders innovation. Docker is great for deployment but it sucks for dev. tea ensures that checking out a project uses the exact versions of things that project needs whatever platform they are developing on.</p>
</div>
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12">
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12 one-box-down">
<h4>pantries</h4>
<p>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.</p>
</div>
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12">
<div class="col-xxl-4 col-xl-4 col-lg-6 col-md-6 col-sm-12 col-12 one-box-down">
<h4>Executable Blog Posts</h4>
<p>Every blog post and tutorial on dev starts with brew install foo in teas future they will instead do sh <(curl tea.xyz) [<http://blog-post.com/article-url/>](<http://blog-post.com/article-url/>) (we will also release web-buttons that activate tea if installed or install it first otherwise).
</p>