HMCB

@kongondo you should consider crowdfunding this. Kickstarter or whatever. The community needs an official or reputable shopping solution and what you’re doing is so much work without a guarantee that it will pay off for you.

Just a thought but instead of diving in headfirst, maybe those interested in creating content whether articles or video should create a content outline. - Purpose of said educational piece - Overview of what students will be learning - Framework requirements (version of PW; any modules required, etc.) - Section overviews (think of this as chapter titles in a book and brief description of what’s covered) - Paid or free Those are a few thoughts. Although I am not a programmer, from a brand standpoint, I’ve watched Laravel develop from its inception. It’s been a beautiful process to watch. And it’s been successful for being opinionated and rigorous in documentation, besides paying attention to the craft of good design.

If you’d like my unadulterated perspective: I think the way PW is communicated is too verbose and complicated. The concept of Pages doesn’t make this any easier. It’s almost like that term has outlived what the product has become known for: power a website or something altogether different. Just look at the Pages overview and you see how it could be totally perplexing to a newbie. Words have meaning and sometimes wisdom requires rethinking how we communicate. Despite being new—having built three or four websites with it—I love this product and hope more people come to appreciate what Ryan has built.

I started in PW a few years back. I love what I’ve been able to develop, although most have been simple marketing websites. I’m a brand developer by trade but I’ve been doing frontend and light database/ php since the late ‘90s. My perception of PW is that it’s a real tool. You can build stuff and not have so much abstraction that revisiting a project requires a ton of time figuring out what code does. I like that because building stuff with staying power serves my clients well. I think PW attracts the kind of person who loves well crafted things; like a good Italian shoe that can be resoaled versus throwing the shoes away because they’re made cheap. I think that PW could really find a wider base if there was a learning framework. There are key people in this community, including Ryan, that could build a curriculum starting from scratch. Courses we pay for that teach us good fundamentals because there are multiple ways to get stuff done but maybe a lot of us could improve our spaghetti code. Then we could delve into more complicated stuff like writing to pages from frontend pages. Some could even involve getting best use of Pro modules. This is an investment because unlike other systems, PW is so fundamentally sound and non-changing that the information would be sound for years. Thanks for listening.

@Noel Boss interesting. And you use Amazon for your live PW sites too? Does Cloud9 let you go from development to EC2 (?) so you never leave the Amazon ecosystem? And I can vouch for Transmit. I’ve been using it for over 10 years.

Congrats on the new machine! Anytime I add something great to my workflow, it energizes me.

Very refined. It would make for a nice experience with front-end editing too. Would love to see this implemented very soon.

I’d love to see, as an option, a user-supplied character inserted between title and sitename. For instance, I usually use the pipe (|) character or sometimes a hyphen. And this character would only obviously be inserted if both title and sitename are used. If sitename isn't supplied, then the pipe or whatever gets stripped.

Why isn’t there any documentation on Markup Regions within the official docs? The only thing I could find was various blog posts. This would surely help beginners.

OK. This could have been an oversight on my end. I now see the FieldsetPage option in the dropdown when creating the field. My apologies.

I already have it installed and it's dependencies. Ultimately, shouldn't it be as easy as: Create your individual fields. Assign those fields to the FieldsetPage field. Assign the FieldsetPage field to a template. Tada…the fields show up in the page edit/create screen.

Guess I'm lost. I just installed today's Dev release (3.0.77). I create my individual fields. I then go to create this new FieldsetPage field type, but it's not there. I have to choose Repeater, then FieldSet page becomes an option BUT ONLY AFTER the field has already been created. But once I switch over to FieldsetPage as the type of Repeater, it seems to break everything. My understanding is that FieldsetPage allows me to take any fields and group them together for reuse. I can then assigned that fieldset to a template. What am I missing?

Do any of you developers refer to “pages” by any other name when you’re explaining PW to clients? I ask because it seems like the term “page” sounds fixed or dated. When I create pages that simply are look-up data (pulled into fields, etc.), they're more like a collection of data and not pages directly accessible on the front-end.

Ok. Thanks for the update. Didn't know that.

Wonder what the state of this premium module is. I think everything listed in the Premium modules page for PW should give a sense of trust. There's not activity in this forum and the last changelog goes back to January of last 2016.