Download the PHP package mkocansey/quickiedox without Composer

Overview

QuickieDox is a purely vanilla PHP( >= 7.4) project that allows you to quickly create elegant documentation from markdown files. Visit https://quickiedox.com for the full documentation.

QuickieDox is not software as a service, thus, doesn't host any documentation. You will need to host everything yourself just like you would host any of your websites.

Who Can Use QuickieDox

• To use QuickieDox you must already know how to write markdown syntax and also know some basic PHP. This guide can bring you up to speed on writing markdown.

• Anyone with documentation needs regardless of the size can use QuickieDox

Installation

There are two ways to create your own documentation website using QuickieDox.

Via Composer

This option is the easiest. Simply run the command below.

Clone From GitHub: HTTPS

Clone From GitHub: SSH

Rename .env-example

You will find a .env-example file at the root of the project you just cloned. Rename it to .env. The app will not run if this is not done.

Run the App

Now that you have cloned the repo, let us run the app to ensure you can see the documentation that ships by default. From the root of the directory you just created, run:

Let's start an inbuilt PHP server to quickly test. Still at the root of the project, type

The above ccommand assumes port 8000 is not in use by another site or app. You should see output similar to what is below. The version of PHP might differ depending on what you have installed on your machine.

Navigating to http://localhost:8000 should display the screen below.

Clicking on Read Documentation from the home page as shown in the image above should display the screen below.

You can tell from the above image that QuickieDox is unable to load the documentation navigation or the default documentation pages. This is very much expected since we have not pulled in the markdown files that make up the documentation.

By default QuickieDox expects the markdown files to be in the markdown directory at the root of the project you just created. You can use any directory name of your choice but just make sure you update the config file to tell QuickieDox where to load your .md files from.

Pull In The Markdown Files

The markdown files that make up the documentation are expected to sit in a directory you specify. The default is markdown. The assumption/convention here is that your markdown files are hosted in their own git repo. There are two ways to pull in the markdown files.

Use The Inbuilt Cloning Tool

via HTTP

It is much easier to pull in your markdown files using the cloning URL that is built into QuickieDox. Assuming you are still running the app from the server we started above using php -S localhost:8000, you will need to visit the URL below.

http://localhost:8000/get-markdown

Ensure you have properly modified your QuickieDox configurations. The URL will ask for the PIN you defined in the .env or .config.php file as GIT_CLONE_PIN. You won't be able to use this URL if your PIN is blank.

via The clone.sh File

Cloning via HTTP will work well if you are cloning from public repositories. If you are cloning your documentation from a private repository, using the clone.sh file is a better option.

Included at the root of the project is a clone.sh shell script that pulls in your markdown files from the repo you specify. You will need to edit the file to change the default values defined for GIT_REPO_URL, DOCS_DIRECTORY and DOC_VERSIONS.

Ensure the script has permissions to execute for owner and/or group. Run.

Now run this command to execute the shell script to pull in the documentation.

Copy and Paste

QuickieDox only needs .md files in the markdown directory. You can simple copy and paste your .md files into this directory and voila! If your documentation is in versions, you will need to have a separate directory for every version. For example, if your documentation has versions 1.5 and 2.2, you will need to create 1.5 and 2.2 directories in the markdown directory. You will then need to copy the appropriate .md files into their respective directories. See the Conventions > Versioning docs for more on this.

Further Reading

Visit https://quickiedox.com for the full documentation but these should help you better understand how QuickieDox works.

• Directory Structure
• The Configuration File
• The Navigation File
• Versioning Your ocumentation
• Customizing The Homepage
• How QuickieDox Works
• Deploying Your Docs

Known Issues

• Integration of Algolia
• Faster site-wide search
• Protecting docs that require signiing in before reading
• Top level navigation items can only be parents and not links to pages

Support

You can tweet @quickiedox or email [email protected] if you have any questions.