Skip to content
Project like tasks manager lite
As you have questions, add them to the syllabus doc . Step 1: Choose your Project Build for a problem you want to solve Build to solve a problem for someone else Rebuild an existing in Coda (e.g. Lattice, Range, Asana, Salesforce, etc.) Build for one of the use cases listed here: Now that you have decided which project you will be working on, it’s time to design your doc. Start with the Database Design What data do you need to track? Tasks and sub tasks, just like ms project, easy to edit and fill. Dates of tasks, auto programing but also limit dates to parent start and user selected limits Costs will not be considered How is that data interconnected? One big table should be better to handle, just like in ms project Data can be connected with formulas and filters What schema would be most effective? Then, focus on the User Experience What do people need to do? program times and limits, auto programing considering times and limits add notes and comments to tasks Remember to members and project managers about in progress tasks, missing tasks and weekly summary of incomming dates and project timeline Flow should be mainly about tasks and their times User should be able to easily change dates and move tasks to upper levels or lower levels Now, focus on the User Interface What should it look like? Like a simple table to add tasks As easy as project to add tasks, sub tasks, auto program dates and use limit dates What makes it delightful? Automate summaries, reports, emails Coda doesn’t have this already Finally, create a diagram, flowchart, visual, or other representation to outline your plan.
This link can't be embedded.
Pro Tip: Find a tool for design - Use an app like or for awesome flowcharts. - If you want a word-based outline, no better place than a Coda Doc - Create a “Scratch” page in your doc to put your outline. - Lastly, you can never go wrong with the analog approach: pencil and paper. The time has come to build your doc! Don’t worry about getting it exactly right, just use your design from ‘Step 2’ to build out a good draft. Here are some questions to ask yourself as you build your doc: Is the you originally designed for the most effective for your doc? Are you building it for ? Will it work as well in the future as it does now? Are your delightful? How will interactions differ (Admin, Read-Only, Interact-Only)? How would make your doc better? Have you turned that into a swan?
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (