Beautiful Website for Your Projects
Table of Contents
- Features
- Getting Started
- 1. Install docula
- 2. Add your content
- 3. Build your site
- Using Your own Template
- Building Multiple Pages
- Helper Functions for Markdown
- Code of Conduct and Contributing
- License
Features
- No configuration requrired. Just setup the folder structure with a logo, favicon, and css file.
- Builds a static website that can be hosted anywhere.
- For more complex projects easily add a
docula.config.js
ordocula.config.ts
file to customize the build process. With PRE and POST methods. - Support for single page with readme or multiple markdown pages in a docs folder.
- Will generate a sitemap.xml and robots.txt for your site.
- Uses Github release notes to generate a changelog / releases page.
- Uses Github to show contributors and link to their profiles.
- Simple search is provided by default out of the box.
Getting Started
1. Install docula
npx docula init
This will create a folder called site with the following structure:
site
├───site.css
├───logo.png
├───favicon.ico
├───README.md
├───docula.config.js
Note: for typescript do 'docula init --typescript'
2. Add your content
Simply replace the logo, favicon, and css file with your own. The readme is your root project readme and you just need to at build time move it over to the site folder. If you have it at the root of the project and this is a folder inside just delete the README.md file in the site folder and docula will copy it over for you automatically.
3. Build your site
npx docula
This will build your site and place it in the dist
folder. You can then host it anywhere you like.
Using Your own Template
If you want to use your own template you can do so by adding a docula.config.ts
file to the root of your project. This file will be used to configure the build process.
or at the command line:
npx docula --template path/to/template
Building Multiple Pages
If you want to build multiple pages you can easily do that by adding in a docs
folder to the root of the site folder. Inside of that folder you can add as many pages as you like. Each page will be a markdown file and it will generate a table of contents for you. Here is an example of what it looks like:
site
├───site.css
├───logo.png
├───favicon.ico
├───docula.config.ts
├───docs
│ ├───getting-started.md
│ ├───contributing.md
│ ├───license.md
│ ├───code-of-conduct.md
The readme.md
file will be the root page and the rest will be added to the table of contents. If you want to control the title or order of the pages you can do so by setting the title
and order
properties in the front matter of the markdown file. Here is an example:
---
title: Getting Started
order: 2
---
Helper Functions for Markdown
docula comes with some helper functions that you can use in your markdown files.
doculaHelpers.getFrontMatter(fileName)
- Gets the front matter of a markdown file.doculaHelpers.setFrontMatter(fileName, frontMatter)
- Sets the front matter of a markdown file.doculaHelpers.createDoc(source, destination, frontMatter?, contentFn[]?)
- Creates a markdown file with the specified front matter and content. The contentFn is a function that is executed on the original content of the file. This is useful if you want to remove content from the original file.
Remove html content
In some cases your markdown file will have html content in it such as the logo of your project or a badge. You can use the doculaHelpers.removeHtmlContent()
helper function to remove that content from the page. Here is an example:
Get and Set the Front Matter of a Markdown File
You can use the doculaHelpers.getFrontMatter()
and doculaHelpers.setFrontMatter()
helper functions to get and set the front matter of a markdown file. Here is an example:
const frontMatter = doculaHelpers.getFrontMatter('../readme.md');
frontMatter.title = 'My Title';
doculaHelpers.setFrontMatter('../readme.md', frontMatter);
Code of Conduct and Contributing
Code of Conduct and Contributing guidelines.
License
MIT © Jared Wray
Latest's Releases
What's Changed
- moving to function calls with js-yaml by @jaredwray in https://github.com/jaredwray/docula/pull/183
- upgrading webpack and typescript to lastest by @jaredwray in https://github.com/jaredwray/docula/pull/184
- upgrading vitest to 2.1.1 by @jaredwray in https://github.com/jaredwray/docula/pull/185
- ESM and CJS support by @jaredwray in https://github.com/jaredwray/docula/pull/186
- updating update-notifier to 7.3.1 by @jaredwray in https://github.com/jaredwray/docula/pull/187
- upgrading axios to 1.7.7 by @jaredwray in https://github.com/jaredwray/docula/pull/188
- upgrading express to 4.21.0 by @jaredwray in https://github.com/jaredwray/docula/pull/189
- upgrading ecto to 4.0.0 by @jaredwray in https://github.com/jaredwray/docula/pull/190
- upgrading keyv to 5.0.1 by @jaredwray in https://github.com/jaredwray/docula/pull/191
Full Changelog: https://github.com/jaredwray/docula/compare/v.0.9.0...v0.9.1
What's Changed
- updating @types/node to latest by @jaredwray in https://github.com/jaredwray/docula/pull/179
- upgrading @types/node to 22.4.1 by @jaredwray in https://github.com/jaredwray/docula/pull/180
- updating to use github corners as more modern by @jaredwray in https://github.com/jaredwray/docula/pull/181
Full Changelog: https://github.com/jaredwray/docula/compare/v0.8.0...v.0.9.0
What's Changed
- feat: table of content by @cialese in https://github.com/jaredwray/docula/pull/173
- Supporting Nodejs 20 and 22 while removing Support for 18 by @jaredwray in https://github.com/jaredwray/docula/pull/174
- upgrading rimraf to 6.0.1 by @jaredwray in https://github.com/jaredwray/docula/pull/175
- upgrading axios to 1.7.4 by @jaredwray in https://github.com/jaredwray/docula/pull/176
- fixing dist for site and updating docula serve console message by @jaredwray in https://github.com/jaredwray/docula/pull/177
- adding in workflow_dispatch by @jaredwray in https://github.com/jaredwray/docula/pull/178
Full Changelog: https://github.com/jaredwray/docula/compare/v0.7.2...v0.8.0