docs: update README to add portal

marko-js · Nov 16, 2019 · 3dbec36 · 3dbec36
1 parent b8cc684
commit 3dbec36
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/README.md b/README.md
@@ -24,12 +24,14 @@
 
 ## Packages
 
+- [context](https://github.com/marko-js/tags/blob/master/tags/context) -
+  share data through arbitrarily deep Marko components.
 - [match-media](https://github.com/marko-js/tags/blob/master/tags/match-media) -
   media queries directly in your Marko templates.
+- [portal](https://github.com/marko-js/tags/blob/master/tags/portal) -
+  render content somewhere else in the DOM.
 - [subscribe](https://github.com/marko-js/tags/blob/master/tags/subscribe) -
   declarative event subscriptions component.
-- [context](https://github.com/marko-js/tags/blob/master/tags/context) -
-  share data through arbitrarily deep Marko components.
 
 ## Contributing
 

diff --git a/tags/portal/README.md b/tags/portal/README.md
@@ -18,8 +18,6 @@
   </a>
 </h1>
 
-A Portal Component for Marko.js
-
 Portals provide a way to render children into a DOM node that exists outside the DOM hierarchy of the parent component.
 
 A typical use case for portals is when a parent component has an `overflow: hidden` or `z-index` style, but you need the child to visually “break out” of its container. For example, dialogs and tooltips.
-Original file line number
+Diff line change
@@ Expand Up / @@ -18,8 +18,6 @@ @@
       </a>
     </h1>
-    A Portal Component for Marko.js
     Portals provide a way to render children into a DOM node that exists outside the DOM hierarchy of the parent component.
     A typical use case for portals is when a parent component has an `overflow: hidden` or `z-index` style, but you need the child to visually “break out” of its container. For example, dialogs and tooltips.
@@ Expand Down @@