How Do I/You Develop a/for TXP Site?

anoke · 2007-07-09 06:12:03

Hey. Care people sharing some of their tips’n‘practices?

I don’t mean generic web-design/planning but how do you keep one devel/beta site at first and then at some point move it to production? Do you use dummy content (if yes, how do you create it and how much)? Where do you create your plugins? How do you treat/versioning different forms and pages? Naming schemes? How do you tracktrack all that? I don’t want to question the role of planning, but sometimes plans and goals are easier to name when the journey is already done..

That sort of questions. (:

Myself I keep two sites, one in production site and other on laptop/desktop/spare server. It sounds difficult, but after first pages and forms it just is more about micromanagement. (I used to love SimCity, no problem there :) It’s this form jungle.

thanks,

squaredeye · 2007-07-09 13:23:42

Anoke,
Those are good questions:
I have two ways (the way I do it, and the way I want to start doing it).

The way I do it

I code the design with xhtml/CSS
I set up a local TXP install
I copy/paste the HTML into a local install
I start a css folder with css/images/ within
I write the appropriate article/navigation tags throughout the site utilizing as many misc forms for global content as is necessary.
I tweak the design if necessary
I dump the sql
I create the necessary db on the live server (for my client)
I create a subdomain for their site for testing
I import the dump
I usually have to change the password on the new install using a mysql query. This one is still a mystery to me. Probably has to do with my local install.
Then I test for usability
Then I switch it to the Top level domain when its ready to rumble

The way I’d like to do it

Keep snippets of useful XHTML, CSS, JS, and TXP available for cut/paste rather than inventing the wheel everytime. (I’m starting a collection of design elements in the same way and its been very useful)
Keep sql dumps and all files of all my previous sites, so that I can replicate functionality where necessary and helpful and more expedient.
Keep a default sql dump of my own that is a good starting place for any site. Perhaps Even the necessary files too?
Perhaps keep a series of sql dumps that are set up for different kinds of sites?

Those are the things I’m thinking about lately.

Matthew

Last edited by ma_smith (2007-07-09 13:25:08)

ellen · 2007-07-23 10:12:34

ma_smith schrieb:

I create a subdomain for their site for testing
I import the dump
I usually have to change the password on the new install using a mysql query. This one is still a mystery to me. Probably has to do with my local install.
Then I test for usability
Then I switch it to the Top level domain when its ready to rumble

Hello Matthew,

When you move your installation to the live server and create a subdomain for testing do you install TXP once and change the subdomains path to point to /textpattern/ or do you install it twice in two different directories?

How do you manage exactly to change the password on the new install?

I’m using MAMP on a OS X to develop locally and still haven’t found an efficient and always-working way to move my sites to the server.

squaredeye · 2007-07-23 13:20:58

Ellen,
I am more likely to minimize changes by simply changing the paths rather than installing twice.
For the password change, search “password mysql” on the texpattern resources site. You’ll find the sql query you need to run.

Matthew

Textpattern CMS

Textpattern CMS support forum

#1 2007-07-09 06:12:03

How Do I/You Develop a/for TXP Site?

#2 2007-07-09 13:23:42

Re: How Do I/You Develop a/for TXP Site?

#3 2007-07-23 10:12:34

Re: How Do I/You Develop a/for TXP Site?

#4 2007-07-23 13:20:58

Re: How Do I/You Develop a/for TXP Site?

Board footer