@Pealco I already write all of my markdown in MACDOWN app, plus much of the content in my existing websites is written in markdown so some of these steps have already been covered. But thanks for the feedback I will look into converting the markdown to HTML.
But it seems it would be SO much easier to just have a markdown bric, especially if It supported some of the features supported by other markdown stacks I have used in Rapidweaver where a markdown file can be used to populate the stack. This effectively allows me to modify the content without having to touch anything in the site as I just edit the file and then upload the changes to the site and it shows up with the changes.
I will try out your idea to see how it works as it would save me a huge amount of time seeing as I already have most of my textual content in markdown format, thanks!
Hey bill, you’ve had a while to make this, you could have created this Bric last year (all the functionality existed then) so I’m afraid you snooze you loose.
Apple make a number of free and paid apps for their products, it doesn’t stop others creating similar (better/worse) alternatives.
And to be honest, I’ve been dying to build with the API. I’ve made close to 20 new Brics for the store to help kick start it’s launch.
Well basic depends on the users skill set and knowledge of css. To you I’m sure it’s a basic css hover, but to many others, the knowledge to do this would be on the more advanced side of things.
Value comes from the fact, this Bric makes the task of adding this type of effect very fast and easily repeatable with a few clicks.
Fun thread, …and yes I have the same bric one my board
@Bill, think big picture here. Now that @Norm is building brics using the API that means API development is going to skyrocket! That will ultimately be better for us. We may even get a release candidate much sooner. Right now the api is still in alpha!
My plan was (and still is). Wait till the api is out of alpha to invest any more time than I already do. By that time Norm will have full-filled his promise of simple brics.
Just food for thought… If you rely long term on an alpha product you’ll need to be very flexible and thick-skinned. So much can change that will require you to make adjustments on the fly, including product strategy.
Finally, I hope this doesn’t mean that anyone thinks if they build a bric first then others can’t build it because that’s a bad assumption. Especially if you’re using an open source library. Someone might may prefer my file size, or custom styles or my support offerings. Seek to deliver on those things and you’ll most likely be okay.
Im hoping to have the Blocs API out of alpha and into beta very soon. You’re absolutely right. Now I have time to build with it, Im able to fill in the blanks.
I feel you may have slightly taken my singular use of the word ‘basic’ out of context with your response. It was in no way diminishing your forthcoming offerings, instead merely emphasizing towards developers given the entirety of my response towards the subject matter.
I trust the Blocs Store will offer definitive value with both free and paid items allowing additional features to users through ease of use. Helping to allow users easy implementation of additional features both basic and advanced, free and paid, along with competitive alternatives. All advancing the cause for Blocs and its users.
This was discussed in that previous thread also. It appears the fun it just now about to begin.
Yeah the Store is a custom theme running on WP, this platform made sense as its easier to maintain for this type of setup, static would take too long to maintain and manage.
But I’ll let you into a little secret. The version of Blocs that runs on my Mac exports to Wordpress Themes…
