Priorities

Elements Feedback
1

I know Dan only wanted ONE thing to add to Elements, so I’m not going to pollute that thread with a list. However, I’ve been working on my own personal delivery list for things I need to do before delivering a number of projects in the next month or two, and this led me to contemplate and prioritize what things in Elements would help me hit the Web project deadlines.

In absolute order of priority:

  1. The fixing and extension of the Typography component. Specifically, lists, but there were other things demonstrated originally (e.g. embedded images) that would be useful, as well. Typography really needs to anchor a full article, if necessary, not just a block of text.
  2. A List component. This may seem redundant with the first, but Typography only needs a solid basic list ability. If you need elaborate lists with more than basic bullets or numbers, then a solid List-oriented component would really be a better choice and highly welcome.
  3. Completion (or perhaps just testing and documentation) of the remaining demonstrated CMS features.
  4. 404 page creation with proper publishing directly supported.
  5. The CMS has some bugs that need fixing. I can get around most of them, which is why this isn’t higher on the priority list.
  6. Completion of the user documentation for where we are after we hit #4 on my list. Again, I can get around this, so it’s a lower priority.
  7. Opening the store to developers. This would likely prove to be the best way to handle my remaining priorities for Elements as it is currently. Like others, I’m highly interested in some of the things that developers-to-be have been hinting at providing.
  8. Any polish that can be added to the existing components and features in Elements.

That’s really it, and the order I’d want Realmac to tackle things. I’m confident I can deliver final projects once all the above have been dealt with. In fact, I could probably do that once #1 and #3 have been done. Thing is, it’s fun and exciting to work within Elements at it exists today, but I’m avoiding site delivery because the above haven’t been addressed yet. I could work around everything, of course, but that just means building out in a kludgy way I’d have to re-address later.