Highlight features that are yet to come

- Tone down "new as of version" boxes
 - Replace all "New as of 0.5" with "yet to be released" text
 - Use strong red only for "yet to be released" boxes

Fixes #1989
This commit is contained in:
Benjamin Kampmann committed 2016-03-13 11:30:14 +01:00
1 parent 7704175f0d
commit 9af8389616
8 files changed
+12 -6

No files matched your search

+4
View File
@@ -238,6 +238,10 @@ blockquote {
margin-bottom: 30px; margin-bottom: 30px;
} }
blockquote.new-as-of { blockquote.new-as-of {
border-left: 4px solid #f0ad4e;
background-color: #f0dc6e;
}
blockquote.not-yet-released {
border-left: 4px solid #ef5b58; border-left: 4px solid #ef5b58;
background-color: #f9ad76; background-color: #f9ad76;
} }
+1 -1
View File
@@ -1,6 +1,6 @@
# Zero Downtime Deploys # Zero Downtime Deploys
> Plugin management is New as of 0.5.0 > Plugin management is not yet released and only available in master
``` ```
checks <app> Show zero-downtime status checks <app> Show zero-downtime status
+1 -1
View File
@@ -1,6 +1,6 @@
# Deployment Tasks # Deployment Tasks
> New as of 0.5.0 > not yet released and only available in master
Sometimes you need to run a command on at deployment time, but before an app is completely deployed. Sometimes you need to run a command on at deployment time, but before an app is completely deployed.
Common use cases include: Common use cases include:
+1 -1
View File
@@ -42,7 +42,7 @@ Setting `$DOKKU_DOCKERFILE_CACHE_BUILD` to `true` or `false` will enable or disa
### Procfiles and Multiple Processes ### Procfiles and Multiple Processes
> New as of 0.5.0 > not yet released and only available in master
You can also customize the run command using a `Procfile`, much like you would on Heroku or You can also customize the run command using a `Procfile`, much like you would on Heroku or
with a buildpack deployed app. The `Procfile` should contain one or more lines defining [process with a buildpack deployed app. The `Procfile` should contain one or more lines defining [process
+1 -1
View File
@@ -1,6 +1,6 @@
# Dokku Core Storage Plugin # Dokku Core Storage Plugin
> New as of 0.5.0 > not yet released and only available in master
The preferred method to mount external containers to a dokku managed container, is to use the dokku storage plugin. The preferred method to mount external containers to a dokku managed container, is to use the dokku storage plugin.
+1 -1
View File
@@ -10,7 +10,7 @@ nginx:error-logs <app> [-t]
## Customizing the nginx configuration ## Customizing the nginx configuration
> New as of 0.5.0 > not yet released and only available in master
Dokku uses a templating library by the name of [sigil](https://github.com/gliderlabs/sigil) to generate nginx configuration for each app. If you'd like to provide a custom template for your application, there are a couple options: Dokku uses a templating library by the name of [sigil](https://github.com/gliderlabs/sigil) to generate nginx configuration for each app. If you'd like to provide a custom template for your application, there are a couple options:
+1 -1
View File
@@ -1,6 +1,6 @@
# Proxy plugin # Proxy plugin
> New as of 0.5.0 > not yet released and only available in master
As of dokku 0.5.0, the proxy functionality has been decoupled from the nginx-vhosts plugin into the proxy plugin. In the future this will allow other proxy software (HAproxy for example) to be used instead of nginx. As of dokku 0.5.0, the proxy functionality has been decoupled from the nginx-vhosts plugin into the proxy plugin. In the future this will allow other proxy software (HAproxy for example) to be used instead of nginx.
+2
View File
@@ -252,6 +252,8 @@
Array.prototype.forEach.call(blockquotes, function (el, i) { Array.prototype.forEach.call(blockquotes, function (el, i) {
if (el.innerHTML.indexOf('New as of') !== -1) { if (el.innerHTML.indexOf('New as of') !== -1) {
addClass(el, 'new-as-of'); addClass(el, 'new-as-of');
} else if (el.innerHTML.indexOf('not yet released') !== -1) {
addClass(el, 'not-yet-released');
} }
}); });
Array.prototype.forEach.call(classNames, function (className, i) { Array.prototype.forEach.call(classNames, function (className, i) {