A PHP tool that helps you write eBooks in markdown and convert to PDF.

Thanks your this package, I've been eagerly waiting for it!

I'm wondering, how do I include images in my pages? Right now I'm trying:

![Image title](images/filename.jpg)

Where I created a folder called "images" inside the "assets" folder. However, this image appears as broken in the PDF.

Thanks for your time!

Is there any chance of including the input files in the example zip file, as well as the output files? Or perhaps a separate simple example of some of the features used?

First, Thanks for releasing this great tool!

I've installed globally using

composer global require themsaid/ibis

Then went into an empty directory and ran:

ibis init

I then get:

PHP Warning:  require(/Users/dave/.composer/vendor/themsaid/ibis/vendor/autoload.php): failed to open stream: No such file or directory in /Users/dave/.composer/vendor/themsaid/ibis/ibis on line 10

Warning: require(/Users/dave/.composer/vendor/themsaid/ibis/vendor/autoload.php): failed to open stream: No such file or directory in /Users/dave/.composer/vendor/themsaid/ibis/ibis on line 10
PHP Fatal error:  require(): Failed opening required '/Users/dave/.composer/vendor/themsaid/ibis/vendor/autoload.php' (include_path='.:/usr/local/Cellar/php/7.4.11/share/php/pear') in /Users/dave/.composer/vendor/themsaid/ibis/ibis on line 10

Fatal error: require(): Failed opening required '/Users/dave/.composer/vendor/themsaid/ibis/vendor/autoload.php' (include_path='.:/usr/local/Cellar/php/7.4.11/share/php/pear') in /Users/dave/.composer/vendor/themsaid/ibis/ibis on line 10

Have I missed a step?

Hi, Mohamed Said,

This is the first run through to keep in touch with you.

I attempted to utilize Arabic letters in your task ibis, it is brilliant.

In any case, is there any approach to set the direction from left to right when utilizing Arabic letters.

Respects,

Mostafa Gaber

Hi, this tool is really simple to use compared to some other solutions I have tried so kudos on that 👍

It would be great if it could support HTML based covers rather than just a JPG. I am hoping I will be able to use this tool for creating reports and the cover I had in mind was more textual with a different layout. Are you open to supporting this use case? I imagine as this project grows, some more configuration options in ibis.php would allow it to support many different document use cases in addition to ebooks.

Hello - and thanks for creating this awesome project. :)

I noticed your .php_cs configuration file and the composer command. However, I noticed some code could be out of standard. In addition, since everyone uses different code standard tools, they might not have php-cs-fixer installed globally. That being said, I'd like to propose the following:

• Ensure all files are code standard compliant
• Add php-cs-fixer as a local project install as a composer dev dependency
• Add a script to composer to do a dry-run for people who'd like to review their code standard changes - and to be ran as part of CI
• Add a github action to run the code standard on pushes and pull requests

I'll submit a pull request with these suggested updates for your review.

Perfect project for me because I write everything in Markdown. However I just got finished updating everything Composer needed in order to finally install it and after ibis init I got the error: Valet only supports the Mac operating system. I'm trying to run this in WSL 2 on Windows 10. I checked the composer.json in the Ibis repo and don't see Laravel or Valet as a dependency, so I'm wondering if this is a side effect of my setup or a dependency of a dependency.

Any way to get this running on Windows or Linux?

Now the markdown files are loaded from : $currentPath.'/content' Where $currentPath is retrieved from getcwd().

My proposal is to allow the user to define the directory (absolute or relative) where to load markdown files. The input argument could be --markdowndir=

If you want i could open a PR.

This PR looks for a configure_commonmark key in the config and if present, it will be called passing the $environment through.

This will allow people to swap in new highlighters or any other commonmark extensions, of which there are many.

Let me know what you think!

Trying to run the global installer composer global require themsaid/ibis I'm getting a conflict with the current Laravel Valet:

Changed current directory to /Users/ericlbarnes/.composer
Using version ^0.1.1 for themsaid/ibis
./composer.json has been updated
Running composer update themsaid/ibis --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - illuminate/container v8.13.0 requires illuminate/contracts ^8.0 -> found illuminate/contracts[v8.0.0, ..., v8.13.0] but it conflicts with another require.
    - laravel/valet v2.12.0 requires illuminate/container ~5.1|^6.0|^7.0|^8.0 -> satisfiable by illuminate/container[v8.13.0].
    - laravel/valet is locked to version v2.12.0 and an update of this package was not requested.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Operating System: Linux Ubuntu 20.04

I ran the command composer global require themsaid/ibis and completed the installation successfully. Upon running ibis init, I get an error.

• upgrade and check with PHP 8.2
• upgrade code using new renderer of Commonmark
• upgrade GitHub Actions workflow
• using Pint with PSR12
• added configuration for cover image (instead of using hardcoded cover.jpg, you can specify a new file name and format, for example, my-cover.png)

Following this issue thread https://github.com/themsaid/ibis/issues/27 it appears that the following type of markdown tables are supported:

| Command | Description | |-----------|-------------| | Test | Test |

i.e. raw format:

| Command | Description |
|---------|-------------|
| Test    | Test        |

However, the following format is not supported:

|Short Flag |Long Flag |Description | |:---|:---|:---| |-l|

i.e. in raw code format:

|**Short Flag**   |**Long Flag**   |**Description**   |
|:---|:---|:---|
|`-l`|<center>-</center>|Show Results in long format|

This format is valid markdown that works here on Github, but when rendered in the PDF, it comes out as a literal string:

I could potentially do a PR to add this new type of parser, but would need some guidance on where to start.

Now, there are:

• cover (if exists) (image or html)
• TOC
• content (pages from markdown)

I would like to suggest having an optional "post cover" after the cover and TOC. This may be useful for having the typical page with inscription "thanks to..." or some quotes.

My proposal is:

• if exists a /assets/post-cover.html file (with some content, like cover.html) (so not mandatory), append the post-cover.html file after the cover in buildPdf() function.

If you want, I can open a PR for this.