We’ve added a “Get notified of updates” section to the header of each Open Decks page. This allows anyone to sign up via either Discord or email and password to then select whether they want to be notified daily or weekly if interesting updates are happening.
The digest email will contain links to new cards as well as cards that have been started or marked as done.
This feature is available to all regular Codecks users as well without having to create an additional sign up.
So feel free to check out the projects on open.codecks.io to see whether there’s some interesting projects you’d like to get updates for!
ctrl/cmd+clickon a card’s id copies just the
$idrather than the full URL. Useful for e.g. commit messages.
This release introduces a reworked shortcut system aimed to make keyboard-based navigation a lot more productive. Hit
? to see all shortcuts available on your current view.
Here’s some highlights:
ctrl/cmd+ato select all cards
bto select the card under the mouse cursor
p, etc opens the corresponding property for the card under the mouse cursor
Returnto open the edit view on an opened card
Arrow Keysto navigate across the mini cards
The Open Deck settings screen now contains charts and counts for your visitors to your project. We also show you the top referrers so you know how people are finding you.
To keep track of your progress, we’ll be sending a weekly digest every Monday to give you a visitor overview of the passed week. Feel free to opt out in the Open Deck settings.
[CARDPUBLICURL] shortcode for better integration with Open Decks.
We’ve released the first version of the Open Decks Portal! It’s a place that highlights the most active and popular projects.
At the moment there are two categories: Staff picks which allows the Codecks team to promote noteworthy and inspirational projects (we’ll populate it soon!). The next category is the Most active open decks one. It’s based on project’s activity of the last 7 days and the card count. We’ll also add a Most popular section once we have the required data.
You can find it under this url: open.codecks.io
If you would like to show up on any of the lists, check your project settings and make sure you’ve agreed to appear there. You’re also able to upload a nice 16:9 promo image for a good first impression of your project.
$command or in the Slack or Discord integration), we’ve added the title of its Hero card.
There are rumors that accountants have feelings too. So we dedicated some time, willing to put a smile on their faces.
We expanded the search functionality. In addition to filtering, you can now jump directly to a deck or card by entering its name.
For an even quicker way to get to your target, you can use the prefix
gd: in the search bar to only show deck or card results. You can use
gad: to go to any card or deck independent of your project visibility.
Rather than limiting you to pick between global milestones or assigning it to a single project, you can now pick as many or few projects you like. For larger teams that will make it a lot easier to focus only on tasks that are relevant to them.
You’re now also able to re-assign the projects (or make it global) after you’ve created a milestone.
Within decks you’re now able to select a sort order called “Manual”. This allows you to drag cards around to give them an order that makes sense to you. This order is shared within your team and affects also open decks.
To make things easier for your team, you can also pick a default order option for a deck, be it the manual order, grouping by milestone or any other order option we’re offering. This allows you to guide both team members as well as visitors of open decks to see a deck in a way you’d prefer them to see it.
The previous system was based on HTML native drag and drop events but it has proven difficult to work with and the drag and drop experience has become a frequent source of frustration with some of our users.
So we decided to rewrite the underlying architecture from scratch as there hasn’t been a good existing alternative solution out there for our various interaction patterns.
And to stick with our current theme of open development we open sourced the library here.
The result should be a much more stable experience across browsers and systems when dragging cards, decks, milestones and files around.
This release allows you to mark a project of yours as public. You can enter a path name and it’ll be visible for everyone under open.codecks.io/your-name. Go to your project settings to find the corresponding options. You have the option to hide comments for visitors. In any case, visitors will have read-only access only. The deck order for public projects is shared for all team members and can be modified by admins via drag and drop.
We’ve been in touch with some of you already and are excited to present some real-life examples soon! We’re also planning to set up an open development portal under open.codecks.io to allow people browsing Open Decks on Codecks.
- . These can be marked as done via clicking
You’re now able easily embed images into your card content:
!. You now can pick an attachment.
Note that this also works for comments. This will make it a lot more straight forward to communicate about visual aspects of your projects!
$cardidfrom the user’s message.
After working and iterating for a few months, we believe Journeys are now ready to be released!
So what exactly are Journeys you ask? Well, Journeys allow you to define a set of recurring steps for your workflows. Once enabled, you can find a new button in your deck headers (Note: the icon is still based on the working title of this feature “Potion”, we’ll be updating it soon!).
With the new Journey view you’re able to define your Journey steps and assign default properties like owner, deck, effort, etc to them. Once your steps are ready, any card within this deck will have a Start Journey button. This will turn the card into a Hero card and create all the Journey’s steps as sub cards.
The Journey view also allows you to create a template card for the deck. This way every card created within this deck has some default properties and content to allow for more consistency. We’re also thinking of deprecating presets in favor of these template cards. So please let us know if there are some use cases we are missing!
As Journeys are still in beta you need to opt in. Go to your Organisation settings and check for the Hero cards & Journeys section at the bottom.
:behind a word.
This releases features an upgrade from v4.0 to all of today’s sweetness from v13. Including proper support for skin tones, gendered and non-gendered Emojis, as well as the latest additions to the standard 🦦.
The new Emoji set is provided by Twitter’s (Twemoji)[https://twemoji.twitter.com/], so the look has changed a little.
We also had to update our editor’s Emoji picker (initiated by typing
:). Instead of using short codes, we now rely on keywords to find relevant Emojis. This will provide more relevant results when typing
:kiss for example.
Card URLs: a card’s title will now be part of a card’s URL. No worries, old URLs will still work and be redirected to their new form.
Card content: A card’s first line will automatically be styled as a heading if it contains no more than 60 characters.
Card content: improved styling for nested lists, fixed issue with successive card references.
Onboarding: new organizations get a more guided experience when setting up their first projects and decks.
Active conversations view: now considers the current project selection.
Image viewer: now also works for images in the activity stream and card history.
Preset picker: when opening the preset section, the preset selector will automatically be opened and additional space will be provided by scrolling down automatically.
Mini cards: clicking on a tag within a mini card won’t cause weird behavior.
Notifications: the “open all” toggle is now persisted (again).
Time Tracking: stop tracking when archiving a started card. Unarchiving a started card will now lead to a non-started state.
tabto auto-complete a suggestion.
Escnow closes the auto-complete box rather than closing the editor.
1.  do this)
- syntax). Also: you’re now able to check a checkbox by hitting the label next to it as well.