Overview

I'm trying to build a simple livemark static site with a colleague and we're experiencing a very interesting problem due to operational systems differences, I believe.

I'm using Linux ubuntu 20.04 and he's using Windows 10.

When I run livemark start or livemark build on my ubuntu everything goes well, but when he does the same on windows it builds weird URLs. It appears that "/" is been changing to "%5C", as you can see here.

The Github source code could be found here.

I also tried to run livemark build --help and see if there were some options related to windows construction and also to search for something in the documentation.

Hi @roll! I am going through the docs and am getting errors when trying to build / start the site.

First, I created a new project without an index.md and got errors, and I also tried it after creating an index.md file and got the same errors. Here are the errors:

livemark build: 'str' object has no attribute 'setdefault'

I also tried livemark start & got an error: AttributeError: 'str' object has no attribute 'copy'

Then, I tried building the site from this repo and also got errors.

livemark build: to_snap() got an unexpected keyword argument 'json'

and

livemark start: TypeError: to_snap() got an unexpected keyword argument 'json'

I'm on Python 3.8 & Livemark 0.39.0

Any ideas? Thanks!

The page: https://github.com/frictionlessdata/livemark/blob/main/pages/getting-started/starting-project.md

gives instructions to start a project but it fails with:

$ livemark start
No documents to build in the project

Obvious reason is, that the file livemark.yaml is incomplete:

brand:
  text: My Project
site:
  favicon: assets/favicon.ico

as it does not contain any pages section so there is nothing to build.

• fixes #205

With livemark is used in Windows, outside a POSIX compliant system the generated URLs inside the generated HTML will have Window back slashes (\folder\file instead of /folder/file). This happens because of how gel_relapath is generating the path using os.path.join. os.path always follows the format of the current OS, this means, if you are in windows it is going to use back slashes. The problem happens that urls follow POSIX path, with this slash /.

I don't know if there are other places that we need to change the paths to POSIX ones. If we just change everywhere that os.path is used, this will causes problems for windows user when livemark need to open a file somewhere.

Overview

Hi @roll , first of all: this is great idea, a great product, thank you very much 🙏🙏🙏.

When I install it, I have this error:

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
mkdocs-rss-plugin 0.17.0 requires Jinja2<3,>=2, but you have jinja2 3.0.2 which is incompatible.
jinja-markdown 1.200630 requires Jinja2~=2.11, but you have jinja2 3.0.2 which is incompatible.
datapackage-pipelines 2.2.6 requires python-dateutil<2.8.1, but you have python-dateutil 2.8.1 which is incompatible.

Does the only solution is to use virtualenv?

Thank you

Please preserve this line to notify @roll (lead of this repository)

Installing with the recommended approach (pip install livemark) or a fresh virtual environment with pip, setuptools, and wheel up to date currently takes a long time, as the frictionless requirement is set with a star: https://github.com/frictionlessdata/livemark/blob/cd4200f143dfe6d77874de23e8c13a1cbeea0e08/setup.py#L48

Due to requirement settings in dependencies, it means that pip also downloads multiple versions of other libraries (livemark itself, simpleeval, etc.). In a non-fresh environment (e.g. one in which frictionless is already installed) it might lead to conflicts during installation, but I was not able to immediately reproduce it (maybe it depends on the order the packages are installed). The multiple downloads were reproduced both under the latest stable Ubuntu (with Python3.8) and WSL.

Overview

Currently, it works fine on localhost and https://livemark.frictionlessdata.io/ but there might be basepath problems e.g. on GIthub Pages without a custom domain.

Overview

It needs to be finished for version 1

Plan

• [ ] structure: logic, table, chart, script, markup, sidebars, widgets, config, plugins?
• [ ] improve current articles
• [ ] add new articles
• [ ] update the main (demo) page
• [ ] update the readme (features)

I quickly read thru all the pages & fixed typos/grammar.

I can merge this @roll but I'll wait until tomorrow in case you have time & want to look first.

The documentation is looking really nice!!

Overview

We have a Github Template for Livemark project - https://github.com/frictionlessdata/livemark-project. We need to use it instead of livemark/assets/documents/template.md to avoid duplication.

Overview

Currently, even though with caching it's not a good idea to have long-running scripts in the script snippet because every livemark build/start; it will be fully executed (although cached during the start session).

ATM we need to write separate scripts to fetch the data and we can include it to the site using FilePlugin. We might consider some special options like slow tags/etc to include these scripts to Livemark makrdown. It's something to investigate.

Overview

It's really popular feature for the writing engines - an ability to have some sections hidden by default with an ability to expand by a reader