The common approach to both solutions is that a JavaScript is run in the browser that matches HTML elements and alters them to be hidden. Therefore all elements are rendered as normal and then are hidden by the script. Content Marker |
---|
|
Content Marker |
---|
id | screenshots-bookmarklet |
---|
|
Section |
---|
Column |
---|
|
Panel |
---|
title | Space Blueprint Wizard with projectdoc Blueprints |
---|
| Image Modified |
|
Column |
---|
|
Panel |
---|
title | Space Blueprint Wizard without projectdoc Blueprints |
---|
| Image Modified |
|
|
Section |
---|
Column |
---|
|
Panel |
---|
title | Page Blueprint Wizard with projectdoc Blueprints |
---|
| Image Modified |
|
Column |
---|
|
Panel |
---|
title | Page Blueprint Wizard without projectdoc Blueprints |
---|
| Image Modified |
|
|
Section |
---|
Column |
---|
|
Panel |
---|
title | Macro Browser with projectdoc Macros |
---|
| Image Modified |
|
Column |
---|
|
Panel |
---|
title | Macro Browser without projectdoc Macros |
---|
| Image Modified |
|
|
|
Section |
---|
Column |
---|
|
Panel |
---|
title | Macro Suggestions with projectdoc Macros |
---|
|
|
|
Panel |
---|
title | Macro Suggestions without projectdoc Macros |
---|
|
Column |
---|
|
|
|
|
|
Note that this use case is not properly supported the bookmarklet. A user will probably not run the bookmarklet manually when using the autocomplete function to select a macro. Note Box |
---|
| The following examples show how to remove all macros or doctypes from the view. In case you need to remove these tools selectively, you would need to adjust the CSS selectors in the scripts. |
|