Posts
Search Results
Site and Policy » Markdown Migration » Post 14
Luna 
Administrator
Devops
Welcome to phase 2, actual database changes are being made. Currently you’ll still write Textile, but it’ll now be written as Markdown to the database and rendered directly, without the conversion layer in-between.
Site and Policy » Markdown Migration » Post 13
Luna
Administrator
Devops
@zBL4CKGH0STz
Oh sorry about that, it was breaking the formatting a bit and I was debugging if it was just a weird quirk or actual parser bug.
Oh sorry about that, it was breaking the formatting a bit and I was debugging if it was just a weird quirk or actual parser bug.
Site and Policy » Markdown Migration » Post 12
zBL4CKGH0STz 
Why my comment was edited?
Ъ¡ɢധ¡ɢ
Finally! I don’t need to add a link twice
@Teaspoon
I think I get it
Why my comment was edited?
Site and Policy » Markdown Migration » Post 9
Anonymous #0A28
stop
Site and Policy » Markdown Migration » Post 7
Radomila Radon 
✾
Yeahhhhhh, let’s gooooooo!
-Airboarder from Rhythm Heaven
%I made a test text from Luna’s format :P%
%I made a test text from Luna’s format :P%
Site and Policy » Markdown Migration » Post 5
Teaspoon 
Change in how you can write stuff like bolds, italics, or links. The helper buttons will work the same if you don’t really care about the exact syntax, which will be closer to that used on other sites and less of a custom version of a somewhat obscure syntax.
Moderator
still using a ps/2 kb
I still didn’t understand what is this, but I’m sure this will be great change
Change in how you can write stuff like bolds, italics, or links. The helper buttons will work the same if you don’t really care about the exact syntax, which will be closer to that used on other sites and less of a custom version of a somewhat obscure syntax.
Site and Policy » Markdown Migration » Topic Opener
Luna
Administrator
Devops
Markdown
Greetings and welcome to one of the most exciting changes to the site yet: Markdown
We are replacing outdated and not very feature-rich text processing engine which we have been using so far, Textile, with something more widely used across the internet: Markdown.
Sounds cool but what does it do?
Markdown, just like Textile, is a text processing engine. It’s powering every single user interactable text that you see on the site. Everything from comments and forum posts to more obscure things like tag descriptions and report text are processed via these text processing engines.
Why the change?
Textile was getting fairly outdated and with other resources, such as Discord, Telegram, Slack, Github and many others using Markdown, it’s been an obvious choice for us. With most of the internet already using Markdown to format its content, most people would be familiar with it to some degree. This familiarity, safety, user-friendliness and the fact that it has less bugs that our Textile parser, were the driving force behind this change.
What flavor of Markdown does Furbooru use?
We’re using Github-Flavored Markdown with our own modifications to support syntax commonly used on our site. Of notable things that we have implemented into our version of CommonMark we should note the following:
- Subscript
- Spoilers
- Strikethrough
- Underline
- >>image syntax
- Blockquotes that don’t require lots of empty lines and require a space after them
How is it implemented?
We have forked and modified comrak to achieve our features. The Elixir code of the site compiles and plugs the Rust code to render Markdown.
What now?
We are implementing the change in baby steps. They are as follows:
- Provide initial implementation with Textile->Markdown translation layer
- In this phase, Textile is converted to Markdown and rendered by Markdown.
- No database changes have been made yet. This is purely visual.
- Test to see if there are any translation issues or bugs.
- You can still write textile, but most of Markdown syntax will work as well (it might get interfered with by the conversion layer, though)
- Convert all existing posts and interactions from Textile to Markdown and write changes to database.
- During this phase all new posts created will still be treated like Textile posts, but their Markdown representation will be written to the database.
- Posts will still be rendered by converting from Textile to Markdown
- During this phase, editing old posts will still be done using the Textile syntax.
- Finalize the conversion by removing Textile versions of old posts. Markdown will become the sole markup on the site.
We are currently at phase #3
Q&A
Can I already write Markdown?
Yes, but due to conversion layer in-between you might run into issues where Textile and Markdown syntax collides.
Can I write raw HTML?
No. It will simply be escaped and output as plain text.
OMG I spotted a bug!
Please reply to this thread and tell us about it! We expect things to break and be buggy, this is why we’re hesitant to write anything to the database just yet.
Have fun!
Showing results 1 - 16 of 16 total
Default search
If you do not specify a field to search over, the search engine will search for posts with a body that is similar to the query's word stems. For example, posts containing the words winged humanization, wings, and spread wings would all be found by a search for wing, but sewing would not be.
Allowed fields
| Field Selector | Type | Description | Example |
|---|---|---|---|
author | Literal | Matches the author of this post. Anonymous authors will never match this term. | author:Joey |
body | Full Text | Matches the body of this post. This is the default field. | body:test |
created_at | Date/Time Range | Matches the creation time of this post. | created_at:2015 |
id | Numeric Range | Matches the numeric surrogate key for this post. | id:1000000 |
my | Meta | my:posts matches posts you have posted if you are signed in. | my:posts |
subject | Full Text | Matches the title of the topic. | subject:time wasting thread |
topic_id | Literal | Matches the numeric surrogate key for the topic this post belongs to. | topic_id:7000 |
topic_position | Numeric Range | Matches the offset from the beginning of the topic of this post. Positions begin at 0. | topic_position:0 |
updated_at | Date/Time Range | Matches the creation or last edit time of this post. | updated_at.gte:2 weeks ago |
user_id | Literal | Matches posts with the specified user_id. Anonymous users will never match this term. | user_id:211190 |
forum | Literal | Matches the short name for the forum this post belongs to. | forum:meta |