mirror of
https://github.com/foambubble/foam.git
synced 2026-04-24 03:01:01 -04:00
deb77328c0
* reorganized and updated foam docs * minor changes to vscode extension readme * added 404 page and minor changes Co-authored-by: Joe Previte <jjprevite@gmail.com>
37 lines
2.1 KiB
Markdown
37 lines
2.1 KiB
Markdown
# Inbox
|
|
|
|
Uncategorised thoughts, to be added
|
|
|
|
- Release notes
|
|
- Markdown Preview
|
|
- It's possible to customise the markdown preview styling. **Maybe make it use local foam workspace styles for live preview of the site??**
|
|
- See: https://marketplace.visualstudio.com/items?itemName=bierner.markdown-preview-github-styles
|
|
- Use VS Code [CodeTour](https://marketplace.visualstudio.com/items?itemName=vsls-contrib.codetour) for onboarding
|
|
- Investigate other similar extensions:
|
|
- [Unotes](https://marketplace.visualstudio.com/items?itemName=ryanmcalister.Unotes)
|
|
- [vscode-memo](https://github.com/svsool/vscode-memo)
|
|
- [gistpad wiki](https://github.com/jevakallio/gistpad/tree/master/src/repos/wiki)
|
|
- Open in Foam
|
|
- When you want to open a Foam published website in your own VS Code, we could have a "Open in Foam" link that opens the link in VS Code via a url binding (if possible), downloads the github repo locally, and opens it as a Foam workspace.
|
|
- Every Foam could have a different theme even in the editor, so you'll see it like they see it
|
|
- UI and layout design of your workspace can become a thing
|
|
- VS Code Notebooks API
|
|
- https://code.visualstudio.com/api/extension-guides/notebook
|
|
- Future architecture
|
|
- Could we do publish-related settings as a pre-push git hook, e.g. generating footnote labels
|
|
- Running them on Github Actions to edit stuff as it comes in
|
|
- Ideally, we shouldn't have to touch files, should be just markdown
|
|
- Looking at the errors/warnings/output panes makes me think, what kind of automated quality tools could we write.
|
|
- Deduplication, finding similarities...
|
|
- Thought Debugger?
|
|
- Knowledge Debugger?
|
|
- Janitor? Gardener?
|
|
- Foam Compiler?
|
|
- Should support Netlify deploys out of the box
|
|
- Foam should tick at the same frequency as your brain, and the Foam graph you build should match the mental model you have in your head, making navigation effortless.
|
|
- Maps have persistent topologies. As the graph grows, you should be able to visualise where an idea belongs. Maybe a literal map? And island? A DeckGL visualisation?
|
|
|
|
Testing: This file is served from the /docs directory.
|
|
|
|
|