mirror of
https://github.com/fleetdm/fleet
synced 2026-05-03 03:17:21 +00:00
* minor clarifications
* further expand comments and stubs
* absorb custom titles embedded in metadata, plus further comment expansion and a followup fix for something i left hanging in f8cbc14829
* Skip non-markdown files and use real path maths
* Prep for running in parallel (Remove `continue` so this isn't dependent on the `for` loop)
* determine + track unique HTML output paths
* Compile markdown + spit out real HTML (without involving any but the crunchy nougaty dependency from the very center of everything)
* add md metadata parsing
* add timestamp
* Update build-static-content.js
* attach misc metadata as "other"
* how doc images might should work (this also aligns with how the select few images in the sailsjs.com docs work)
* add file extension to generated HTML files
* "options"=>"meta"
* Make "htmlId" useful for alphabetically sorting pages within their bottom-level section
See recent comments on https://github.com/fleetdm/fleet/issues/706 for more information.
* list out the most important, specific build-time transformations
* Omit ordering prefixes like "1-" from expected content page URLs
* add a little zone for consolidating backwards compatible permalinks
* interpret README.md files by mapping their URLs to match their containing folder
* clarify plan for images
* decrease probability of collisions
* Make capitalization smarter using known acronyms, proper nouns, and a smarter numeric word trim
* Resolve app path in case pwd is different in prod
* Delete HTML output from previous runs, if any
* condense the stuff about github emojis
* got rid of "permalink" thing, since id gets automatically attached during markdown compilation anyway
Also "permalink" isn't even a good name for what this is. See https://github.com/fleetdm/fleet/issues/706#issuecomment-884693931
* …and that eliminates the need for the cheerio dep!
* Bring in bubbles+syntax highlighting into build script, and remove sails.helpers.compileMarkdownContent() -- this leaves link munging as a todo though
* trivial (condense comments)
* Remove unused code from toHtml() helper
* Implemented target="_blank" and root-relative-ification
* remove todo about emojis after testing and verifying it works just fine
* trivial: add link to comment in case github emojis matter at some point
* consolidate "what ifs" in comments
* Leave this up to Sarah, for now. (Either bring it back here in the build script or do it all on the frontend)
* Enable /docs and /handbook routes, and add example of a redirect for a legacy/deprecated URL
* implement routing
* Upgrade deps
this takes advantages of the latest work from @eashaw, @rachaelshaw, and the rest of the Sails community
* tweak var names and comments
* make readme pages use their folder names to determine their default (fallback) titles
as discussed in https://github.com/fleetdm/fleet/issues/706#issuecomment-884788002
* first (good enough for now) pass at link rewriting
as discussed in https://github.com/fleetdm/fleet/issues/706#issuecomment-884742072
* Adapt docs pages to build from markdown output
* Continue work on docs pages
* Add landing page
* Remove unused code; minor changes
* Replace regex
* fixes https://github.com/fleetdm/fleet/pull/1380#issuecomment-891429581
* Don't rely on "path" being a global var
* Syle fleetdm doc pages
* Continue work on docs pages
* Fix linting error
* Disable lesshint style warnings
* parasails-has-no-page-script attribute
Added a parasails-has-no-page-script attribute to the docs template, added a check for that attribute in parasails.js and removed the empty page script for 498
* bring in latest parasails dep
* trivial
* Update links to dedupe and not open in new tab unless actually external
* Disable handbook for now til styles are ready
* fix CTA links
* trivial
* make sitemap.xml get served in prod
* hide search boxes for now, remove hard-coded version and make releases open in new tab
* clean out unused files
Co-authored-by: gillespi314 <[email protected]>
Co-authored-by: eashaw <[email protected]>
110 lines
3.3 KiB
JavaScript
Vendored
110 lines
3.3 KiB
JavaScript
Vendored
module.exports = {
|
|
|
|
|
|
friendlyName: 'To HTML',
|
|
|
|
|
|
description: 'Compile a Markdown string into an HTML string.',
|
|
|
|
|
|
extendedDescription:
|
|
'Expects GitHub-flavored Markdown syntax. Uses [`marked`](https://github.com/chjj/marked)@v0.3.5. '+
|
|
'Inspired by https://github.com/mikermcneil/machinepack-markdown/tree/5d8cee127e8ce45c702ec9bbb2b4f9bc4b7fafac',
|
|
|
|
|
|
moreInfoUrl: 'https://help.github.com/articles/basic-writing-and-formatting-syntax/',
|
|
|
|
|
|
sideEffects: 'cacheable',
|
|
|
|
|
|
inputs: {
|
|
|
|
mdString: {
|
|
description: 'Markdown string to convert',
|
|
example: '# hello world\n it\'s me, some markdown string \n\n ```js\n//but maybe i have code snippets too...\n```',
|
|
required: true
|
|
},
|
|
|
|
allowHtml: {
|
|
friendlyName: 'Allow HTML?',
|
|
description: 'Whether or not to allow HTML tags in the Markdown input. Defaults to `true`.',
|
|
extendedDescription: 'If `false`, any input that contains HTML tags will trigger the `unsafeMarkdown` exit.',
|
|
example: true,
|
|
defaultsTo: true
|
|
},
|
|
|
|
addIdsToHeadings: {
|
|
friendlyName: 'Add IDs to headings?',
|
|
description: 'Whether or not to add an ID attribute to rendered heading tags like <h1>',
|
|
extendedDescription: 'This is not part of the Markdown specification (see http://daringfireball.net/projects/markdown/dingus), but it is the default behavior for the `marked` module. Defaults to `true`.',
|
|
example: true,
|
|
defaultsTo: true
|
|
}
|
|
|
|
},
|
|
|
|
|
|
exits: {
|
|
|
|
success: {
|
|
outputFriendlyName: 'HTML',
|
|
outputExample: '<h1 id="hello-world">hello world</h1>\n<p> it's me, some markdown string </p>\n<pre><code class="lang-js">//but maybe i have code snippets too...</code></pre>\n'
|
|
},
|
|
|
|
unsafeMarkdown: {
|
|
friendlyName: 'Unsafe Markdown detected',
|
|
description: 'The provided input contained unsafe content (like HTML tags).'
|
|
}
|
|
|
|
},
|
|
|
|
|
|
fn: function(inputs, exits) {
|
|
var marked = require('marked');
|
|
|
|
// For full list of options, see:
|
|
// • https://github.com/chjj/marked
|
|
var markedOpts = {
|
|
gfm: true,
|
|
tables: true,
|
|
breaks: false,
|
|
pedantic: false,
|
|
smartLists: true,
|
|
smartypants: false,
|
|
};
|
|
|
|
if (inputs.addIdsToHeadings === false) {
|
|
var renderer = new marked.Renderer();
|
|
renderer.heading = function (text, level) {
|
|
return '<h'+level+'>'+text+'</h'+level+'>';
|
|
};
|
|
markedOpts.renderer = renderer;
|
|
}
|
|
|
|
// Now actually compile the markdown to HTML.
|
|
marked(inputs.mdString, markedOpts, function afterwards (err, htmlString) {
|
|
if (err) { return exits.error(err); }
|
|
|
|
// If we're not allowing HTML, compile the input again with the `sanitize` option on.
|
|
if (inputs.allowHtml === false) {
|
|
markedOpts.sanitize = true;
|
|
marked(inputs.mdString, markedOpts, function sanitized (err, sanitizedHtmlString) {
|
|
if (err) { return exits.error(err); }
|
|
|
|
// Now compare the unsanitized and the sanitized output, and if they're not the same,
|
|
// leave through the `unsafeMarkdown` exit since it means that HTML tags were detected.
|
|
if (htmlString !== sanitizedHtmlString) {
|
|
return exits.unsafeMarkdown();
|
|
}
|
|
return exits.success(htmlString);
|
|
});
|
|
}
|
|
else {
|
|
return exits.success(htmlString);
|
|
}
|
|
});
|
|
}
|
|
|
|
|
|
};
|