NoDice

OK, thanks for that reply and the link! I installed PW now and did some tests before reading your reply. What I did was move the whole default folder where I put PW after installation one folder down. The only thing I had to do to make the site links work again was change the url in the .thaccess file RewriteBase line to reflect the move (this was a fix I had to apply in the first place to make the installation work as described by thomasandman here: http://processwire.com/talk/topic/1-what-is-the-admin-login-url/?p=28330). The links were automatically output the right way (root relative) after the move of all files (I E one level was removed from all links when output to HTML as read by the browser compared to when read in their original location). But what I take away from the discussion you linked is that I now may have some problems in my mySQL database where the old links my still be present? Or if no such db-data have been produced yet since I only have the standard installation test pages so far, I may get such problems after a similar move once I have completed my actual site? If so, the find-replace solution would be ok for me (but I had not planned to have to export and import the database since I will be on the same server the whole time). ** Edit ** I exported and searched but there were no traces of link references (from before or after the move) in the exported mysql database file yet as far as I could find.

Actually, I was just wondering this myself as I am just about to install and setup my dev environment. My initial plan was to just make a “test” folder under the main domain on the actual server I will later use for the live site, and use that as my site root. As I will be working from several different client computers, I figured that would be the easiest solution (since it will also continuously expose any problems that might exist in the server environment). I intend to use relative links throughout, in order to not have anything break as I move to the domain root directory. Anything in particular I should think/worry about if I make these choices as far as pw and the futre move to the root is concerned?

Well, after those thoughtful replies, I guess I’ll just have to jump in! And I do understand and see all the upside; what is perhaps a little bit unusual in my case, is that I will probably only be making these two sites, and that there will be no clients. I am making them for my company, and I could be doing all the editing myself. Also, I am not a graphical designer, web designer, coder, photographer, moviemaker, copywriter etc. Yet I will be doing everything on these sites myself, so it will be a massive undertaking for me anyway. So, what I really wanted to make sure of before even starting, was that I would not be prevented from using, say new “CSS3” transitions or such, since the CMS-framework might not support or work with some HTML, JavaScript or CSS-features. That I would not realize down the road that the decision to go with PW would mean I simply could not do something that I otherwise could have, if you will. Thank so much for taking the time to give such great replies – now, wish me luck, I will need it!

Hi! I am a Swede in the process of designing two sites for my company, and I have some grasp of HTML, CSS and Javascript (that I am currently updating since I have not made a site in years). The important part for us as I set out on this project is design and cross platform functionality, so my initial inclination was to just make a site using these basic tools. Of course, as soon as you start thinking of making two sites using the same basic custom design-templates, and also ponder the fact that it would be good if your colleagues could easily make changes additions to sites; you realize content management with some more server side database functionality probably is the way to go from the start. Having researched what product would provide the best tools for someone with a design focus (I really just want to think about how to achieve what I want using HTML/CSS and its new capabilities instead of flash that I used last time around), I landed here. My questions before I decide which way to go (true CMS or not) are the following: • How much extra work/time will I have to put in, as far as understanding and writing php and getting the hang of the PW system, just to be able to create the same responsive designs I would make in HTML/CSS/Javascrip, while also achieving the easiest type of content editing capabilities (in line with what you can get with a CushyCMS type product)? That would be my goal initially, and the upside for me - apart from basic editing that I could get using simpler tools - would be that I could then add more advanced features and CMS functionality down the line if I am already in the right structure. • Is it always possible to “fall back” to regular HTML and CSS for sections that you give up on having management features for? That is, will it be possible to use regular code within this framework if you are willing to forgo the CMS functionality on some pages? I hope that question makes sense, but what I am really asking is if I will be able to fallback to and use any and all designs and functionality that I can achieve with html/css/javascript if I fail to achieve what I want within the PW framework. Hanging around this site and the forums here, I feel like PW is certainly the way to go; but as always, it is a question of whether or not I have the extra time and effort to invest now to get the results I want, and for me, it is very hard to figure out how big that investment would be if I am not after very advanced CMS functionality at this stage. Thanks in advance for any input you may have on this!