So that you don't have to scroll back up

Then use its built-in http.FileServer to handle '/*' routes that are not prefixed by neither projects/ nor database/. The webview will navigate to localhost:(some detected available port) and the server will serve both user content and built Svelte files

See: https://github.com/rakyll/statik

Since they need to be inserted at each occurence of the abbreviation's name, they shouldn't be entered in markdown editors. I would handle them like this:

In content blocks:

• Strip tags before giving paragraph content to tiptap
• Give all abbreviation definitions
• When updating the value prop in , apply all abbreviations

And, outside of the content grid:

• Add a list of inputs to define/edit/remove abbreviation definitions, just like footnotes (which also need to be implemented...)

The GUI only focuses on managing your database for now, but I actually want it to handle the whole process, up to site publishing.

So, to generate the site, some kind of templates need to exist.

But this becomes a little more tricky to do without knowledge of at least HTML & CSS.

The idea is to provide people with ortfo themes, that are HTML template files along assets like JS & CSS, and those that can't be bothered to learn HTML&CSS can just use themes.

• People still want to control what shows up on e.g. about pages (all pages that aren't :work, :tag, :technology and :site), so markdown as a HTML preprocessor needs to be supported just as Pug is (shouldn't be hard)
• People might stil want to tweak things like colors, fonts, so a 'Customize theme' section should be available somewhere, and would expose top-level (:root) CSS variables for people to change
• They also still want to put e.g. their personal logo on the navbar (which won't be modifyable without programming, of course), so access to a 'Assets' section where user can select files to use with the theme is needed

Warn on use of reserved URL characters

If the user modified a work since the rebuild start, apply the changes back after the changes from the DB rebuild

Provide undo functionnality for operations on content blocks (moving, resizing, deleting, adding)

Might cause user data loss, make sure the user has everything saved before doing so. This allows for hot theme-swapping, for example.

Right now the generated ortfodb.yaml file is empty, thus the db can't be built

I can’t distribute the .exe as-is, as I need to run this to ensure loopback support from UWP contexts:

CheckNetIsolation.exe LoopbackExempt -a -n="Microsoft.Win32WebViewHost_cw5n1h2txyewy"

(see Accessing localhost on Windows on webview/webview’s README)

I should take advantage of this to also ask for a location to store configuration data

(and maybe separate portfolio-database/ and ui_state.json from settings.json)

That way, users can't think that different languages have independent layouts

With one global switch, it appears as though the two languages for the same work are completely independent, and users might be surprised when they see the layout edits they did in one language affect the other language(s).

This would help prevent crashes with the app when updating the database schema with new versions

See ortfo/db#48

The following should be done:

• Add to the $database store
• Prepend instead of appending, so that the user sees the new tag and can confirm that it was added
• Close the modal!!! This really gives the impression that some fields should've been filled and that the tag was not added

In editor, in fields for tags & technologies used, use suggestions (just like languages in settings) to suggest tags & technologies

Especially for <SearchableList>, anywhere where there's :focus and :hover, it's getting kinda messy without nesting. I tried not using a preprocessor.

So that exisiting descriptions are found

need scrolling/updating the UI before the app registers a layout change and shows a "unsaved changes" dot in the navbar. Forcing a work update on <Grid>'s on:change does not fix the problem.

• Debian (.deb)
• Fedora (.rpm)
• Arch (PKGBUILD)
• Gentoo (.ebuild)
• Stampede (.slp)
• Slackware (.tgz)
• nix
• homebrew (needs significant popularity)
• chocolatey
• winget
• snap
• flatpak
• appimage
• Windows (.exe or .msi)
• MacOS (.dmg)

And maybe some stores:

• App Store (if I can)
• Windows store

Make it slide from down (slide up) when appearing and slide into down (slide down) when disappearing

Could be used to customize components of the portfolio:

Shows individual components like content blocks (link, media, ...) and CSS/HTML code that can be modified on-the-fly to see modifications

Importing a .m3u asks if you want to bulk-import audio files referenced as separate media blocks, one for each file

See

Used to:

• Start in specific tab (--tab=TabName (no effect if ui_state.editingworkid is empty), --edit=EditingWorkID (also sets --tab=editor))
• Start with specific settings (--settings=SettingsFile, --settings.Key=Value to override specific settings, --projects=ProjectsFolder as an alias to --settings.projectsfolder=ProjectsFolder)
• Start with specific UI state (--state=UIStateFile, --state.Key=Value to override specific state values)
• Get a setting / ui state (--setting.SettingKey, --state.UIStateKey)
• Show version (--version)
• Show info (--info, like --version but also shows build date, commit hash)
• Launch update without launching GUI (--update) (Depends on #32)
• Maybe hidden experimental settings could be toggled via CLI only
• Start with specific window dimensions (--width, --height)
• Maybe other stuff????

Some go packages exist to self-update an app. Leverage them with Github Releases to provide an in-app update mechanism.

When creating a new media or link, copy over the source/url to other languages if their versions of that block have empty source/url. For paragraphs, maybe copy over the text of the paragraph if other versions are empty?

Allow changing the ID of a project, which:

• renames the folder
• updates all paths that reference that folder
• (rebuilds the db)

For example, every work using the Lark python library should have #language

currently, it's hardcoded as .portfoliodb

Right now the generated ortfodb.yaml file is empty, thus the db can't be built

Add a vim keyboard navigation mode

So that you don't have to scroll back up.

Make it set itself back into the page when its place appears (when scrolled down) — pretty much a postion: sticky, except that it should be animated.

Also, when not scrolled completely, the new block should be added above the bottommost visible block.

Right now this is done alongside the portfolio's pages translations, it should be separate, just like work descriptions are

should add the old slug to the aliases

And rename src/ to frontend/

undefined