You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Contributing to TagStudio
2
2
3
-
_Last Updated: November 19th, 2024_
3
+
_Last Updated: December 12th, 2024_
4
4
5
5
Thank you so much for showing interest in contributing to TagStudio! Here are a set of instructions and guidelines for contributing code or documentation to the project. This document will change over time, so make sure that your contributions still line up with the requirements here before submitting a pull request.
6
6
@@ -14,6 +14,7 @@ Thank you so much for showing interest in contributing to TagStudio! Here are a
14
14
- Check the [Feature Roadmap](/docs/updates/roadmap.md) page to see what priority features there are, the [FAQ](/README.md/#faq), as well as the open [Issues](https://github.com/TagStudioDev/TagStudio/issues) and [Pull Requests](https://github.com/TagStudioDev/TagStudio/pulls).
15
15
- If you'd like to add a feature that isn't on the feature roadmap or doesn't have an open issue, **PLEASE create a feature request** issue for it discussing your intentions so any feedback or important information can be given by the team first.
16
16
- We don't want you wasting time developing a feature or making a change that can't/won't be added for any reason ranging from pre-existing refactors to design philosophy differences.
17
+
-**Please don't** create pull requests that consist of large refactors, *especially* without discussing them with us first. These end up doing more harm than good for the project by continuously delaying progress and disrupting everyone else's work.
17
18
- If you wish to discuss TagStudio further, feel free to join the [Discord Server](https://discord.com/invite/hRNnVKhF2G)
18
19
19
20
### Contribution Checklist
@@ -150,9 +151,6 @@ Most of the style guidelines can be checked, fixed, and enforced via Ruff. Older
150
151
151
152
### Commit and Pull Request Style
152
153
153
-
> [!CAUTION]
154
-
> Please do not close and re-open pull requests. This makes it **much** more difficult to re-pull during reviews. If you would like to signal that your pull request is not ready, please mark is as a draft instead.
155
-
156
154
- Use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0) as a guideline for commit messages. This allows us to easily generate changelogs for releases.
157
155
- See some [examples](https://www.conventionalcommits.org/en/v1.0.0/#examples) of what this looks like in practice.
158
156
- Use clear and concise commit messages. If your commit does too much, either consider breaking it up into smaller commits or providing extra detail in the commit description.
Copy file name to clipboardExpand all lines: docs/help/ffmpeg.md
+21-8Lines changed: 21 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,38 +3,51 @@
3
3
FFmpeg is required for thumbnail previews and playback features on audio and video files. FFmpeg is a free Open Source project dedicated to the handling of multimedia (video, audio, etc) files. For more information, see their official website at [ffmpeg.org](https://www.ffmpeg.org/).
4
4
5
5
## Installation on Windows
6
+
6
7
### Prebuilt Binaries
7
-
Pre-built binaries from trusted sources are available on the [FFmpeg website](https://www.ffmpeg.org/download.html#build-windows). To install:
8
+
9
+
Pre-built binaries from trusted sources are available on the [FFmpeg website](https://www.ffmpeg.org/download.html). Under "More downloading options" click on the Windows section, then under "Windows EXE Files" select a source to download a build from. Follow any further download instructions from whichever build website you choose.
1. Download 7z or zip file and extract it (right click > Extract All)
10
19
2. Move extracted contents to a unique folder (i.e; `c:\ffmpeg` or `c:\Program Files\ffmpeg`)
11
-
3. Add FFmpeg to your PATH
20
+
3. Add FFmpeg to your system PATH
12
21
13
-
1.Go to "Edit the system environment variables"
14
-
2. Under "User Variables", select "Path" then edit
15
-
3. Click new and add `<Your folder>\bin` (e.g; `c:\ffmpeg\bin` or `c:\Program Files\ffmpeg\bin`)
16
-
4. Click okay
22
+
1.In Windows, search for or go to "Edit the system environment variables" under the Control Panel
23
+
2. Under "User Variables", select "Path" then edit
24
+
3. Click new and add `<Your folder>\bin` (e.g; `c:\ffmpeg\bin` or `c:\Program Files\ffmpeg\bin`)
25
+
4. Click "Okay"
17
26
18
27
### Package Managers
28
+
19
29
FFmpeg is also available from:
20
30
21
31
1. WinGet (`winget install ffmpeg`)
22
32
2. Scoop (`scoop install main/ffmpeg`)
23
33
3. Chocolatey (`choco install ffmpeg-full`)
24
34
25
35
## Installation on Mac
36
+
26
37
### Homebrew
27
-
FFmpeg is available via [Homebrew](https://brew.sh/) and can be installed via:
28
38
29
-
`brew install ffmpeg`
39
+
FFmpeg is available under the macOS section of the [FFmpeg website](https://www.ffmpeg.org/download.html) or can be installed via [Homebrew](https://brew.sh/) using `brew install ffmpeg`.
30
40
31
41
## Installation on Linux
42
+
32
43
### Package Managers
44
+
33
45
FFmpeg may be installed by default on some Linux distributions, but if not, it is available via your distro's package manager of choice:
34
46
35
47
1. Debian/Ubuntu (`sudo apt install ffmpeg`)
36
48
2. Fedora (`sudo dnf install ffmpeg-free`)
37
49
3. Arch (`sudo pacman -S ffmpeg`)
38
50
39
51
# Help
52
+
40
53
For additional help, please join the [Discord](https://discord.gg/hRNnVKhF2G) or create an Issue on the [GitHub repository](https://github.com/TagStudioDev/TagStudio)
Copy file name to clipboardExpand all lines: docs/index.md
+40-18Lines changed: 40 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,39 +9,61 @@ title: Home
9
9
10
10

11
11
12
-
TagStudio is a photo & file organization application with an underlying system that focuses on giving freedom and flexibility to the user. No proprietary programs or formats, no sea of sidecar files, and no complete upheaval of your filesystem structure.
12
+
TagStudio is a photo & file organization application with an underlying tag-based system that focuses on giving freedom and flexibility to the user. No proprietary programs or formats, no sea of sidecar files, and no complete upheaval of your filesystem structure.
13
13
14
-
<figuremarkdown="span">
14
+
<figurewidth="60%"markdown="span">
15
15

16
-
<figcaption>TagStudio Alpha v9.1.0 running on Windows 10</figcaption>
16
+
<figcaption>TagStudio Alpha v9.4.2 running on Windows 10</figcaption>
17
17
</figure>
18
18
19
19
## Goals
20
20
21
-
-To achieve a portable, privacy-oriented, open, extensible, and feature-rich system of organizing and rediscovering files.
22
-
-To provide powerful methods for organization, notably the concept of tag composition, or “taggable tags”.
23
-
-To create an implementation of such a system that is resilient against a user’s actions outside the program (modifying, moving, or renaming files) while also not burdening the user with mandatory sidecar files or otherwise requiring them to change their existing file structures and workflows.
24
-
-To support a wide range of users spanning across different platforms, multi-user setups, and those with large (several terabyte) libraries.
25
-
-To make the darn thing look like nice, too. It’s 2024, not 1994.
21
+
- To achieve a portable, private, extensible, open-format, and feature-rich system of organizing and rediscovering files.
22
+
- To provide powerful methods for organization, notably the concept of tag inheritance, or “taggable tags”_(and in the near future, the combination of composition-based tags)._
23
+
- To create an implementation of such a system that is resilient against a user’s actions outside the program (modifying, moving, or renaming files) while also not burdening the user with mandatory sidecar files or requiring them to change their existing file structures and workflows.
24
+
- To support a wide range of users spanning across different platforms, multi-user setups, and those with large (several terabyte) libraries.
25
+
- To make the darn thing look like nice, too. It’s 2024, not 1994.
26
26
27
27
## Priorities
28
28
29
-
1.**The concept.** Even if TagStudio as a project or application fails, I’d hope that the idea lives on in a superior project. The [goals](#goals) outlined above don’t reference TagStudio once - _TagStudio_ is what references the _goals._
29
+
1.**The concept.** Even if TagStudio as an application fails, I’d hope that the idea lives on in a superior project. The [goals](#goals) outlined above don’t reference TagStudio once - _TagStudio_ is what references the _goals._
30
30
2.**The system.** Frontends and implementations can vary, as they should. The core underlying metadata management system is what should be interoperable between different frontends, programs, and operating systems. A standard implementation for this should settle as development continues. This opens up the doors for improved and varied clients, integration with third-party applications, and more.
31
31
3.**The application.** If nothing else, TagStudio the application serves as the first (and so far only) implementation for this system of metadata management. This has the responsibility of doing the idea justice and showing just what’s possible when it comes to user file management.
32
-
4. (The name.) I think it’s fine for an app or client, but it doesn’t really make sense for a system or standard. I suppose this will evolve with time.
32
+
4. (The name.) I think it’s fine for an app or client, but it doesn’t really make sense for a system or standard. I suppose this will evolve with time...
33
33
34
34
## Feature Roadmap
35
35
36
36
The [Feature Roadmap](updates/roadmap.md) lists all of the planned core features for TagStudio to be considered "feature complete" along with estimated release milestones. The development and testing of these features takes priority over all other requested or submitted features unless they are later added to this roadmap. This helps ensure that TagStudio eventually sees a full release and becomes more usable by more people more quickly.
37
37
38
38
## Current Features
39
39
40
-
- Create libraries/vaults centered around a system directory. Libraries contain a series of entries: the representations of your files combined with metadata fields. Each entry represents a file in your library’s directory, and is linked to its location.
41
-
- Add metadata to your library entries, including:
42
-
- Name, Author, Artist (Single-Line Text Fields)
43
-
- Description, Notes (Multiline Text Fields)
44
-
- Tags, Meta Tags, Content Tags (Tag Boxes)
45
-
- Create rich tags composed of a name, a list of aliases, and a list of “subtags” - being tags in which these tags inherit values from.
46
-
- Search for entries based on tags, ~~metadata~~ (TBA), or filenames/filetypes (using `filename: <query>`)
47
-
- Special search conditions for entries that are: `untagged`/`no tags` and `empty`/`no fields`.
40
+
### Libraries
41
+
42
+
- Create libraries/vaults centered around a system directory. Libraries contain a series of entries: the representations of your files combined with metadata fields. Each entry represents a file in your library’s directory, and is linked to its location.
43
+
- Address moved, deleted, or otherwise "unlinked" files by using the "Fix Unlinked Entries" option in the Tools menu.
44
+
45
+
### Metadata + Tagging
46
+
47
+
- Add metadata to your library entries, including:
48
+
- Name, Author, Artist (Single-Line Text Fields)
49
+
- Description, Notes (Multiline Text Fields)
50
+
- Tags, Meta Tags, Content Tags (Tag Boxes)
51
+
- Create rich tags composed of a name, a list of aliases, and a list of “parent tags” - being tags in which these tags inherit values from.
52
+
- Copy and paste tags and fields across file entries
53
+
- Generate tags from your existing folder structure with the "Folders to Tags" macro (NOTE: these tags do NOT sync with folders after they are created)
54
+
55
+
### Search
56
+
57
+
- Search for entries based on tags, ~~metadata~~ (TBA), or filenames/filetypes (using `filename: <query>`).
58
+
- Special search conditions for entries that are: `untagged` and `empty`.
59
+
60
+
### File Entries
61
+
62
+
- All\* file types are supported in TagStudio libraries - just not all have dedicated thumbnail support.
63
+
- Preview most image file types, animated GIFs, videos, plain text documents, audio files\*\*, Blender projects, and more!
64
+
- Open files or file locations by right-clicking on thumbnails and previews and selecting the respective context menu options. You can also click on the preview panel image to open the file, and click the file path label to open its location.
65
+
- Delete files from both your library and drive by right-clicking the thumbnail(s) and selecting the "Move to Trash"/"Move to Recycle Bin" option.
66
+
67
+
> _\* Weird files with no extension or files such as ".\_DS_Store" currently have limited support._
0 commit comments