Localize footer texts
Style lists
Format APIv3 content
Style code example blocks
More descriptive key name for API v3 early access form url
Rename partial analytics to google_analytics
Break-down Analytics documentation
Format API v2 content
Move /help to /support
Optimize build output
Build assets only for current flavor
Handle header width per layout
Fix style for retina images
Serve on-demand multiple locales for individual pages and flavor

To make a single page available in other locales for the current
flavor, you have to define it in the frontmatter:

  locale: { some_flavor: ['en', 'el'], another_flavor: ['en', 'tr'] }

EXAMPLE

The `feedspec` page is available in 3 languages: ['en', 'el', 'tr'].

For the `skroutz` flavor, the `feedspec` page should be available in
['en', 'el'].
For the `alve` flavor, the `feedspec` page should be available in
['en', 'tr'].

To achieve it, we have to declare at the frontmatter of:

- `feedspec.en.html.erb`
  locale: { alve: ['en', 'tr'], skroutz: ['en', 'el'] }

- `feedspec.tr.html.erb`
  locale: { alve: ['en', 'tr'] }

- `feedspec.el.html.erb`
  locale: { skroutz: ['en', 'el'] }
Add API email
Proofread Support page
Set flavor from GET param
Show only supported documentation per flavor
Migrate Feedspec documentation
Show inline available locales for Feedspec