-
Posts
4,314 -
Joined
-
Last visited
-
Days Won
80
Everything posted by diogo
-
I bet it's the $pa parameter. You have to replace by the the top level page object. Also, read the comments on the top to know about the other possible parameters.
-
It's a nice project. The website is only for the photography work and the photos are not related with architecture at all. Only nice b/w—hight contrast—almost abstract images. But i won't spoil the fun, you can see it very soon
-
A website for a Swiss architect/photographer, one for a German dementia help association and one for a Portuguese small publisher (the one that published my small book ) All very simple, mainly using the core capabilities of PW.
-
When I open a OGG file in chrome or firefox it plays it in the browser, same happens with MP3 or most video files. If I open a PDF, it is also shown in the browser, same with JPG, PNG, GIF and most surprising of all, it even happens with HTML files!
-
Did you try to open the file url directly? does it work?
-
Pi 2 looks great! This will finally convince me to buy a raspberry
- 38 replies
-
- webserver
- raspberrypi
-
(and 1 more)
Tagged with:
-
The simplicity and scalability of PW for front end dev?
diogo replied to kathep's topic in General Support
Manlio, you know that if you don't change your avatar until the 60th post, the forum software will change it irreversibly to a random spice girl. You're dangerously close to it... -
The simplicity and scalability of PW for front end dev?
diogo replied to kathep's topic in General Support
Maybeyoustaygoodforsomeyears-withtimeyouwillgetlousyeven -
Looking much better already Edit: but the open menu occupies way too much space. In my screen I didn't see the social icons for instance, and I didn't tend to scroll down because I thought it was an overlay.
- 17 replies
-
- webdesign
- workinprogress
-
(and 3 more)
Tagged with:
-
Just had a quick look at changing the height of the top bar. You're right, it is hell.
- 17 replies
-
- webdesign
- workinprogress
-
(and 3 more)
Tagged with:
-
That syndrome belongs to clients, not designers don't let it influence you and make the logo as big as the design asks for. Look at the size of the logo here, for example http://www.chicagolshirts.com/. The client didn't ask for it for sure
- 17 replies
-
- webdesign
- workinprogress
-
(and 3 more)
Tagged with:
-
Looks pretty alive to me, but not because of the design. Minimal doesn't mean undesigned. You have to be much more careful with the details when there aren't many of them. Don't add more details but pay special attention to the ones you have already. Work harder on each one of them, see very well designed websites and try to figure how they solved the small things, try different solutions for each detail. From a first glance, I would say, choose a nice font from here —for example— http://www.haritomedia.com/best-script-handwritten-google-web-fonts/ the logo, and make it BIG, also get a nice badge for "new" http://freepsdfiles.net/web-elements/best-free-psd-badges-and-ribbons and get rid of those blocky spans under the images
- 17 replies
-
- 2
-
-
- webdesign
- workinprogress
-
(and 3 more)
Tagged with:
-
We all learn with each other. Even the forum itself learns with each one of us ps: Sorry Martijn, I couldn't resist
-
Hm, I don't think that's the situation right now, with the amount of psychologists that didn't find a job after studies and want to open their own business as an alternative to shift career... I would say it's pretty much like with any other profession actually.
-
Nice! We've done once a site for psychologists and we're currently building another. I have to say that the research was painful. The sites are generally very bad, and the images are either very negative or feel completely fake (like, simulated happiness), and usually with terrible metaphors. I don't know if you had something to do with the choice of images, but I like these I was going to write the same as Adrian. And I will add that the animations from the info boxes in the slideshow behave a bit funny.
-
To make it clear, there are two suggestions here: The first is to keep the folder scheme that you have now and symlink the wire directory. You don't have to configure anything on apache because it seems that this is how it's working for you already. This would look like: home web1 public_html wire (the real one) site etc... web2 public_html wire (link to the first wire) site etc... web3 public_html wire (also link to the first wire) site etc... The second one is to use the multisite technique that I referred before. For that you will have to configure the host (on your computer and server) to point all domains to the same folder. I'm not going to explain how to do this because it depends on your system, but already gave you the words that I would use to search for it on search engines. This solution will take some effort from your part to learn something about setting virtual hosts, and I wouldn't recommend it if you're not willing to look for that information for yourself. Anyway, once you set up your server to point all domains to the same folder, adding a new site is as easy as creating a new DB, copying a new site folder from the PW zip and naming it to "site-something", and adding it to the index.config.php file as described before.
-
It's all on the field's settings. Go through them and you'll find it.
-
You can use url segments on the homepage to achieve this https://processwire.com/docs/tutorials/how-to-use-url-segments/ Go through it, and tell us if you don't know how you can use them in this case. We'll jump in and explain. edit: In some way you would be doing a simplified version of what is being discussed here: https://processwire.com/talk/topic/8894-how-to-implement-the-url-like-wordpress/
-
I think a balanced solution would be staying in the middle of both solutions discussed. Create pages for the years and use the url segments on those pages instead of the parent "posts" page: posts 2015 <-url segments would be used on the template for these pages post5 post4 post3 2014 post2 post1 This would make it easier to use the "posts" for listing the posts and use the year pages only for the purpose of displaying the individual post pages. Also, you could reduce the url segments to 3 (the default) instead of 4. You don't really need to use a range of timestamps to decode the url. All you need for getting the right post is the last segment (the name), and you can use the day and month to validate the page, by confirming that they match the post's date and throwing a 404 when it doesn't. The reverse (creating the urls) is just as easy. You can, for instance, display the parent's url (mysite.com/2015/), add the month and day using the posts date and PHP's time function and add the post's name in the end. I'm not giving code examples because you said you would like to write your own code for learning purposes
-
Not a problem in this case. You would use the template of the parent page, "posts" in this example: Posts post1 post2 post3 The post pages themselves wouldn't need a template, since they wouldn't be shown directly. The only problem I see with this approach is that you wouldn't be able to use the $page->url method for getting this pages, but create your own method to generate the new urls Anyway, I'm not sure that these WP urls are really better than mysite.com/posts/post-name
-
I agree, this would be a mess for the user
-
Seriosuly? See here: Google "apache localhost subdomains" to know how to do this.
-
Best thing to do is to add it to a template and print_r() it from a template file to see what kind of result you get