search

inboundnow / inbound-pro

Inbound Pro Plugin for WordPress - Landing Page Framework, Calls to Action Framework, Visitor Analytics & List Segmentation, Email Campaigns & Marketing Automation
https://www.inboundnow.com
31 stars 17 forks source link

Private repo cleaning #108

Closed DavidWells closed 9 years ago

DavidWells commented 9 years ago

Hey Hudson,

I'm revamping our /templating setup so we can work in github repos for quicker pro template generation. This means we will need 3 free private (we have 1 already) repo slots for /lp, /cta and /email

This means we can clone down each template directory in the correct /wp-uploads/PLUGIN-Name/templates folder and have 100% up to date templates no matter what

Do we need https://github.com/inboundnow/QA-Tests repo?

Can we move https://github.com/inboundnow/inbound-google-analytics to private bitbucket?

Any other repos we can migrate to bitbucket for now to make room?

atwellpub commented 9 years ago

The QA repo can go. Inbound Google Analytics is now on BitBucket too: https://bitbucket.org/inboundnow/inbound-google-analytics/src

But at the end of the day we still need 1 repo per template for file serving. I have all non core landing page templates & call to action templates individualy listed on BitBucket, and files are being server from there too.

DavidWells commented 9 years ago

The idea is to have all landing page templates in a single repo then push changes directly up to the live versions on demo.inboundnow.com and then demo.inboundnow.com serving the zip to clients.

If we have an individual repo for every template is it going to slow down updates on them and be much harder to manage as the template base grows ( which I'm expecting to happen with this slick new setup )

The shared repo also serves to speed up dev of new templates because they will share a master gulp file for automatic css/js minifications, automatic thumbnail creation, etc.

The template builder tool I built will also probably live in here to speed up stuff even more (maybe not though need to think on the best scenario for that)

On Sep 3, 2015, at 10:07 AM, Hudson Atwell notifications@github.com wrote:

The QA repo can go. Inbound Google Analytics is now on BitBucket too: https://bitbucket.org/inboundnow/inbound-google-analytics/src

But at the end of the day we still need 1 repo per template for file serving. I have all non core landing page templates & call to action templates individualy listed on BitBucket, and files are being server from there too.

— Reply to this email directly or view it on GitHub.

DavidWells commented 9 years ago

Ok inbound-google-analytics is deleted. Templates repo is coming tomorrow with some better build processes

DavidWells commented 9 years ago

QA-tests set to public