I'm going to learn the language Markdown to quickly and easily write articles for my website under Wordpress.
To do this, I installed under the Sublime Text 2 plugin Markdown Editing. All delivered normally. Then I create a new document in the editor and assign it a syntax Markdown.
But what to do next? How should I save this file? What do I need to compile the file from the markdown in html? I have not found a good description of how to work with this plugin and how to get ready html-file from the file markup markdown.
Tell me, please.
You may want to install the markdown plugin for Wordpress: http://wordpress.org/plugin...
One possible scenario: You save your blog entries to `.md` files under a folder. To publish an entry, you copy raw markdown content of it to the wordpress. That wordpress plugin will automatically convert it to html for you. (P.S. I haven't used the plugin before)
You may want to install markdown plugin for Wordpress: http://wordpress.org/plugin...
One possible scenario: You save your blog entries to `.md` files under a folder. To publish an entry, you copy raw markdown content of it to the wordpress. That wordpress plugin will automatically convert it to html for you. (P.S. I haven't use the plugin before)
I hope I don't ask something obvious, and I also hope you don't mind 'support' questions here, but here goes...
Is there a way to *not* set the color scheme in the package settings?
Due to the hierarchy of setting files in Sublime, the color scheme for my markdown files now get chosen via Markdown.sublime-settings, through the default or user version. I would love to just use the color scheme in my global sublime preference file (I use camaleon to cycle through a few themes/schemes). But I can't reset the colorscheme setting in the Markdown.sublime-settings file. I tried to set it to 'null', or keep it empty, but that doesn't work. Is there a way around this? I used to just edit the non-user file, but Sublime 3 doesn't allow that anymore.
Another thing: I tried and tried, but I can't seem to get Shift+alt+g to work for finding reference links withouth a defined link.
I'm using the newest OS X and Sublime dev build.
What benefit would it bring to other developers to join your package though?
Surely it is just going to result in them receiving less credit for their work than if they published their own package.
Developing a parser at this level is something that could easily be accomplished by a single developer who could just clone all features on the market.
All md plugins in the market are trying to solve the very same
problems. Because they are based on the native ST md plugin. So they
have the same potential bugs. Developing and _maintaining_ a syntax file
is not as easy as you imagine (or maybe you are working on one?). When
you want to fix something, you proably break some other thing. Just go
and see open issues of those plugins.
We only invite people. It
is up to them to join or not. Personally, me and Brett don't care about
credits. Still, we have a credits part in the README for that stuff. On the other hand,
there is an organization now. And MarkdownEditing is becoming more
popular day by day. Probably, in the next months, being a push access
user in this organization will be more valuable credit than being the
owner of another plugin. Well, it that guy cares about this.
We just want to bring Markdown to more people. That's the OSS spirit.
Thanks for the feedback.