Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix broken headings in Markdown files #711

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
#THIS REPO IS DEPRECATED
##Mixed Mode can be found at [https://github.com/famous/engine](https://github.com/famous/engine)
# THIS REPO IS DEPRECATED
## Mixed Mode can be found at [https://github.com/famous/engine](https://github.com/famous/engine)

If you are looking for the old website with the support material for this version of famous please visit [http://deprecated.famous.org](http://deprecated.famous.org)

Expand Down
4 changes: 2 additions & 2 deletions guides/layout.md
Original file line number Diff line number Diff line change
Expand Up @@ -291,7 +291,7 @@ properties can animate over time. This can be done in one of two methods:
- [push-based](#push)
- [pull-based](#pull)

####<a name="push">Push-based animations</a>
#### <a name="push">Push-based animations</a>

The `StateModifier` class found in Famous/modifiers/StateModifier.js is a push-based
implementation. Here, `StateModifier` has the methods
Expand Down Expand Up @@ -326,7 +326,7 @@ stateModifier.setOpacity(
);
```

####<a name="pull">Pull-based animations</a>
#### <a name="pull">Pull-based animations</a>

The `Modifier` class found in Famous/core/Modifier.js is a pull-based
implementation. The `Modifier` itself doesn't keep any state (like what the
Expand Down
2 changes: 1 addition & 1 deletion guides/migrating-0.2-to-0.3.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ The `initial-scale=1` setting will ensure that the content is displayed correctl

First, let's look at the breaking changes in the v0.3 release of Famo.us:

###src folder
### src folder
All src code is now found in a src/ folder. This will cause issues with any pathing you are currently relying on. Please see the above sections that describe how to properly update your tooling stack accordingly.

### Align & origin
Expand Down
20 changes: 10 additions & 10 deletions guides/render-tree.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ the expectations every web developer has of the DOM, but in a way that doesn't c
performance. The Render Tree is our solution to relative positioning and
semantic structure. In other documentation we'll go into events and animation.

#Overview
# Overview

- [Creating the Tree](#creation)
- [Extending the Tree](#extension)
Expand All @@ -39,7 +39,7 @@ semantic structure. In other documentation we'll go into events and animation.
- [The Big Picture](#review)


##<a name="creation">Creating the Tree</a>
## <a name="creation">Creating the Tree</a>


A tree's starting point is called its root. In HTML, this root is the `<body>` tag.
Expand All @@ -52,7 +52,7 @@ class `famous-container` (we can also pass in a pre-existing DOM element).
```

##<a name="extension">Extending the Tree</a>
## <a name="extension">Extending the Tree</a>


So far we have a pretty boring app. A Context has no visual representation,
Expand All @@ -68,7 +68,7 @@ corresponds to a `<div>` in HTML. This `<div>` will be nested inside of the
surface context.add(surface);
```

##<a name="nodes">Types of Nodes</a>
## <a name="nodes">Types of Nodes</a>


A tree is made up of nodes. In HTML, these nodes are tags like `<div>` or
Expand All @@ -77,7 +77,7 @@ Above, we saw how to add one type of renderable, a Surface, to the Render Tree.
Below, we will examine other kinds of nodes that make up a typical Render Tree.


##<a name="renderables">Renderables</a>
## <a name="renderables">Renderables</a>


Renderables are nodes that get drawn to the screen. We have already been
Expand Down Expand Up @@ -108,7 +108,7 @@ complex composited renderables. These are called Views and will be
discussed [below](#views).


##<a name="modifiers">Modifiers</a>
## <a name="modifiers">Modifiers</a>


A Modifier is another type of Famo.us node that is capable of modifying
Expand Down Expand Up @@ -140,7 +140,7 @@ then the surface will be at `[100px, 200px]` from the top left of the Context.
Modifiers also have more complicated support for layout, like auto-centering
and sizing, but this will be discussed in a different tutorial.

##<a name="chaining">Chaining Nodes</a>
## <a name="chaining">Chaining Nodes</a>


Modifiers affect the render tree beneath them. But that means Modifiers can
Expand All @@ -158,7 +158,7 @@ separating state easy to do. One modifier can handle opacity, another, rotation.
surface
```

##<a name="branching">Branching Nodes</a>
## <a name="branching">Branching Nodes</a>


So far our Render Trees have been linear: one node sequentially following another.
Expand Down Expand Up @@ -191,7 +191,7 @@ Here, `surface1` and `surface2` are both relative to `modifier1`, and
(assuming these modifiers are for translating nodes).


##<a name="views">Views</a>
## <a name="views">Views</a>


So far we've seen that you can add Modifiers and Surfaces to the Render Tree.
Expand Down Expand Up @@ -262,7 +262,7 @@ manageable. And unlike DOM, there is no performance degradation incurred from
nesting structure; everything is flattened by the time it gets to the DOM.


##<a name="review">The Big Picture</a>
## <a name="review">The Big Picture</a>


> It's modifiers all the way down - *Anon*
Expand Down