4awpawz / trio Goto Github PK

browser-sync

Mainly for CSS vendor prefixes.
Idea: Trio calls require for some vendor prefix library & its configuration from user project and calls it with found config if require succeeds.

the callback could insert additional links needing to be prefixed.

Allow user to add appendToTarget: true to include front-matter

would make filtering/finding in lists easier

.catch(() => { });

use curl or search for an npm module that implements the github clone api or write to the github clone api directly

const mainSassFile = glob.sync("source/sass/{*.scss, *.sass}",

should be:

const mainSassFile = glob.sync("source/sass/{*.scss,*.sass}", 

Removing the space between *.scss, and *.sass fixes the problem.

{$, frag, siteMetadata, cheerio} -> {$, [page|include], site, cheerio}
$: cheerio wrapper for either a page or an include
page|include: page or include front matter
site: site front matter
cheerio: a cheerio constructor function

trio_template
trio_appendToTarget
trio_title
trio_callback
trio_tag
trio_category
trio_id
trio_path
trio_destPath
trio_url
...

Use marked

All you graphic artist types, please help Help HELP :)

Contribute to the Trio project.

Your contribution will be greatly appreciated and you will receive attribution too :)

Let's talk.

https://www.wordstream.com/meta-tags
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta

eliminating redundant reads will provide improved performance

See what Visual Studio Code is using when formatting HTML and possibly use that.

Trio should always generate its trio.manifest.json file.

fragment "blogging.md" generates the following:
public/blogging.html

should generate the following:
public/blogging/index.html

Minimalist

sass plugin or post css compiler

npm module to push to gitthub pages

Current Behavior:
The cli is buggy because it isn't thoroughly validating that option are entered correctly and are paired with commands correctly. Also, when printing to the console more spacing should be applied to make it easier to read.

Expected Behavior:

• Options must be validated for:
  • correct use of single and double dashes
  • they are actually supported
  • they are paired correctly with commands
• Spacing is applied to make reading console output easier

add attribute "autocomplete=off" to the checkbox to implement this

node-sass v4.9.2 has security warnings for hoek dependency. They are working on an update to address the issue.

sass/

• main.sass
  • bootstrap/ <====
    • bootstrap.sass <====

The above should generate the following in public/css/:

• csss/
  • main.css
    • bootstrap/ <===
      • bootstrap.css <===

Current behavior is to abort the process when a fragment is missing either its title or template properties.

New behavior should just discard the offending fragment from the build process and log a warning message to the console.

chokidar

Pretty links allow urls like http://treo/somename where the source page "somename.html" gets saved as index.html in a parent folder named somename:

somename
|__ index.html

"buildType": ["development"|"release"]

callbacks -> _callbacks
css -> _css
fragments -> _fragments
includes -> _includes
pages (will be renamed to templates - see #6) -> _templates
sass -> _sass
?scripts -> _scripts?