I tried to find what these files are used for, but couldn't find anything.
I'm making a theme for Hugo and wanted to know they are required.
Also if they are required what is their purpose?
The files I'm asking about:
themes\[THEME]\_default\list.html
and
themes\[THEME]\_default\section.html
So I found the information that I was searched for, and probably should've waited before asking, but since I already asked let me answer it for the other people.
list.html is used by Hugo to generate a page that displays a list of the pages inside the content folder. It is not required for Hugo to work, but another page would have to replace it. Most commonly this would be index.html in the layouts folder.
section.html I'm still not really sure what this is used for, but it is not required. There is a way to make a separate list.html files for a specific folders in the contents folder, but I still haven't checked out all the details about this.
I found this tutorials on YouTube by Mike Dane which may be useful although they are pretty old.
Related
so I'm having this issue where whenever I run the hugo command, only part of my website gets generated. I don't have empty files, they all have some content within. I would like to note that the specific section that isn't getting compiled is the faq section. any suggestions as to how I may fix this?
Site Structure
Generated files
The bug was caused by hugo not recognizing the layout. Although I haven't found a way to fix it, I somewhat patched it by using the default layout for the page given that I had layouts for all other pages.
I'm starting with angular.js and after reading realized that I should use ng-boilerplate to bootstrap my project. But I'm a bit confused, I've cloned the project and stuff and I have a project called ng-boilerplate with all the structure needed, but what now? Do I need to change the project name "ng-boilerplate" to my project name? And what about the folders for example "Home" and "About"? Do I need to delete these folders and create the ones I need? I guess I have to remove some code in other files right? the problem is that I'm starting with angular so don't know what should I remove and what not.
As you can see I'm pretty new with this, am I right with the procedure?
thanks
Well if you read the ngboilerplate documentation carefully you will understand it use. As the first line says:
ngBoilerplate is designed to make life easy by providing a basic
framework with which to kickstart AngularJS projects.
ngboilerplate like many other seed projects, provide a prescriptive guideline about how a project should be structured. To demonstrate the working of the setup some project like this one add implementation for some standard scenarios to highlight how the complete setup works. Remember a working sample is far better than writing lengthy documentation.
The pages that you have mentioned are indeed for demo purpose and you can remove the folders if required. What this organization is telling us is that group your model-view-controller implementation together into a folder. These folders could be one per view or one per feature. The documentation on the site itself is self explanatory here https://github.com/ngbp/ngbp/tree/v0.3.2-release/src/app
Almost all folders of ngboilerplate have some documentation around specifics of that area. Read it to learn more about it.
In my search for a good social login package for App Engine, I am giving gae-boilerplate a try. But I find there is no documentation except the readme file, which I think it is not enough at all.
I have many questions, among them:
Should the boilerplate be used as a library or download and modify as needed?
How should the boilerplate be updated?
What does each model do?
Where should my templates go?
Should I have a different routes file?
Should I derive my Handlers from BaseHandler?
In general, what things should I implement in my pages? For example, I found out that I have to include a csrf_token in all POST requests. It would have been nice to know this in advance, and the many other things that I'm having to find out along the way, and which I implement without being sure if I'm supposed to be doing that.
And some more...
My biggest problem is that Social login is not working, and I feel this boilerplate is a big monster with which I don't know where to start. To make things worse, it is hard to debug social auth from any machine that is not the production one. Thats why I'm desperately looking for some docs.
I have not found anything in SO, and I guess there must be more people in my situation. So, any pointers to documentation that could help to understand gae-boilerplate a little bit better would be very appreciated.
EDIT: I switched to gae-boilerplate in a site that I had previously working. Maybe most of my problems come from the way that I have tried to integrate gae-boilerplate and my existing site. As a result I have tried to treat gae-boilerplate as a library, and keep my own templates, handlers, static files and such.
Thank you guys!
EDIT 2: After trying other options, I have to say that I am very happy with gae-simpleauth. It works really well, and Alex's support is superb.
I will try to answer most of your questions below:
Should the boilerplate be used as a library or download and modify as needed?
You can modify it as needed based on your specific requirements.
How should the boilerplate be updated?
What do you mean?
What does each model do?
User and SocialUser are pretty self explanatory. LogVisit and LogEmail are used for auditing purposes.
Where should my templates go?
In the templates directory
Should I have a different routes file?
No, you can use the existing file for all your routes.
Should I derive my Handlers from BaseHandler?
It't not mandatory but I would recommend to do so. BaseHandler is very handy and provides a lot of good stuff.
In general, what things should I implement in my pages?
What exactly do you mean?
In general, you can use gae-boilerplate as a reference on top of which you will built your own project. Study the code step by step, try to figure out what is the purpose of each file and library used and how they work together. This way you will gain good knowledge of a lot of things like jinja templating, oauth2, etc.
Hope this helps.
my final job on my current site is trying to add multi language capability to my EE site.
The steps I followed on the wiki here: http://expressionengine.com/wiki/Multi_language_site_alternative
were straight forward enough and despite having to search around for a bit of help when the htaccess didn’t work, I now have (I believe) a working subfolder on my site: /en . If i point my browser at http://mysite.com/en/template_group/view/title a page comes up fine.
The next step however of using en_custom_field doesn’t seem to work.
I have the feeling that the /en folder is an exact mirror image of the normal site.
For example in my embedded header template I have lang=”{country_code}” but when I view source in my /en subfolder it shows as “fr” (which is the default language)
Also, other curious things are happening - in the /en subfolder, my current dropdown menu (a navee menu) has been replaced by my old menu which is no longer in my template (!) I have literally no idea how this is happening…
Would appreciate any help from anyone who's seen something familiar thanks!
Are you using ExpressionEngine 1.x or 2.x ? The instructions in the wiki really only work for 1.x (and not even very well for that).
There are several free and paid addons that can help you do this. For EE1, I'd recommend Transcribe: http://eeharbor.com/transcribe
For EE2, you might try Berkol's MultiLanguage addon, found here: http://devot-ee.com/add-ons/multi-language-support -- it requires you to create custom fields, but handles all the URL nonsense pretty nicely as far as I can tell.
So, I must be missing something.
I want to create a specific template for a Basic Page with Drupal 7. I've read about doing something like creating a file called page—mypagename.tpl.php, and putting it in the theme folder but this has not worked for me.
Can anyone provide a quick walk through for this?
Drupal makes my head hurt. :\
Thank you.
Make sure to clear your cache in Drupal after major theme changes which include adding files to the theme as above, otherwise your theme may not pick up the new files.
Last I checked, the Devel module was still buggy for D7, but if it has come along then I highly recommend using this along with the devel_themer module, it has a tool that will tell you what exactly to name your theme files for different elements (pages, nodes, fields, etc).