[Bf-docboard] Corporate Identity & manual structure

[Tobias Heinke]

Hi,

|> CSS override patches: why they don't break anything

How override works:

     HTML class="id1": color = blue | <- THEME id1: color = --red-- |  
<- OVERRIDE id1: color = blue

If ID is changed:

     HTML class="id2": color = green | <- THEME id2: color = green |  <- 
OVERRIDE id1: color = blue

Override CSS rule points at nothing and get not applied.
(there is the 1% chance that the old class id is used by a new HTML object)

With chance of deactivation by theme/Sphinx changes:
     - Color overwrite".org colors" https://developer.blender.org/D1871
     - Blender Icon before nav title https://developer.blender.org/D1908

Zero chance, because I define the class name ID's:
     - home .org header https://developer.blender.org/D1887
     - section descriptions https://developer.blender.org/D1899

I carefully designed it so, that the fallback works:
Demo "when worse comes to worse" shows RST changes only in theme styling:

https://github.com/tobiasHeinke/demo/blob/master/images/fallback.PNG
(I've deleted some section for the image)
(the margin moves the header - the clear:both issue)

Tobias

Am 24.03.2016 um 22:02 schrieb Tobias Heinke:
> Hello doc team,
>
> |> Blender branding: my recent patch
>
> The aim is to communicate to the user that she's on a Blender side.
> By Corporate Identity / Design. That means logo's and colors.
>
> While colors can be changed by simply overwriting them.
> The challenge is the "injection" of the logo:
>
> The rules are: minimal invasive, CSS only, with fallback.
> A fallback is always available, because the theme gets overwritten and
> not replaced.
>
> The Loge could be added to every existing HTML element by the ::before
> selector
> The image is drawn as a background.
>
> So where to place an logo (thats visible on all pages):
>
> The only place I see is before the "Blender Reference Manual"-header,
> but theres already sits an *ugly home icon.
> Witch only purpose it is to indicate to the user that the header is a
> clickable link.
>
> (home)  (B. logo) "Blender Reference Manual"
>
> Next I converted the header visually to a button and show (home) only on
> hover.
>
> Demo time screenshots:
> https://github.com/tobiasHeinke/demo
>
> I've made 3 button versions:
> 3D, glass plain, light frame
>
> Which one looks best? Or send me an link to an "inspiration" screenshots
> of a button.
>
> |> Manual Structure or There lures a Monster in the Deep!
>
> Diffrent approaches to CG are causing structural weaknesses in the manual:
> While the technical (micro) approach is omnipresent (explain CG over the
> description of what every button does = tooltips)
> The structure defined by technical (macro) colliding with the production
> pipeline structuring.
>
> Technical view micro: interface
> Technical view macro: editors
>
> Editors, Data System (technical)
> Model; Paint. & Sculp; Rig; Anima; Physics (production pipeline)
> Render, Compositing (technical)
>
> The problem arising: stumps (if missing - links to section), duplicates,
> separation.
>
>       Stump: https://www.blender.org/manual/editors/index.html#settings
> [link: Preferences ]
>
>       Dublication: Texturing is in 3 places: editors> UV, 3D paint,
> Rendering > (engine) > texturing
>
>       Separation:
>       object mode:
> https://www.blender.org/manual/editors/3dview/selecting.html
>       edit mode:
> https://www.blender.org/manual/modeling/meshes/selecting/introduction.html
>
> Solution:
> 1. Decide for one way (technical/ production pipeline /...)
> 2. Apply approach where it's strength lay.
> 3. ( ? )
>
> yay no tldr;
>
> Tobias
>
> _______________________________________________
> Bf-docboard mailing list
> Bf-docboard at blender.org
> http://lists.blender.org/mailman/listinfo/bf-docboard

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20160411/14b071af/attachment.htm