mb21 / mb21/panwriter

User data directory location

Open
#17 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
1.3k
Forks
66
PR merge metrics
No merged PRs in 30d

Description

Hi and thanks for this pandoc editor. I'm hoping to recommend it for a new project. I would be planing to use this as a tool for previewing, but not rendering, which would take place on a CI server. I notice that it's possible to set default.yml in a so called user data directory. But what I'd really want, is to have a configuration set from the same location, that way the respository we'd be working with would be self contained and every contributor would be editing the same .css files using the same configuration. Would it be possible for panwriter to read configuration files from the same directory as the source file? In the end, relative paths to .css files is what I'm mostly after, and since we have so many files, it wouldn't make sense to copy paste the styles into the metadata section of each file.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating how Panwriter resolves the user data directory and reads default.yml, then trace how source-file locations and CSS paths are handled. Done means a repository can provide shared configuration beside its source files, with relative CSS paths applying consistently during preview without copying styles into each file.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, electron, react, typescript
Domain
content, desktop, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.