skiano / pinto

Minimal build and dev for really tiny HTML projects

pinto

what is it?

A minimal and zero-configuration tool for developing super tiny HTML projects, such as:

• quick experiments and prototypes — it’s easy to build and deploy
• student projects — the environment is almost non-existent
• super small sites — single page portfolio etc
• project documentation — by using pinto on your gh-pages branch

how do I use it?

$ npm install pinto -g # install the cli

$ pinto init src        # scaffolds the project in src/ folder
$ pinto dev src         # starts a dev src/
$ pinto build src dist  # builds a static page in dist
$ pinto preview dist    # previews the static page in dist

what it does?

Pinto creates a completely static html page from the following:

• A single CSS file
• A single JS file
• A handlebars template
• A JSON file that powers the handlebars template
• An assets folder for public images or whatever

pinto's Issues

Include optional support for live reload

Personally, I'm not bothered by not having live reload, but I think people would like it. So I think it should be considered as an optional feature.

Data example missing from stub template

the logic for the template creation is busted, so there is no example of dynamic data created.

Render clearer errors in browser

When something fails in dev, the raw error is stringified and sent to the browser. However, depending on the error, there may be a more helpful message possible. For example, the postcss errors are more elaborate than standard errors. Maybe look for what library is powering popular tools like vue cli's or angular cli's error display.

Document use with .jsx

Using jsx would be nice

Better integration with now

Public or static folder for some assets

Do not overrite existing project files

It would be very sad indeed

Expose postcss config for user to manipulate

It seems easy to do, and almost inevitable that people would ask for it.

Flatten data and reserve `js` and `css` keys

Having to key into data is not very intuitive

add support for object spread

buble needs an extra option to support spreading

Expose buble config options

Allow user to modify buble config. This would be especially useful if they want jsx with something like hyperapp

Allow pinto init to create folder

Right now pinto init scaffolds in cwd. Would be nice if it could accept a path and create the folder too. Might make onboarding a little nicer.

Add tests

Would be nice to have test coverage for some parts of this. But i think it is simple enough I'm not too worried yet.