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
Tyto arose from a desire of my own and members of my then team. The desire for an intuitive and simple tool for easy workflow/task management. Whether it be managing tasks in the current sprint or your weekly schedule. An ability to share was also vital.
24
+
### Why tyto? What's it for?
25
+
26
+
Tyto arose from the want for an electronic post-it board without the need for accounts. Something simple and intuitive that could be easily shared.
27
+
28
+
It's also the product of my own curiosity being used as an opportunity to pick up new tech stacks. It started as a vanilla JS app utilising one file and experimenting with HTML5 drag and drop. It then grew a little more, and a little more after that. Now it uses Backbone w/ Marionette. The next step? Most likely Angular 2.0 or React.
In truth, most organisations have some form of tool for this. In my experience though, most are cumbersomeand clunky. Employees tend to dislike internal tools. Whiteboards and walls etc. are still covered in sticky notes.
32
+
In truth, most organisations have some form of tool for what Tyto is doing. In my experience though, they can be cumbersome, clunky and just a bit noisy. Some employees tend to dislike internal tools. You still see whiteboards and walls plastered in sticky notes.
29
33
30
-
This is why tyto came about. It's intuitive and minimal. No accounts are necessary. On top of that, the source isn't too hard to grasp making it rather easy to extend and customise.
34
+
This is where Tyto came from, It's my personal intuitive and minimal TodoMVC. No accounts necessary and the source isn't too hard to grasp making it rather easy to extend and customise.
Developer and project managers were the original target audience. A means to share project progression on a more personal level. As opposed to an automated message from an internal system.
38
+
### Who's it for?
39
+
Developer and project managers were the original target audience. A means to share project progression on a more _personal_ level. As opposed to publicly through an internal system. Almost like a complimentary attachment to an email.
For example; a developer may track the different stages of a task. They may also want to track time spent on different tasks and then email this to a project manager.
38
-
Tyto isn't restricting. It has use in a multitude of scenarios. Not quite right out of the box? Extensibility provides a means to create a bespoke version based on theme or functionality.
43
+
There are no restrictions though, it's open source. Not quite right out of the box? Change it :smile:
39
44
40
-
Examples:
41
-
* the plan for the week ahead.
42
-
* ingredient lists.
43
-
* priority lists etc.
44
-
* managing your xmas shopping
45
+
Extensibility provides a means to create a bespoke version based on theme or functionality.
45
46
46
47
Tyto is a personal pet of mine and if it can help others, that's great!
47
48
@@ -59,12 +60,10 @@ Changes are persistent thanks to `localStorage`.
59
60
60
61
Want to move to a different browser or machine though? Use the export utility to export a json file. Load this using the import utility.
61
62
62
-
A persistent workflow across devices? I'm afraid I haven't implemented that. Accounts is not something I am keen on implementing. I think it diverts from my original intention with tyto.
63
-
64
-
63
+
A persistent workflow across devices? I'm afraid I haven't implemented that. Accounts is _not_ something I am keen on implementing/hosting right now. I think it diverts from my original intention with Tyto.
65
64
66
-
####Your own environment
67
-
#####Prerequisites
65
+
####Your own environment
66
+
#####Prerequisites
68
67
If you're cloning the repo and setting up the codebase you are going to need __[node]__, __[bower]__ and __[gulp]__ installed.
69
68
#####Set up
70
69
1. Clone the repo.
@@ -81,14 +80,14 @@ If you're cloning the repo and setting up the codebase you are going to need __[
81
80
82
81
gulp
83
82
84
-
####Hosting
83
+
####Hosting
85
84
I would suggest just taking a snapshot of the `gh-pages` branch and ftp'ing this onto your desired server or web space. Alternatively, follow the set up procedure and FTP the contents of the `public` directory.
86
85
87
86
If you wish to host on Github. Follow the set up procedure first(ideally, with a fork). When happy with your version, use the `deploy` task. This will require familiarity with `gulp-gh-pages` in order to publish to the correct location if other than `gh-pages`.
0 commit comments