>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #424400. --> Reported by: [Jeff Burnz](https://www.drupal.org/user/61393) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>In the on going attempt to reduce barriers of entries, we have decided to move impliment an enhanced editor for entering documentation, forum posts and issues in full html markup.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>To use the html editor called <a href="http://drupal.org/project/bueditor">BUEditor</a> in the attempt to further reduce barriers of entry and increase quality and usage of HTML markup. BUEditor was written specifically for Drupal and is managed and written by our very own <a href="http://drupal.org/user/9910">ufku</a>. This GNU Licensed module can be maintained and managed in house while providing some unique benifits over WYSIWYG editors.</p> <p>WYSIWYG Editors have complex code, large code deposits, and need extensive setup and configurations to make them work perfectly. They ultimately attempt to recreate a true WYSIWYG environment like Dreamweaver, while not actually providing full compatibility or true WYSIWYG. </p> <p>BUEditor on the other hand assists individuals in writing HTML. The quick preview allows for less page refreshes and quick review of changes. The light weight nature provides complete security while the client side only javascript keeps AJAX or JQuerry call backs that will increase server load.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li> <p>A completed and tested procedure has been written and must be implemented on Drupal.org. The procedure is as follows:</p> <ol> <li>Install BUEditor in modules directory</li> <li>Enable BUEditor in modules</li> <li>Administer -&gt;Site Configuration-&gt;BUEditor</li> <li> Import "<a href="http://drupal.org/files/HTML.Basic_.bueditor_2.txt">HTML.Basic_.bueditor_2.txt</a>" by filling in Title: "HTML Basic" Directory (leave blank) Editor Code: Paste and copy text file Above. </li> <li>Press Import</li> <li>Check to see if changes to BBCode -&gt; "HTML Basic" where made</li> <li>Goto /admin/settings/bueditor</li> <li> Assign all roles to BBCode for "HTML Basic" and none as alternative.</li> <li> Goto Permissions and set BUEditor Module -&gt; Administrator bueditor (execute PHP) to thoose ADMINS you want to give it to (suggest none?)</li> <li>Install New Icons</li> <ol> <li>cd /files</li> <li>mkdir bueditor-icons</li> <li> cd bueditor-icons</li> <li> wget <a href="https://www.drupal.org/files/ico_bueditor+.zip" title="http://drupal.org/files/ico_bueditor+.zip" rel="nofollow">http://drupal.org/files/ico_bueditor+.zip</a></li> <li> unzip ico_bueditor+.zip</li> <li> Go to admin/settings/bueditor/2, expand "Editor paths", and </li> <li>Change "Directory of editor icons" to "%FILES/bueditor-icons"</li> </ol> <li>Save and PARTY</li> </ol> </li> <li> <p>(optional and possibly post-deployment) <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/webmasters/issues/1302972" title="Status: Closed (won't fix)">#1302972: Decide on a specific set of libraries, extensions, and icons for BUEditor as used on drupal.org</a></span></p> </li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>The user interface changes will not distract fluent HTML users, while provide helper functions to thoose early entry point consumers. The optional BUEditor user interface provides an additional tool bar above the text box. This rather unobtrusive bar provides unique help for individuals who are not as fluent in HTML, or assistance to thoose looking to include more complex HTML like lists, strong, headers, etc.</p> <p><img src="https://www.drupal.org/files/BUEditor%20Screan%20Shot.png"></p> <h3>Sandbox Testing Info</h3> <p>Path: <a href="http://bueditor-drupal.redesign.devdrupal.org/">http://bueditor-drupal.redesign.devdrupal.org/</a><br><br> Username/Password Window: drupal/drupal<br> Username/Password Drupal: bananas/bananas for basic user, jn2/jn2 for documentation team member</p> <h3 id="summary-api-changes">API changes</h3> <p>The lightweight BUEditor requires nor adds no new API changes.</p> <h3 id="summary-original-report">Original report by <a href="http://drupal.org/user/61393" title="View user profile.">Jeff Burnz</a></h3> <p>n the vein of "reducing barriers" and making it easier, I would like the option to use Markdown.</p> <p>Heres a simple example of how Markdown can improve and make it easier to markup doc book nodes - the footnote.</p> <p>Footnotes and references are sorely missing from many book pages. Yes we often provide contextual inline links to relevant sources, articles and other Drupal nodes but as a "book" and a "wiki" we're not providing an easy method of citing references and adding footnotes.</p> <p>If we want to make a footnote currently we need to do this (or similar)</p> <pre>This is some text&lt;sup&gt;&lt;a href="#123" id="fn1"&gt;1&lt;/a&gt;&lt;/sup&gt;<br>&lt;!-- Notes --&gt;<br>&lt;ul id="footnotes"&gt;<br> &lt;li id="123"&gt;This is a footnote &lt;a href="#fn1"&gt;&amp;#8593;&lt;/a&gt;&lt;/li&gt;<br>&lt;/ul&gt;</pre><p>Markdown equivalent:</p> <pre>This is some text[^1]<br>&lt;!-- Notes --&gt;<br>[^1]: footnote 1</pre><p>If we could use Markdown and even the BU Editor with Markdown (perhaps even with Preview?) I think it would make it faster, easier and more in line with other Wikis.</p> <p>Of course, footnotes are just one example so please don't get hung up on footnotes, its about reducing barriers and making it faster/smarter/easier. For me speed is a big driver, I only have so much time and anything that can make marking up quicker is a win.</p>