If I try to build hi.fpm.dev package on windows I am facing below error:

Error: PackageError { message: "Could not find `how-to/get-started-github-pages.ftd` in original package" }

This variable should be provide us access to location.hash in browser.

<meta name="viewport" content="width=device-width, initial-scale=1">

Ref.:
https://developer.mozilla.org/en-US/docs/Web/HTML/Viewport_meta_tag

We can possibly optimise fpm build by doing this. Once #62 is implemented we will have a dependency graph.

We will also store another file, .build-workspace/hashes.ftd which will store hash of every file during fpm build:

-- document: filename.ftd
hash: <sha256 hash of filename.ftd>

In order for this to work reliably (so changes on file system why fpm build is working do not mess our hashing and dependency) we will first do an in-memory read of all ftd files, and compute the current hash.

When processing any file, in fpm::commands::build::process_ftd() we will use content of hashes.ftd and deps.ftd file to see if the hash of ftd file or any of it's dependencies has changed since last run. If not we would skip this file.

What about missing or modified html files?

To be sure we do proper rebuild, we will also store the hash of generated HTML file, and if the HTML file is missing of hash does not match, we will rebuild the ftd file.

https://kawamurakazushi.com/20200217-publishing-a-rust-cli-to-Homebrew/

After fastn-stack/ftd.dev@b16c378 I am getting panic when trying to do fpm build --base=/:

amitu@Apples-MacBook-Pro-2 ftd.dev % fpm build --base=/ 
thread 'main' panicked at 'index out of bounds: the len is 4 but the index is 4', /Users/amitu/.cargo/git/checkouts/ftd-1d08df4728f7983b/68c0f9d/src/p2/interpreter.rs:452:15
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Its even problematic because even

  - `ftd::p1` grammar
    url: /p1-grammar/

Doesn't work.

https://reddit.com/r/rust/comments/sturle/is_there_any_crate_that_will_make_by_panic/

Getting the following error:

Error: PackageError { message: "failed to parse ParseError { message: \"ftd.dev/examples/diagram#config is not present in doc, Err(ParseError { message: \\\"ftd.dev/examples/diagram: not found (\\\\\\\"ftd.dev/examples/diagram#config\\\\\\\"), f: get_thing\\\", doc_id: \\\"ftd.dev/examples/diagram\\\", line_number: 1 })\", doc_id: \"ftd.dev/examples/diagram\", line_number: 1 }" }

We used ~ in FifthTry.com as separator but ~ is not allowed in filenames with Github Pages. I think /-/ looks better than /FPM/ etc.

• fpm.bind
• remove the zip key

Trying to build this repo.
Getting the following error

Error: PackageError { message: "failed to parse ParseError { message: \"library not found: arpita-jaiswal.github.io/vivekanand/config\", doc_id: \"\", line_number: 0 }" }

We want to store dependency tree of every ftd module in a package in .build-workspace folder.

fpm build command will create .build-workspace/deps.ftd file:

-- deps: name/of/file.ftd
depends-on: some-file.ftd
depends-on: some-other-file.ftd

The type of deps is going to be:

-- record deps:
caption name:
string list depends-on:

Implementation Detail

In fpm::Library we will add dependencies, vector containing all files that were loaded, and we will modify fpm::Library.get() method and on every call to .get() we will store the name argument to fpm::LIbrary.dependencies.

We will also add a method: write_depds() in fpm::Library. fpm::Library's document_id will be the deps.name and .dependencies will be written as depends-on.

while using below spnipet:

-- ft.header-toc:
$processor$: toc-v2

- Quickstart: quickstart/
- Use this template
  url: https://github.com/FifthTry/Blue-Sapphire-Template/generate/

I see below error:

thread 'main' panicked at 'not yet implemented', src\library\new_toc.rs:291:26
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

https://doc.rust-lang.org/std/panic/fn.catch_unwind.html

Since our spacial pages would not exist in original project, eg /-/translation-status/ is fpm feature and does not exist in canonical (non fpm) location (we are assuming people will only use canonical when they are importing their content to FPM only for translation purpose), the special URLs on canonical host will 404.

/-/* pages should not include <link rel="canonical"> tag.

Before merging a change it would be great to know if fpm.dev/ftd.dev and a bunch of our FPM packages compile.

on Windows fpm build is not fetching packages. We need to manually download all packages.

Error: IoError(Os { code: 3, kind: NotFound, message: "The system cannot find the path specified." })

Can we have a list of missing packages it's looking for?

When creating a section, sometime I want to create a folder, and put everything related to that section in that folder. Currently its organised as <section-name>.ftd and <section-name>/intro.ftd and so on. I prefer if everything related to section can be kept in a folder.

What if both foo.ftd and foo/index.ftd exist?

Easiest thing would be to be strict and error out. For now let's go with this and wait for issues say this is a bad idea.

We can use one of the following https://crates.io/keywords/minify maybe? Or consider individual minifiers eg uglify-js etc to get maximum compression.

foo.com/x/y.png would be stored in .build/-/foo.com/x/y.png, for all static files (current package and dependencies). When referring to status URLs, eg image etc, always use -/foo.com/x/y.png etc path.

We can use https://docs.rs/comrak/latest/comrak/struct.ComrakRenderOptions.html#structfield.width for this.

Currently we ship some UI in those files, but they should be part of theme. Ideal version would be:

-- import: ft
-- import:  <package-name>/config

-- ft.package-info-page:

And so on. We will have three components: package-info-page, translation-status-page and original-status-page to be provided by themes implementing fpm.dev/fpm-info.

In ftd.dev repo right now fpm status is not working.

Error: IoError(Error { kind: InvalidData, message: "stream did not contain valid UTF-8" })

<meta name="theme-color" content="#3c790a">

IMP:: => the color value should be configurable.

This is how we should be able to do this.

-- import: fpm

-- fpm.theme-color: #3c790a

Ref:

1. https://html.spec.whatwg.org/multipage/semantics.html#meta-theme-color
2. https://css-tricks.com/meta-theme-color-and-trickery/

Say I have a dependency on Forest-Theme, which itself depends on fifthtry.github.io/header. Now say I created my own mycompany.com/header which implements fifthtry.github.io/header and I want Forest-Theme to use my header instead of the FifthTry header, I should be able to do this:

-- fpm.dependency: fifthtry.github.io/Forest-Theme as ft
override: mycompany.com/header as fifthtry.github.io/header

override can be called once or more. Also it works recursively, eg if ft does not directly use a dependency but is used transitively.

sh -c "$(curl -fsSL https://raw.githubusercontent.com/FifthTry/fpm/main/install-fpm.sh)"

The above command is not working for the new mac because it is moving downloaded fpm binary inside /usr/local/bin directory and there is no bin folder present inside /usr/local. Hence it fails.