Tweets

Justin Jackson
Justin Jackson@mijustin
Replying to @mijustin
Our instinct is to target people who are "starting out."

But it's actually better to target folks who have already started. ⚡️
⟳ 2 ♡ 12
Justin Jackson
Justin Jackson@mijustin
Targeting absolute beginners is really tough.

It's more effective to help someone who's already "pretty good" get better.
⟳ 4 ♡ 45
Justin Jackson
Justin Jackson@mijustin
Replying to @cezarfloroiu
@cezarfloroiu That's the only way for me to deliver updates to you (and for you to be able to re-download it easily)
⟳ 0 ♡ 0
Justin Jackson
Justin Jackson@mijustin
@marcusthehirsch @DiceForBrains To increase word of mouth, the podcast needs to ask listeners to share the show with their friends

(Plus rate and review in iTunes)
⟳ 0 ♡ 1
Justin Jackson
Justin Jackson@mijustin
RT
RT @hofmannsven: This is crazy! I can't believe I've won a copy of the book Marketing for Developers by @mijustin! Thank you so much @marke
⟳ 0 ♡ 0
Justin Jackson
Justin Jackson@mijustin
Replying to @abigailotwell
@abigailotwell YESSSSSS!!!!

I miss hanging out with everybody. We should all just go to NYC for fun. Skip the conference and go straight to the pubs! 😜
⟳ 0 ♡ 2
Justin Jackson
Justin Jackson@mijustin
Tip: going to events can help you get new customers!

