I’m building a base Rails 5 API (postgres) with no sprockets/turbolinks/action cable, using webpack to build/load es6 js files and scss css files. And the framework will be Vue.js. There will probably be no css framework, and unless you are against it I will use flexbox.
I’ve decided webpack over rollup quite a bit arbitrary, but I’ve found a lot more documentation on webpack than on rollup.
Once I’ve finished the skeleton, I will submit it for review.
Maybe we could hook the submission process up with user API keys?
Site admin enters directory.discourse.org/submit
Site admin opts in to the directory via the user API
The new site enters our queue for review.
That way, as far as I can tell, the only way to spam our queue would be to generate a great number of Discourse instances, which is…, not very cost efficient spamming.
Right. About that, what do you think about a more tag-like system? I often find myself limited by a single category. Take http://forum.gethopscotch.com/ for instance. I think this community is equal parts “Online Education” and “Software Development”, so I’d like it to appear in both.
The tougher question then is how we should do featured listings. If it’s not too hard to do, I’d prefer to select featured items per tag and not globally, i.e. Hopscotch could be a featured community in “Online Education”, but a regular listing in “Software Development”.
The taxonomy will certainly change over time, but here’s something to start with:
Waiting for comments, do not hesitate, I want to learn. Also tell me if you have any issue starting the apps.
The skeleton is mostly focused on the js side of the App, the rails side is easier for me and shouldn’t have any surprise (active_model_serializer/rspec…) I will work on it later, once js is OK.
I tried to follow what you use on Discourse, but chose Karma as it’s recommended with webpack.
I’m a little puzzled by the goal and target audience fo this project - and have been asking myself who’d be using such a directory:
As a potential ‘external’ community member (let say, someone who’s interested in cats), I don’t care about the technology a site is running on. An index by a software provider would not be a natural starting point for me to find a place to join.
As a Discourse site owner, I’d be interested in finding inspiration for site design, structure or technology (plugins?), and to learn about how the steps others take to increase community engagement. I would not search based on the type of community, but on technical and community management aspects.
As the Discourse team, I might be interested in having strong showcase of my product. This is already covered on the customers page.
As this is a project by the Discourse team, I’m guessing the focus should be on helping their own community of site owners and customers, therefore focusing on site owners ? The examples so far seem to focus more on external community members though.