rick

Thanks! Happy New Year to everyone! Be safe! I want to see everyone back here!

Hello atar, and welcome to the forums! -- Don't worry about your English. Ask any questions you want and everyone will jump in to help. Edit: Misunderstood the question.

I'll second that. Nice work on the new .pw domain

Things that make you go, "Hmmm". A few options are: 1. Using responsive tables may work, but I suspect it will yield the same results as you are trading one container for another, and the same issue as described in #2 remains. 2. You may want to use images of much larger dimensions, initially set for the largest target display resolution. The issue appears that you're wanting a subordinate element to conform to it's parent when the parent itself no longer conforms -- hence the Cascade in Css appearing to fail* after a certain point. 3. Lastly, javascript can adjust the desired elements of a certain class/id/name. This was the method commonly used to mask issue #2 before browsers learned to parse more specific css directives and windowing events, such as resizing. * Technically, css is not failing here. If you were to display a background color for each element, you will see that they occupy the desired space. The figure image should be enlarged to fill the available space to aesthetically resolve this issue.

Hi Peter, Take a look at this figcap test example and see if it is what you are looking for. I copied the portion of your original site referring to Richard for the content. I use bootstrap myself, but you could adapt your styles easily enough. All the styles are inline rather than a separate file for quick reference. I've tested this in FF, Chrome, and Opera. I don't use internet exploder so I'll leave that up to you.

Macrura, that second link under 'others' says I don't have permission to view this forum.

heldercervantesWorks great on linux with FF, Chrome, and Opera

Thanks! Merry Christmas to you and your family as well! Here's to a safe and prosperous new year for all!

I'd like to thank LostKobrakai for this excellent tutorial included in the Dec 25, 2015 blog post regarding custom page types. If you haven't read it yet, please do so. It is contributions like this by the senior members that prove selecting ProcessWire was the correct decision for this ProcessWire-Newbie. I am impressed at what I have learned within the functionality of ProcessWire, and discovering avenues I hadn't yet thought about. It is indeed a merry Christmas. I also want to thank all staff members. They deserve our gratitude for the time they dedicate to helping us learn ProcessWire, and the many avenues available with each project. For example, kongondo contribution is another great example of the team in place here. My hat is off to Ryan and his team for giving of their time and sharing their knowledge. In addition to the regular staff, there are many members, such as Kixe, Tom, (and too many others to name them all here) that also deserve recognition for their contributions and assistance. It is greatly appreciated. I am certainly looking forward to ProcessWire 2016 ;-)

Not that I would 'alter' my basic LAMP development and production machines for the sake of having new stuff, but so far PW 2.7.x and 3.x have performed without issue using MariaDB 10.x on my ubuntu 14.04 localhost and debian 8.x servers, also with custom tables/pdo. I haven't pulled the trigger on lightspeed just yet -- I'm only curious about the performance difference to apache. Again, if it ain't broke, don't fix it. I see no reason to change until there is reason to do so, such as exceeding mysql indexing limits, or apache barfin' on concurrent users, etc.

Old has been referenced way too many times in this thread. I find it interesting to observe the development methodologies preferred by the different generations. It reminds me of this...

Merry Christmas to you as well. That was one of the many CMSs I looked at before making my decision to go with ProcessWire. I'm old-school, so my requirements are far more basic than what others may think is best for development. For example, that matrix functionality, in my opinion, was one of the items that was more fluff than actual enhancement. Being old-school, I don't care for the "dreamweaver/frontpage"-esque approach to developer tools. As powerfully simple as ProcessWire is, anyone can develop whatever feature module they think may help take their ability to create to the next level. I prefer an unobstructed, hands-on approach to development, rather than adding bloat from installers, less, template engines, and any other proclaimed 'enhancement' for development. Split windows and a refresh work just fine for preview.

Nicely done! And cheers to a wonderful holiday for you and your family as well!

I like the Powered by, DaveP. I'll add this to the list.

Yeah, mine too. I didn't realize that I was a dentist, math professor, and a porn star!

Regarding a person's name, I would spell it out rather than use initials due to possible acronym conflicts. That said, it is more difficult today to find 'your name'.com available than 20 years ago. Also might want to consider whether seo is necessary. For example, whole name search results are far more 'fine' than using initials (again, acronyms). just my $.02

