www.freebsd.org

2014-08-13 Thread Julie



Hi,

If you want your website to work harder, WE can help you measure your
performances, identify areas of weakness, and clear a path to better
conversion rates. There's no single reason why visitors to your website
fail to become customers. The need is to attract visitor's attention that
helps in better interaction. Optimisation does not mean changing the
existing layout of your website but these are tools for better visitor
engagements.

Every non-converting visitor costs you in wasted market-ing efforts and
missed sale.

Would you be interested in receiving further information & a quote for
optimising your website with no-strings-attached?
 Best regards,
Julie
Conversion Optimisation Specialist

*D*OMOTICS Western Australia, Northern Territory, South Australia,
Queensland, New South Wales, Victoria, Australian Capital Territory,
Tasmania

Disclaimer: We respect your privacy and want to make sure you are aware of
a few things. By replying to this email, you authorise our affiliates that
can help with your project to contact you at the number you provided, and
you understand that they may use automated technology to reach you. At no
time are you required to make a purchase.

___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"


/etc/motd update

2014-08-13 Thread Warren Block
The existing /etc/motd breaks many of our document rules and has some 
weird language constructs.  The current version in HEAD:

http://svnweb.freebsd.org/base/head/etc/motd?view=co

Here is a rewrite.  URLs are now the only thing on a line, instead of 
inline and hard to locate.  No contractions are used.  Odd phrases are 
rephrased:


Here is the proposed new version and a diff:
http://www.wonkity.com/~wblock/motd/motd
http://www.wonkity.com/~wblock/motd/motd.diff

Making it clear that commands are to be typed without quotes is a little 
difficult.  This file is plain text, so no out-of-band highlighting is 
available.  ANSI colors or bold could be used, but the terminal is not 
guaranteed to be able to display them.  The only really clear way would 
be to put commands on a separate line, indented.  That takes up more 
space, maybe not a big deal.


The other issue is whether we should mention the search box on the web 
page, which is not very effective at finding things.


Comments and suggestions welcome.
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"


Re: /etc/motd update

2014-08-13 Thread Brooks Davis
On Wed, Aug 13, 2014 at 02:23:00PM -0600, Warren Block wrote:
> The existing /etc/motd breaks many of our document rules and has some 
> weird language constructs.  The current version in HEAD:
> http://svnweb.freebsd.org/base/head/etc/motd?view=co
> 
> Here is a rewrite.  URLs are now the only thing on a line, instead of 
> inline and hard to locate.  No contractions are used.  Odd phrases are 
> rephrased:
> 
> Here is the proposed new version and a diff:
> http://www.wonkity.com/~wblock/motd/motd
> http://www.wonkity.com/~wblock/motd/motd.diff

> Making it clear that commands are to be typed without quotes is a little 
> difficult.  This file is plain text, so no out-of-band highlighting is 
> available.  ANSI colors or bold could be used, but the terminal is not 
> guaranteed to be able to display them.  The only really clear way would 
> be to put commands on a separate line, indented.  That takes up more 
> space, maybe not a big deal.
> 
> The other issue is whether we should mention the search box on the web 
> page, which is not very effective at finding things.
> 
> Comments and suggestions welcome.

My first thought was that it's definitely better, but too long since 25
rows of text won't fit on the default console.

My second thought was that a better approach might be to replace most of
the contents with a URL like:

http://freebsd.org/getting-started-with-freebsd-11

and a reference to a local copy of the content a release time.  That
would allow unlimited formatting, let us target different user
audiences, and let us improve the online version over time.

-- Brooks


pgpPfqQXQm1VI.pgp
Description: PGP signature


Re: /etc/motd update

2014-08-13 Thread Warren Block

On Wed, 13 Aug 2014, Brooks Davis wrote:


On Wed, Aug 13, 2014 at 02:23:00PM -0600, Warren Block wrote:

The existing /etc/motd breaks many of our document rules and has some
weird language constructs.  The current version in HEAD:
http://svnweb.freebsd.org/base/head/etc/motd?view=co

Here is a rewrite.  URLs are now the only thing on a line, instead of
inline and hard to locate.  No contractions are used.  Odd phrases are
rephrased:

Here is the proposed new version and a diff:
http://www.wonkity.com/~wblock/motd/motd
http://www.wonkity.com/~wblock/motd/motd.diff



Making it clear that commands are to be typed without quotes is a little
difficult.  This file is plain text, so no out-of-band highlighting is
available.  ANSI colors or bold could be used, but the terminal is not
guaranteed to be able to display them.  The only really clear way would
be to put commands on a separate line, indented.  That takes up more
space, maybe not a big deal.

The other issue is whether we should mention the search box on the web
page, which is not very effective at finding things.

Comments and suggestions welcome.


My first thought was that it's definitely better, but too long since 25
rows of text won't fit on the default console.

My second thought was that a better approach might be to replace most of
the contents with a URL like:

http://freebsd.org/getting-started-with-freebsd-11

and a reference to a local copy of the content a release time.  That
would allow unlimited formatting, let us target different user
audiences, and let us improve the online version over time.


That would allow much more vertical space in the actual "intro" file, 
and clearer explanations:


Type
  man man
for an introduction to manual pages.

Where should the intro file be stored?  /usr/doc is not always present.
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"