npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ideamark

v0.3.0

Published

A simple nodejs document store for ideas, concepts, documentation supporting markdown

Downloads

18

Readme

ideamark

ideamark is an online container for your ideas, concepts and documentations based on this-blog a simple blogging engine by Dusko Jordanovski written in node.js. All documents are written with Markdown markup.

Features

  • Simple publishing mechanism - use a single command
  • No database - all data is kept in files
  • Blog posts are single files and contain their own configuration
  • Can handle multiple languages
  • Can tag posts and dynamically build tag categories
  • Posts can have their own templates or use the provided master
  • File watcher to live-update pages

Installation

To use it, you will have to make 2 installations, one on your server and one on your local machine:

npm install ideamark

Usage

Setting up

Before you start it, you need to edit the settings.json file in the root directory. Your local and remote installation must have the same settings for these options:

remoteUrl:    "example.com"
remotePort:   80
password:     "icanhazcheezburger"
contentDirs:  ["posts", "templates", "static"]

You need to get these to be the same on your server and local installation. Everything else is configurable later. The remoteUrl and remotePort are the public URL and port of your blog. The password is used to authenticate you when you publish posts.

You can start your server by running

node blog.js -s 

on your server.

Publishing

To upload posts, images and templates start adding them in one of the contentDirs that you defined. Normally your posts would go in the posts directory, templates in the templates directory, but *ideamark uses only the file extension to make difference between posts and other files. Any file with the .md extension will be treated like a post.

After you're done publish your changes by running

node blog.js -p 

on your local machine.

Configuration

Here's an overview of the configuration options in the settings.json file:

port:        The port for the node server to listen to (if you use a proxy)
remotePort:  The public port for your blog (should be 80)
remoteUrl:   The public URL of your blog
password:    Authentication password - needs to be the same
contentDirs: Dirs scanned for content changes before publishing
gaCode:      Google analytics key
postsUrl:    Url path for posts (with leading slash)
tagsUrl:     Url path for tags (with leading slash)
adminUrl:    Url path for publishing (passworded, with leading slash)
errorLog:    Error log filename 
watchFiles:  Activates the file watcher to live-update your instance
useCaching:  Activates caching for files (will be deactivated if `watchFiles` is set to `true`)
maxExcerpts: Maximum number of posts shown on a tag/home page
pagination:  Maximum number of pagination links
languages:   List of languages - ["en", "mk"]
langinfo:    Hash of language names - {"en": "English", "mk": "Македонски"}
sitemenus:   List of menus that posts can appear in - ["bookmarks", "2011"]
strings:     A hash of stranslation strings for each language

Appart from the settings.json file, you can also configure your posts individually by using headers. A post filename should look like this:

This is my first post.en.md

It has to have the md extension for it to be treated like a post. The ".en" part tells This Blog the language of the post. If it's ommitted, the first language in your languages settings will be used. To have the same post on another language, just do this:

This is my first post.en.md  # English Version
This is my first post.de.md  # German Version

Posts are further configured by using headers. All posts must start with a set of HTTP-like headers. Headers must be the first thing in the post file and are over when the first instance of 2 consecutive newlines is found

Here's an example post file:

Language:     en                    # This is found in the filename 
Title:        My First Post         # This appears as the title (<h1>)
Date:         2011-12-19            # Must be a date in the ISO format
Description:  Nothing special       # META description
Menus:        Bookmarks             # One of the menus in which it appears
Tags:         Blog, Node.js         # Post tags

Notice the 2 new lines. This is the beginning of the post. We ommit the
title because it will be automatically added for us from the headers.

This part is the post excerpt. Notice the 5 dashes in-between double 
linebreaks (\n\n-----\n\n). That's the excerpt delimiter. Everything before
those dashes will appear in the list on the homepage/tag pages. If you
ommit those dashes, the whole post will appear on the homepage along with
other posts.

-----

This is the continuation of the post. This will be visible only on the
post page.

License

ideamark is lincensed under the MIT license.

TODOS

  • Add an option to exclude a post from being listed on the homepage.
  • Support .markdown file extension
  • Templating for list of posts