Hi @alberto and @matthias - I wanted to start a task to discuss how EdgeRyders could be integrated with the unMonastery website. The way I see it at the moment is that individual projects have a landing page on the unMon website, which is linked to individuals and challenges. Each project has a short description a video and associated networks (i.e Twitter, Github, etc).
What I want to be able to create is a sort of widget, that principally has a link to where the project is posted on EdgeRyders, potentially a project page of it’s own on the site, a simple link could suffice but ideally I’d like it if we could automate (with RSS or JSON) links related to the conversation around the project - which updates automatically.
So my first question, what sort of support do we currently have for RSS or JSON feeds, and what could I do to help with this. More generally it would be really great if going forward people could put a kind of EdgeRyder badge on their own website (similar to the twitter one: Overview | Docs | Twitter Developer Platform - so to create multiple portals/points of entry for the platform.
Matt knows more than me, but I do know we have installed Views JSON. This exports any Drupal view in JSON format: I use it for my network stuff. Essentially, you decide what data you want to read, build a view and tell Drupal to channel it out in JSON. In Drupal parlance a view is a stored database query which is invoked every time the website needs it. For example, when you look up the projects directory, Drupal runs one such query that tells the database to look for nodes of type group, retrieve their title and logo, order them from newest to oldest and print the first 50 on the screen. Then, from the receiving end, you can call this JSON-ized view at any time, like
thanks [Alberto]! i’ll take a look at what RDF we can get with those views
we start using Markdown for all the content, trello, github and many other services also use it so one needs to know how to use it anyhow… for drupal i’ve found this module: https://drupal.org/project/markdown
[Matthias] can you please enable markdown? [Ben] can confirm that it makes writing very nice and even [Bembo] picked it up in just 30min or so…
Current WYSIWIG I find super clunky, breaking browser spell checker and in general discuraging from writing here. I understand that those who like it can still use it but those of us who prefer markdown could enjoy much smoother experience.
I totally agree that I need to do sth. about the current editor soon (or even exchange it), it’s really not great. It should be restricted to just the relevant options and styles, styles should be the same as in the frontend, ok spell checking would be nice, and clearly visible keyboard shortcus for all the stuff.
Markdown is nice when you build your whole website around it and have a nice editor with live preview, such as on StackExchange sites. I admit that I like it there. But even there: I often run into problems that I guess are “too nerdy” for most users. Try a code section inside a list (yep, eight spaces). Try a link like [source] – it’s [source], done wrong even by the StackExchange editor. But I guess I dislike mostly to deal with all the little details that adding Markdown cleanly would entail: getting the conversion to e-mail format working, and what happens when I need to run drupal_migrate again one day and my source formats are mixed, and so on.
So I propose to give the rich text editor an overhaul first (needs to be done anyway) and then you tell me what you think. Works?
@Matthias can you please fix ASAP spell checker? If enabling markdown fixes it, for me even better, if you can fix this WYSIWYG then we can take some more time to discuss need for markdow. I guess most people here don’t speak english natively and enjoy when computer correct our typos
Just fixed the browser-native spell checkers to work again. Tested with newest versions of Chromium and Firefox.
The solution involved working around CKEditor bugs / quirks (effectively use a combination of this and this answer on StackOverflow).
Re. markdown I’m sorry but I don’t think we can get that done any time soon (except somebody wants to take it on, and even then we have to see if a clean integration is possible at all). For me, the choice to make is between overhauling CKEditor and adding markdown to a broken CKEditor, and that’s not a difficult one
Short note: Except for defining a proper set of styles in the “Styles” dropdown and some wording, the CKEditor rich text editor overhaul is done now. Shoud be much more tidy now. There is still a HTML source mode (now as a link below the editor) for power users who need more than the buttons that remain.
I agree with Pavlik here, I think Markdown really is “everywhere” ( trello, github, etc ) and it is quite easy ( especially if you have some editor support, as it github )
But other than that “doing something” with the editor is something to be considered, as we have talked about a while ago, but I think it’s more about adding some ‘usual’ options and removing some options like ‘styles’ in this editor ( very limited and a bit funny, “Blue Title”, “Red Title”, etc ) , spell check would be useful too.
Another reason for supporing Mardown relates to advantages of Decoupled CMS. Currently we force everyone to use a particular UI to interact with this dataspace, I would compare it to forcing someone to use Thunderbird to send an email to our mailing list.
For well defined interactions and types of resources, comment, event, q/a etc. one could use UI of ones own choice and still interact with the same dataspace. Markdown gives interesting start, since trello, github etc. support it we could already experiment with using current APIs so that everyone can use UI which fits ones needs!
