Perhaps a different perspective is how many people in 2000+ would use CMS? How many of these would use a blog? For those hobbyists there is not necessarily a need to use CMS, some may want a blog and others don’t. So maybe the views are dictated by this not markdown discussion?
perhaps, but only 14 voted for markdown, less than 1%
the current version of CMS is not that difficult, it is not fully featured yet, so limited, but you can use and create some good stuff - depends how much is added to the current version
Both CMS and markdown require a learning curve for most users, just use for a one off website is not worth it or required I would imagine,
I think a lot of users require time to understand exactly what Elements can do out the box
watching the forum what percentage users actually ask questions or do they go direct (can they)
what happened to the option to ask for components and vote on them
I can only see what’s on the forum, would I base my business on less than 1%, but again businesses differ same as thoughts, I only comment on the forum info,
my thoughts only, should not be taken seriously
another vote for markdown just added
Again, saying that only 1% voted for Markdown is a misrepresentation. 14 of 101, or 13.86% of the people that saw the message voted for Markdown. In statistics you use the sample (101) to predict the population (2000). Technically, for a 95% confidence level, we’d need to sample 323 Elements users, so the confidence level is somewhat low from the sample, which is why I used 10-20%. (I have a PhD minor in Statistics, by the way.)
The comment that both the CMS and Markdown require a learning curve, while basically true, I think is irrelevant. There’s more learning curve in just the basics of Elements that’s tougher for people than understanding basic Markdown is. When John Gruber first proposed Markdown, there was a lot of pushback on “not another thing to learn,” but that definitely hasn’t stopped it from becoming near ubiquitous in the notetaking and Web site world. Markdown is a simple way to separate data (text) from design (formatting). And that’s clearly the trend these days (e.g. JSON and other “don’t have design embedded” formats).
I think I understand your point, and if I do, I agree with it. If I don’t understand, I disagree ;~).
Absolute v relative - interest and knowledge
I did say just able to understand Elements out of the box was more of an issue
Just this extra discussion has greater another 36 views, or would that have happened anyway, only generated one more vote,
Data can be manipulated to give a different output, just play with a percentage of a percentage without introducing no user interest / knowledge of the subject
140 views
39 more views 2 votes for 1 for not
the percentage is worse??
Thom what I was trying to say if I am a hobbyist doing one organisation/church/business etc. or even a couple, I do all the web work on my own and “own” my sites, no one else has any input except through me - so therefore they don not need CMS. Now some of these people might want to add a blog so will need to get into blog side. Therefore only a percentage need CMS and only a percentage of those use a blog. I hope I’ve explained myself?
It’s being implemented anyway not sure why the vote
Think this more about markdown in Elements and the option to produce markdown manually or perhaps paste in markdown? If you know markdown it can be a lot more productive to produce content
Very useful in CMS as well if you need that amount of layout
I expect a lot of website are parallel in setup to yours so I agree with you
A couple more woken up and voted
Still not 1%
no more comments from me
Yes, that’s what I thought you were saying.
1 Like
The .htaccess editor like the one in Classic isn’t really necessary for Elements.
To create an .htaccess file in Elements, you just need to create it directly in Elements and then edit it however you like.
That’s essentially all the editor does in Classic as well. Or is there something specific you feel is missing?
1 Like
Also, we are forgetting how much of the population actually doesn’t vote.
I hadn’t because this was already being developed and not far from completion, so what’s the point. I will definitely use this feature and as it certainly doesn’t sound like an either or decision: typography or markdown, it sounds like a win win. We get both.
Thank you Dan and crew for putting in the work and continually improving the product.
https://forums.realmacsoftware.com/t/dedicated-markdown-component/53557/29?u=upssjw
I did mention why was there a vote
Perhaps was it should we carryon developing
Again my point was only a percentage of users view the forums, either they are content with the product, not using it or struggling or perhaps no knowledge of markdown (not want to learn)
You can use data in different ways
I’m glad you will use the component, this was not about not having a markdown component, more about other want/need components functionality
I also mentioned in this thread - Not saying this does not move Elements forward and attract new customers
I am an advocate for Elements by the way, a big advocate
If you scan the entire Elements forum and look at the the hits you will see a pattern, what attracts most views, again these could be non users
Again data can be interpreted in many ways
Good to discuss, and credit to Realmac for the interaction over the last couple of years and continuous development
Actually reached 21 yes votes and almost 200 views in this thread
I think the more people read the threads the more they may vote or gain knowledge
Bye the way I have never used markdown, not needed to, not that I have not checked out how to use markdown. Years ago. But I doubt I will use in Elements again no issues with markdown component
since tom, according to dan, is already working on the markdown component, we’ll most likely get it as well.
maybe even as an optional “paid” component… for a small fee.
We were just putting it out here for feedback really 
Its been requested for quite awhile, especially those coming from the Classic/Stacks universe.
It’ll be shipping soon 
2 Likes
I voted in the other poll but not this one as I would vote no and I don’t want to tell RMS what they should not spend their efforts on.
Not interested in blogging so have not explored what CMS is all about and while I see the term Markdown quite a bit I have made no effort to try and understand what it is as I don’t need it. I think.
2 Likes
@dan just a couple of questions
The block of text etc in the markdown component, can you interact normally adjust etc from the normal editor or does the content have to be always edited in that component
Also will there be the ability to adjust for responsive across screen sizes or is the text fixed
I am coming to this thread a bit late, but I use Markdown a lot on my Classic/Stacks site, as it is an info-heavy site, and it is far faster for me to type and set in Markdown than to struggle with styled text. Frankly, I can’t remember the last time that I used styled text, and it is probably the one thing that has stopped me from converting the site to Elements.
2 Likes