What do these articles (written by the 50 or so authors) pertain to? Are they entirely individual points of view of various topics, or are they supposed to be related to some corporate business practice or general industry-field? If an article is company-centric, then their 'own' design should be restricted to conform to the standards of the company. If the articles are not related to specific company practices or industry, then the author is less restricted. For example: A lawfirm would have articles (suits) that must adhere to specific standards of layout and content placement, etc., while also having articles (briefs) whose format and content are far less restricted. That same lawfirm may have established standards for each type of article (suits, briefs, etc.).

I like your process for the room archive, kongondo. The only difference I was thinking was to create the dots on-the-fly by dragging a dot-type from a legend onto the image, then having a popup dialog box where the user can add the data associated with that specific dot. So we'd have the parent image-page with child dot-pages, which contains x,y, name, description, etc. I don't have the experience with PW yet, so this would have been my initial approach.

In addition to kongondo's questions, do you want a one-to-one relationship between a user and a map? That is: Do you want each user to upload one or more maps, and subsequently add location data for each map (one-to-many), or, Do you want one map where multiple users add location data to it (many-to-one), or, Do you want one map per user (one-to-one)?

Hi heldercervantes, Just off the top of my head, there are a couple of approaches you could take. The drag and drop approach you suggested in your original post of placing a marker (pseudo-callout) is probably the most user-friendly with images whose 'content' is not consistent (ie, automobiles, furniture, etc). A page containing the image, with sub-pages containing a marker icon and associated text content for each position would be my approach, along with the drag and drop js utility. There could be other options more PW-specific that the members who are much smarter than me might be able to offer.

Nicely done! ...and thanks for the code snippet too. I hadn't looked at the InputfieldMapMarker before, but will be checking it out soon.

Hi Mats, This is nice. Are you computing the coordinates dynamically, or are you hard-coding them? If dynamic, what are you using?

I think that each of your items all relate to usability. Regardless of the user type, whether they be a content writer or casual reader, the layout must remain consistent. By that I am referring to the following (as an example, not a complete list): Menu(s): A user needs to be accustomed to accessing options in the same location, with the same visual queues (colors, icons, etc.), for all pages of a specific type. Links: All links should be consistently displayed; underscores, background colors, whatever the desired style. Images: The use of imagery is a bit more complex. For example, advertisements, figure references within articles, icons, etc., should all be consistently displayed. This requires a little bit more thought as to their creation and presentation. Textual content: Again, consistency is the key. Refer to elements using the same format, such as a list of table data or a figure image. Table data is usually referred to by reference, while a figure is commonly referred to by illustration. Example: Figure 1. illustrates the ..., or, Refer to Table 1 for a list of ... . Even article elements such as a note to the reader should be consistent in it's content and appearance. Basically, it comes down to this: A style guide should the standard for developing the site, just as a coding style guide is used in programming and a corporate standards manual is used with company creatives. The tools you as the developer provide to your users, ckeditor, page fields, etc., should be selected based on the best fit with the approved style guide. Hope this helps!

In my opinion (and that is all that it is), your categorization issue is a bit more complex than just a simple tag reference. For example, the general tag, 'Hair', as related to the 'Fashion' category, is not sufficient to determine a related post. The post context might be referencing hair-removal, while a related post based only on the tag 'Hair' could return a post with content relating to hair-coloring. While this may seem trivial at first, consider how the google dertermines content ranking. It quite possibly could harm your seo results by having 'un-related' references. Creating finer grained tags such as, Hair -> Removal, Hair -> Coloring, and Hair -> Styling, etc., would allow for more accurate relational results. Also, by having a finer-grain tagging system, it would limit the number of related posts results. Personally, I would limit the results to three related references, regardless of the number returned. /$.02

Not hosting on media temple, so can't help you there. But the site does load very slow for me too. Nice looking site, btw. The images are loading very slow, between 408ms to 951ms each, on average, each time I view the site. This is not good, especially since your image sizes (KB) are small. Just based off this info, it would appear to be an issue with the particular server. Is this shared hosting?