Ahh, with 1751 commits since it started, it’s clearly a decision that was made a long time ago.
When I read:
Specifically chose Vue because of the ease of use, learning curve and smoother transition from Blaze (see template interpolation and mustache syntax) - @d3vild06
I thought it was a recent discussion. No worries.
On a separate note:
While you’re doing a walkthrough of the project structure, can you add a map of the file-tree to the readme so that it’s clear where the code should live?
Here’s your current directory structure to get you started:
|-.meteor
|-server
| |-home
| |-comments
| |-twitter
| |-migrations
| |-messages
| |-app_stats
| |-hangouts
| |-discussion_responses
| |-seeder
| |-discussions
| |-resources
| |-admin
| |-learnings
| |-conversations
| |-cron_job
| |-users
| |-availability
| |-activities
| |-slack
| |-seo
| |-study_groups
| |-archived_users
| |-notifications
| |-email
|-imports
| |-ui
| | |-components
| | |-pages
| | | |-users
| |-libs
| | |-server
| | | |-cb_mailer
| | | |-user
| | | |-cron
| |-api
| | |-unsubscribe_links
| | | |-server
| |-startup
| | |-server
| |-data
|-.deploy
|-public
| |-images
|-private
| |-templates
| | |-seo
| | |-email
|-lib
|-i18n
|-client
| |-css
| |-compatibilities
| | |-timepicker
| | |-select2
| |-libs
| |-layouts
| |-templates
| | |-settings
| | |-home
| | |-comments
| | |-inbox
| | |-resources
| | |-other
| | |-admin
| | | |-landing
| | | |-inc
| | | |-notification
| | | | |-inc
| | | |-user
| | | |-dashboard
| | | |-report
| | |-hangout
| | |-status
| | |-profile
| | | |-profile-learnings
| | | |-profile-hangouts-joined
| | | |-profile-edit
| | |-availability
| | |-usr-notification
| | |-members
| | |-nav
| | |-discussion
| | |-study_groups
Which you can get with: find . -type d | sed -e "s/[^-][^\/]*\// |/g" -e "s/|\([^ ]\)/|-\1/"