We are continuing to provide free Academic & Nonprofit Accounts to a wide range of people, across many different countries.
It turned out we had an internal problem with routing requests for such accounts, when they were made from within the Kerika app itself, as a results of which we must have seemed very unresponsive to some folks who never heard back from us. Our apologies for this!
Anyway, if you would like to get a free Academic & Nonprofit Account, which lets you have an account team size of up to 10 people, please let us know by emailing support@kerika.com. That might be the most reliable way of getting in touch with us…
We used to refer to “Projects” and “Boards” somewhat interchangeably on our website, our blog and in the Kerika app itself.
There was no special reason for this: in our mind, a Project was clearly a Board, and vice-versa, and it never occurred to us that this might prove a source of confusion to anyone.
Well, we were wrong about that.
In the real world, people are very cautious about “starting a new project”, because this might involve getting formal administrative approval, budget allocation, staff changes, etc.
In other words, in the real world a “project” is a big deal.
Unlike so many other collaboration tools that make it difficult for you to create as many boards as you like, Kerika was always designed to make it very easy for you to redesign your work as needed: start new boards, move cards or canvases from one board to another (using Cut, Copy and Paste), and to move ideas and content from one context to another.
Many of our competitors don’t offer this kind of flexibility: either the software makes it hard, or their billing model actively discourages you from creating multiple boards.
That will never be the case with Kerika: we will always support flexibility in how you organize and manage your boards.
Still, our interchangeable use of “projects” and “boards” was definitely causing some confusion, which we have fixed with our latest release by using the term “Board” consistently and avoiding use of the term “Project”.
So, if you were a Project Leader previously, you are now a Board Admin on that board. Your rights and privileges remain the same, it’s just your title that changed.
Board Admin
When you start a new board, what used to be called “New Project” is now labeled “New Board” to make it clear what you are doing:
We used to refer to “Projects” and “Boards” somewhat interchangeably on our website, our blog and in the Kerika app itself.
There was no special reason for this: in our mind, a Project was clearly a Board, and vice-versa, and it never occurred to us that this might prove a source of confusion to anyone.
Well, we were wrong about that.
In the real world, people are very cautious about “starting a new project”, because this might involve getting formal administrative approval, budget allocation, staff changes, etc.
In other words, in the real world a “project” is a big deal.
Unlike so many other collaboration tools that make it difficult for you to create as many boards as you like, Kerika was always designed to make it very easy for you to redesign your work as needed: start new boards, move cards or canvases from one board to another (using Cut, Copy and Paste), and to move ideas and content from one context to another.
Many of our competitors don’t offer this kind of flexibility: either the software makes it hard, or their billing model actively discourages you from creating multiple boards.
That will never be the case with Kerika: we will always support flexibility in how you organize and manage your boards.
Still, our interchangeable use of “projects” and “boards” was definitely causing some confusion, which we have fixed with our latest release by using the term “Board” consistently and avoiding use of the term “Project”.
So, if you were a Project Leader previously, you are now a Board Admin on that board. Your rights and privileges remain the same, it’s just your title that changed.
Board Admin
When you start a new board, what used to be called “New Project” is now labeled “New Board” to make it clear what you are doing:
We used to refer to “Projects” and “Boards” somewhat interchangeably on our website, our blog and in the Kerika app itself.
There was no special reason for this: in our mind, a Project was clearly a Board, and vice-versa, and it never occurred to us that this might prove a source of confusion to anyone.
Well, we were wrong about that.
In the real world, people are very cautious about “starting a new project”, because this might involve getting formal administrative approval, budget allocation, staff changes, etc.
In other words, in the real world a “project” is a big deal.
Unlike so many other collaboration tools that make it difficult for you to create as many boards as you like, Kerika was always designed to make it very easy for you to redesign your work as needed: start new boards, move cards or canvases from one board to another (using Cut, Copy and Paste), and to move ideas and content from one context to another.
Many of our competitors don’t offer this kind of flexibility: either the software makes it hard, or their billing model actively discourages you from creating multiple boards.
That will never be the case with Kerika: we will always support flexibility in how you organize and manage your boards.
Still, our interchangeable use of “projects” and “boards” was definitely causing some confusion, which we have fixed with our latest release by using the term “Board” consistently and avoiding use of the term “Project”.
So, if you were a Project Leader previously, you are now a Board Admin on that board. Your rights and privileges remain the same, it’s just your title that changed.
Board Admin
When you start a new board, what used to be called “New Project” is now labeled “New Board” to make it clear what you are doing:
We post our tutorial videos on both YouTube and Vimeo, and get far more traffic on YouTube than we do on Vimeo.
But, as we go through a review/refresh of our website, we are switching over to Vimeo for embedding these tutorials, because Vimeo provides a cleaner look that seems to be less intrusive within our own design.
Here’s the same video, embedded from YouTube (on top) and Vimeo (on bottom):
The YouTube video has a weird grey shadow on the top part of the thumbnail, like it was deliberately trying to provide a retro, cathode-ray-tube (CRT) look.
(We are not fans of CRTs; don’t own vinyl any more…)
If you are the only Project Leader on a Task Board, Scrum Board or Whiteboard, you will know when someone joins a board — after all, you would have approved their invitation in the first place.
But, if there are several Project Leaders for a board, it might be one of the others who added somebody to your board, and they might not have discussed this with you…
So, Kerika makes sure you know whenever the project team on any board has changed in any way:
If someone has joined,
If someone’s role has changed,
If someone has left.
(After all, someone could have left the team on their own, without telling you!)
Whenever there is a change in the project team, the Board Settings button on the top-right of the board will appear in orange.
Board Settings is highlighted
Click on the Board Settings button, and you will see the Team tab is highlighted: this is Kerika’s way of drawing your attention to this particular tab within the Board Settings display.
Team tab is highlighted
When you go over to the Team tab, you will see that the new person’s name is highlighted in orange, for a few seconds. It’s a discrete yet very effective notification from Kerika, drawing your attention to the presence of someone new on the team.
Changed roles are highlighted
The same kind of notification is used when someone’s role on the team is changed, e.g. from Team Member to Visitor.
Kerika also tries to let you know when someone has left the team, by highlighting the Project Settings button in orange, and the Team tab within the Project Settings in orange as well.
Smart notifications, from Kerika — the only work management system that’s designed specially for distributed Lean and Agile teams :-)
If you are the only Project Leader on a Task Board, Scrum Board or Whiteboard, you will know when someone joins a board — after all, you would have approved their invitation in the first place.
But, if there are several Project Leaders for a board, it might be one of the others who added somebody to your board, and they might not have discussed this with you…
So, Kerika makes sure you know whenever the project team on any board has changed in any way:
If someone has joined,
If someone’s role has changed,
If someone has left.
(After all, someone could have left the team on their own, without telling you!)
Whenever there is a change in the project team, the Board Settings button on the top-right of the board will appear in orange.
Board Settings is highlighted
Click on the Board Settings button, and you will see the Team tab is highlighted: this is Kerika’s way of drawing your attention to this particular tab within the Board Settings display.
Team tab is highlighted
When you go over to the Team tab, you will see that the new person’s name is highlighted in orange, for a few seconds. It’s a discrete yet very effective notification from Kerika, drawing your attention to the presence of someone new on the team.
Changed roles are highlighted
The same kind of notification is used when someone’s role on the team is changed, e.g. from Team Member to Visitor.
Kerika also tries to let you know when someone has left the team, by highlighting the Project Settings button in orange, and the Team tab within the Project Settings in orange as well.
Smart notifications, from Kerika — the only work management system that’s designed specially for distributed Lean and Agile teams :-)
Less is a CSS pre-processor: it extends CSS by adding variables, mixins, functions and many other techniques that allow easier maintenance of your browser stylesheets.
You can compile Less either on the client side, or on the server. We thought it didn’t matter; but it turns out that Google search engine crawler doesn’t like the client-side compilation:
less.css compilation
If you are using Less on your website, you might want to also avoid client-side compilation so that Google doesn’t barf on it…
Less is a CSS pre-processor: it extends CSS by adding variables, mixins, functions and many other techniques that allow easier maintenance of your browser stylesheets.
You can compile Less either on the client side, or on the server. We thought it didn’t matter; but it turns out that Google search engine crawler doesn’t like the client-side compilation:
less.css compilation
If you are using Less on your website, you might want to also avoid client-side compilation so that Google doesn’t barf on it…
We have added a new feature that should prove handy for a lot of folks: you can now add content — files from your laptop, images from your mobile or tablet, Web links from your Intranet or the Internet, or canvases — to a Task Board or Scrum Board itself.
If this sounds like something that was always there, maybe we need to say that differently: you used to have the ability to add content to a card, now you can add it to the board itself.
There are many situations we have encountered where we want to share content or a canvas with a team, but there wasn’t any obvious place to still it — no single card on the board that seemed like the right place to attach that content.
And that’s because the content we wanted to add was applicable across the entire board, not just relevant to a single card.
This was getting frustrating, so we decided to scratch our itch: a new button on the top-right area of your Kerika app will let you add files, Web links and canvases to the board itself:
Board Attachments
This should make some of you as happy as it has made us!