I get tons of messages from @marketingdevs customers like this one. 👌 (thanx #laracon)
⟳ 1 ♡ 10
Justin Jackson
Justin Jackson@mijustin
Editing old writing is so much like refactoring old code.

Making a paragraph better (more efficient, more readable) feels *so* good.
⟳ 0 ♡ 13
Justin Jackson
Justin Jackson@mijustin
RT
RT @metakermit: I can really recommend Justin's book 📕 and the accompanying course 📺. Great materials for learning about marketing and buil…
⟳ 0 ♡ 0
Justin Jackson
Justin Jackson@mijustin
My book, @marketingdevs, is being re-released today.

It covers some of the hardest topics indie developers face (including sales!)
⟳ 13 ♡ 21
Justin Jackson
Justin Jackson@mijustin
Replying to @boaticus
@boaticus @citadelgrad BTW - there's not a single option on this list that publishes directly to GitHub Pages + supports flat-files

(two of my requirements)
⟳ 0 ♡ 1
Justin Jackson
Justin Jackson@mijustin
Replying to @boaticus
@boaticus @citadelgrad On one side you have Jekyll (command-line, technical).

On the other you have web apps (WP, Medium).

Is there opportunity in the middle?
⟳ 0 ♡ 1
Justin Jackson
Justin Jackson@mijustin
Replying to @boaticus
@boaticus @citadelgrad However... since yesterday 41 people say they agree with me (and about a handful more in my DMs).

I'm seeing a gap in the market.
⟳ 0 ♡ 1
Justin Jackson
Justin Jackson@mijustin
Replying to @boaticus
@boaticus @citadelgrad I recognize there are a *few* solutions (I'm planning on trying Marsedit).

I also recognize this might only be my problem.
⟳ 0 ♡ 2
Justin Jackson
Justin Jackson@mijustin
Replying to @joeworkman
@joeworkman 1. Which apps are you talking about?

2. I don't want to publish to WordPress or Medium. I want static files (speed, portability, etc)
⟳ 0 ♡ 1
Justin Jackson
Justin Jackson@mijustin
Replying to @GentScientist
@GentScientist I already pay for GitHub (and so I have versioning, scalability, web hosting, CDN).

I just need the desktop publishing piece. ;)
⟳ 0 ♡ 0
Justin Jackson
Justin Jackson@mijustin
@xtraordinarylab @kylefox YES. But there's no reason a desktop client couldn't manage all that, locally, and then just push the result up to the server.
⟳ 0 ♡ 1
Justin Jackson
Justin Jackson@mijustin
Replying to @kelkes
@kelkes There are lots of techie folks like me that don't want to use the command line.

Why do you think GitHub made their desktop app? (I use it).
⟳ 0 ♡ 1
Justin Jackson
Justin Jackson@mijustin
Replying to @mijustin
Most bloggers don't want to use the command line!

(BTW - installing stuff via terminal is way more finicky than most of you are admitting)
⟳ 1 ♡ 13
Justin Jackson
Justin Jackson@mijustin
Replying to @GentScientist
@GentScientist Most of my peers (and I) use WPengine because it can handle huge traffic spikes, WP security, backups etc..

But that costs $100 / month.
⟳ 0 ♡ 1
Justin Jackson
Justin Jackson@mijustin
Replying to @kelkes
@kelkes I've tried a bunch.

But as soon as I need to get in the command line it's already done for me.

I don't want to use the command line.
⟳ 0 ♡ 0
Justin Jackson
Justin Jackson@mijustin
@xtraordinarylab @kylefox I suck at HTML, but I can easily create a static file that embeds email forms, podcast player, etc...

The challenge is the CMS piece.
⟳ 0 ♡ 0
Justin Jackson
Justin Jackson@mijustin
Replying to @mijustin
SERIOUSLY. Read the Jekyll troubleshooting section:
#installation-problems" rel="noopener noreferrer">https://jekyllrb.com/docs/troubleshooting/#installation-problems
Jekyll's fine for some people.
But it's not a solution for most.
⟳ 0 ♡ 4
Justin Jackson
Justin Jackson@mijustin
RT
RT @kylefox: @mijustin They’re essentially the same thing, it’s just that one is going to a private inbox and one is going on a public serv…
⟳ 0 ♡ 0
Justin Jackson
Justin Jackson@mijustin
RT
RT @kylefox: @mijustin Publishing a blog post really shouldn’t be any more complicated than sending an email.
⟳ 0 ♡ 0
Justin Jackson
Justin Jackson@mijustin
Replying to @mijustin
Jekyll isn't the answer for 90% of bloggers.

(If your solution includes a troubleshooting section that looks like this, it's too complex)
⟳ 1 ♡ 12
Justin Jackson
Justin Jackson@mijustin
Replying to @mijustin
A blog shouldn't be technical to set up and maintain.

No need for the command line, installing gems, or a local server.
⟳ 0 ♡ 1
Justin Jackson
Justin Jackson@mijustin
Replying to @mijustin
A blog should be easy to move from one provider to the next.

You should be able to choose GitHub Pages, Digital Ocean, Dropbox, etc...
⟳ 0 ♡ 0
Justin Jackson
Justin Jackson@mijustin
Replying to @mijustin
A blog shouldn't just exist until you die (when your hosting + domain expires).

If your words are valuable, they should be stored locally.
⟳ 0 ♡ 4
Justin Jackson
Justin Jackson@mijustin
Replying to @mijustin
A blog should be BLAZING fast for visitors.

It should easily scale up when traffic increases.

(Without the need for expensive hosting)
⟳ 0 ♡ 3
Justin Jackson
Justin Jackson@mijustin
Replying to @mijustin
Writing a blog post should be dead simple:

1. Open up editor.
2. Write.
3. Publish

(No log in, no dashboard, no waiting for web to load)
⟳ 2 ♡ 6
Justin Jackson
Justin Jackson@mijustin
Replying to @ChaseFlorell
@ChaseFlorell We could use Jekyll in the background.

I don't care as much about *how* we build it.

More interested in solving the struggle.
⟳ 0 ♡ 0
Justin Jackson
Justin Jackson@mijustin
Replying to @ChaseFlorell
@ChaseFlorell - Jekyll is way too complicated for most people
- I'm talking about hosting on GitHub pages
- you still need to generate blog feed & nav
⟳ 0 ♡ 0
Justin Jackson
Justin Jackson@mijustin
Replying to @mbuckbee
@mbuckbee Yes, everyone has funny workarounds. ;)

I don't want to run a CMS server (local or remote).
⟳ 0 ♡ 0