Search the Community
Showing results for tags 'concept'.
Found 3 results
-
First of all, Merry Christmas everyone. Because someone in our company recently suggested to try out Craft CMS, I have played around with their online demo, and was pleasantly surprised. PW has most of the Craft features already, and much longer. Much of what they advertise as unique features is pretty much standard in PW-land (and open-source, too). However, there is a thing they call Matrix*, which (afaik) PW can't do (correct me if I'm wrong). In editing mode, you are able to select / add / re-arrange any kind of input field, however you want. With most input types, you can further customize it (e.g. place the content block left, center, right or full width). Perhaps that's not a feature every type of site needs - most of the time I guess having a fixed set of input fields and a certain predefined frontend element-order is enough. Another feature I found impressive is live preview. You get a split view: left the admin edit view, and right the frontend page. Though that is impressive, I found it rather something "nice to have" than essential. Now my question to all PW-devs: Is there some kind of technique / module that would enable the "Matrix" functionality in the PW-editor? I've purchased ProFields, and played around with it. I was hoping to construct something like the Matrix with either Multipliers, PageTables, or any of the other relatively new modules/fieldtypes. Perhaps I missed something crucial - I don't visit the PW forums as much as I used to - so if you know of any tutorial, module, PW profile etc. that would allow this kind of editorial flexibility, please share it. I know I could probably add custom WYSIWYG buttons. Or use Hanna Code. But that wouldn't come close to the nice UX the Matrix offers. * If you don't want to setup a Craft demo, here's a video (oh, and in case this sounds like an ad for Craft - it's not. I am just genuinely curious.)
-
Hello, in my project I have about 20 different content types eg: - basic item - news item - publication (image, description, view restriction etc.) - gallery - video file - document (file pdf, docx...) - project (project start date, project end date...) - manager profile (image, CV, position...) - company (company profile, products category...) - event (event date, location ...) - etc... Also there are shared content with additional templates ("widgets/blocks") where I have about 15 types of widgets (weather module, image banner, text banne, slider, header, link button, notification popup etc...). To reduce number of templates I create "category" template (for main content), and category template can show "list of news", "list of publications", "list of documents", "list of galleries" etc... Also category can have as child another category. Problem is that on some "list" need to show or hide some fields, need different number of items/per-page, need different sorting etc. If I use Ryan "Skyscrapers" concept and create pairs of templates eg: news -> news_item events -> event notifications -> notification galleries -> gallery videos -> video documents -> document publications -> publication projects -> project managers -> manager companies -> company discounts ->discount etc... In that case I will have very big number of templates/files (~40) but don't need many switches/flags. I really like option with "category" template, because it reduces number of templates, but on the other need to have switches ("show date", "sort (front) by..." "number of items"). Also additional "price" for that is bigger number of fields (page select). Also as small note, I don't use "hard core" checks in code (eg. by ID, template name, parent etc..) because I want to avoid administration mistakes/errors, and also to get much as possible flexible management in backend. What is your suggestion to reduce number of templates when you have many totally different content types? Right now I can see these options: 1. templates without files and "include/layouts"concept -> "fat logic" / "_func.php" 2. use files for everything -> "fat templates folder" 3. combination 1+ 2 -> chaotic (my current situation) Thanks and regards, Sasa
-
Hi guys, recently, I'm reading Stephen Hay's "Responsive Design Workflow" and am fascinated by its idea of "Content reference workflows". In short: this approach does not use any software like OmniGraffle, MS Visio, etc. but plain HTML. This way the wireframes can be responsive (and be created quickly since one is at home in HTML anyway). The other thing is, that these type of wireframes are very minimalistic and, instead of a detailed graphic-design-like approach, it more or less uses two colors, borders and labels. So the danger of mistaking these wireframes as a design proposal is minimized. And since metaphors are always good I tried to tweak this philosophy with a well known instrument of the "analogue" world: blueprints. This way, at least thats the intention, it becomes even more clear for the customer that this is an abstraction. If you communicate it right, for example with a explainatory popup/modal, no customer ever should misunderstand it and ask: "What? My website is meant to be blue?" Find some screenshots below and a demo of what I'm aiming for here: http://demo.marcus-herrmann.com/blueprint-wireframes/ Before I confront any more customers of mine with this approach I would be very thankfully to hear any feedback on this from fellow developers. What is your (or your employer's) approach on this? Are there any obvious quirks with this one? As usual, you can find the code on GitHub: https://github.com/marcus-herrmann/blueprint-wireframes Have a nice weekend! Marcus
- 1 reply
-
- 3
-
-
- wireframes
- concept
- (and 1 more)
