<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>doc.mashweb.club – structure</title>
    <link>/tags/structure/</link>
    <description>Recent content in structure on doc.mashweb.club</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Thu, 05 Jan 2017 00:00:00 +0000</lastBuildDate>
    
	  <atom:link href="/tags/structure/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Zen-White-Paper: Critique of current WYSIWYM web-page composers</title>
      <link>/zen-white-paper/wysiwym/</link>
      <pubDate>Thu, 05 Jan 2017 00:00:00 +0000</pubDate>
      
      <guid>/zen-white-paper/wysiwym/</guid>
      <description>
        
        
        &lt;p&gt;WYMeditor is the best-known WYSIWYM web page editor. &lt;em&gt;WYSIWYM&lt;/em&gt; stands for &lt;em&gt;What You See Is What You Mean&lt;/em&gt;. In a WYSIWYM editor, the user creates a document with &lt;em&gt;structured, meaningful content&lt;/em&gt;. The &lt;em&gt;presentation&lt;/em&gt; of the content is out of his hands. The separation of &lt;em&gt;content&lt;/em&gt; from its &lt;em&gt;look and feel&lt;/em&gt; makes it possible to view the document in many ways on many devices, which is a central principle of good web design.

&lt;figure&gt;
    &lt;img src=&#34;/images/WYMeditor.png&#34;/&gt; &lt;figcaption&gt;
            &lt;h4&gt;WYMeditor&lt;/h4&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;The WYSIWYM principle undoubtedly is suitable for web design, but WYMeditor has serious drawbacks. It was tricky to set up in the author&amp;rsquo;s own experience. A web page cannot embed it. According to an old Wikipedia article on WYMeditor (now archived on Archive.org),&lt;a href=&#34;/zen-white-paper/notes/#fn:27&#34;&gt;&lt;sup&gt;27&lt;/sup&gt;&lt;/a&gt;
 &amp;ldquo;One downside of WYMeditor is that it cannot be used to include JavaScript in the content it edits. Changing this would require eliminating WYMeditor&amp;rsquo;s use of the &lt;code&gt;innerHtml&lt;/code&gt; property.&amp;rdquo; Thus, WYMeditor won&amp;rsquo;t work with reactive widgets.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The author might expand this section to cover a representative set of WYSIWYM composers.&lt;/em&gt;&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Zen-White-Paper: Values</title>
      <link>/zen-white-paper/values/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/zen-white-paper/values/</guid>
      <description>
        
        
        &lt;p&gt;The values driving Zen&amp;rsquo;s development are:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Creating novel, beautiful, well-formatted, semantic HTML and CSS should be dead simple.&lt;/li&gt;
&lt;li&gt;Amateur web authors should easily create virtually any page structure and style.&lt;/li&gt;
&lt;li&gt;The interface should have a virtually zero learning curve, and zero should mean zero. Zen must leverage well-known interface metaphors and gestures to the hilt. The &amp;ldquo;principle of least surprise&amp;rdquo; should be followed.&lt;/li&gt;
&lt;li&gt;Zen should not clutter its interface for manipulating and creating semantic and presentation structure with every possible detail. Zen should hide details until they are needed; it is better to let the user drill down to these details than to present them by default.&lt;/li&gt;
&lt;li&gt;The interface should have two mutually exclusive modes for semantics and styling. The semantics mode should hide page styling information and help search engines &amp;ldquo;understand&amp;rdquo; the page&amp;rsquo;s subject matter to classify it for the sake of web seekers. Styles will set fonts and colors and the interaction of the page&amp;rsquo;s elements with other elements and with the height and width of the page.&lt;/li&gt;
&lt;li&gt;The interface should have two mutually exclusive modes: a semantics mode and a styling mode. The semantics mode should hide page styling information. The styles will set the looks of the page and the interaction of the page&amp;rsquo;s elements with such things as other elements and the height and width of the page. each other and the The clear and proper semantic structure will help search engines &amp;ldquo;understand&amp;rdquo; the page&amp;rsquo;s subject matter to classify it. The other mode should hide the semantics and focus on the look and feel of the web page. The look and feel is&lt;/li&gt;
&lt;li&gt;Meta organization, like themes, templates, or partials,&lt;a href=&#34;/zen-white-paper/notes/#fn:28&#34;&gt;&lt;sup&gt;28&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:29&#34;&gt;&lt;sup&gt;29&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:30&#34;&gt;&lt;sup&gt;30&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:31&#34;&gt;&lt;sup&gt;31&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:32&#34;&gt;&lt;sup&gt;32&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:33&#34;&gt;&lt;sup&gt;33&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:34&#34;&gt;&lt;sup&gt;34&lt;/sup&gt;&lt;/a&gt;
 should not be precluded by the structure of Zen&amp;rsquo;s low-level tools. Zen should empower the creation of these, even if not directly implement them.&lt;/li&gt;
&lt;/ol&gt;

      </description>
    </item>
    
  </channel>
</rss>
