The only difference to default is that I have restricted cpanel web services and webdisk by disabling TLSv1_1 (as pere zeros and one)
These are the current changes I have made. The rest of the relevant cipher settings are left as default
This is a collection of resources and software I have come across to help me reset Windows 10 profile passwords. These techniques will also work on other versions of Windows but I am aiming and Windows 10 with my examples.
- Updated to [OpenWrt Wiki] OpenWrt 21.02.1 - Service Release - 25 October 2021
- This is currently on for pre-DSA firmwares, but I am sure it can be adapted
- The BT Home Hub 5A WiFi driver is not capable of bridge mode so we use Client mode and this is why we have to use RelayD to perform a type of masquerading on the WiFi client IP.
- I do not know if the new DSA firmwares will allow proper bridging without RelayD
Disclaimer: This setup has not been tested with IPv6 or extensively tested in the wild apart from my setup here, so if you are relying on this being secure you need to test it yourself before putting it into service
The following instructions will turn your BT Home Hub 5A/Plusnet One OpenWRT router into a WIFI client which has the following features:
Why?
On my test bench where I work with client laptops and PCs i need a secure network so infected computers do not attack my computers with virus, but I also have a netowrk laser printer that is not wifi capable. So i connect my printer to the red socket on my primary network allowing me to print whilst i can use the yellow ethernet sockets for an isolated network for working on client machines.
This configuration can be adapted for your needs, some people might only want 'Bridge Mode' and by following my instructions you can have that. I quite like the fact you can change the setup of the networks by jsut changing the VLAN tags (except for the AP, i need to check this)
Requirements
Here we are going to set the groundwork for this project.
I am going to use the 5GHz radio because my parent router is a 5GHz router and this will give much better connection speed than the 2.4GHz.
We now are going to configure the OpenWRT to have a secure NAT'ed network and this will run on the yellow yellow LAN sockets. Make sure you follow each section below in order.
My parent WiFi SSID is openwrt_5g
These rules only need a few changes because they are already geared up for NAT and all of the preconfigured Firewall rules are applied to these zones so we should keep them for the NAT WIFI Client
We will be re-using the rules that are already present to preserve all of the preconfigured rules for extra security. They might not all be needed, however if you do not want any of them, then delete the rules and just add the new zones with the settings below.
Edit LAN Zone
Edit WAN Zone
You have now configured your OpenWRT router to act as a WiFi client on your parent network via NAT on the yellow ethernet sockets with the interfaces and firewall rules are clearly labelled
This allows us to extend your parent network to your OpenWRT router. This will work alongside the NAT WiFi Client network we just configured or as a standalone by just using the red socket on a separate VLAN.
- relayd does not currently support IPv6
- relayd is NOT a true bridge
- How the 'Relay Bridge' works
- Masquerade = NAT.
- Not all OpenWRT devices have bridge capable drivers.
- The 'Relay Bridge' bridges 2 networks together because OpenWRT cannot do this natively.
- The 'Relay Bridge' masquerades the Interface IP on the donour network (i.e. WWAN) to be able to pass and route the traffic to the target network (i.e. BRIDGE_LAN).
- The 'Relay Bridge' allows some broadcast traffic through the networks, but it is limited to DHCP (I think).
- The local addresses on the BRIDGE_LAN even though they are on the same subnet as the WWAN, the traffic is always masqueraded through the WWAN IP.
- This behaviour can cause issues with routing specific IPs with kit such as pfSense being given the WWAN Ip and not the Device IP.
According to OpenWRT, the open source drivers of this router they use do not support native Client Bridge so you have to use a software workaround using relayd which required the following packages to be installed:
A useful video to watch, the OpenWRT version is an old version but it should help with any issues, How to set up openwrt to be a wireless receiver [Bridge] with Relayd - YouTube
Extra software/packages are required to bridge the networks. We will now install them.
We now need to create a firewall zone for the bridge LAN network
The bridge network needs interfaces creating so the router know where to talk to the network.
This is the invisible routing node that relayd provides but it does appear as an interface.
Cannot access router from BRIDGE_LAN
- With this configuration you cannot access the router from the BRIDGE_LAN
- If you add an IP to the BRIDGE_RELAY or BRIDGE_LAN routing will break.
- If anyone works out the solution please let me know.
If you have spent time configuring your router and find that you need to connect BRIDGE_LAN to your 'Parent Network' via the ethernet because of a bad WiFi signal or you just need more speed then that is easy to do.
You cannot have the router sending traffic to the 'Parent Network' whilst getting the 'Parent Network' from the ethernet as this will casue a broadcast storm so we need to correct this with the minimum intervention.
I will be investigating VLANs and how to apply them to my 'Primary Router' and it's WiFi so this network is further isolated.
I now need to isolate the NAT network (nat_lan) from my main network because both networks are present on the OpenWRT router, and OpenWRT will always try and figure out the best route for all traffic which is undesirable in this case.
This is different from Wireless client isolation.
Solution
The fix is simple, we need to configure the Firewall Traffic Rules by adding some additional rules.
Adding a Firewall Rule
- A copy and paste list is at the bottom for those of you more familiar with OpenWrt
- Add each following rules, in order, into LuCi.
- The following rules need to be added at the top of the 'Firewall - Traffic Rules' List (LuCi)
- When you re-order rules in LuCi you need to click 'Save & Apply'
Block 'Parent Network' IPs
Currently if you ping an IP address on the 'Parent Network' from the NAT_LAN network you will get a response because the device on the 'Parent Network' will only see the IP address of the officerouter (192.168.1.2) and will not know the difference (IP Masquerading). Not only can you ping devices, you can make connections for such things as file sharing and in these modern times if an encryption malware can see a share, it will encrypt it.
Allow LuCI from the WAN
These rules just allow access to the officerouter's LuCI from the 'Parent Network' via the WAN route on 192.168.1.2
This a copy on the whole file (/etc/config/firewall) to make things easier and quicker.
Once you have updated your firewall config reboot your router.
config defaults option input 'ACCEPT' option output 'ACCEPT' option forward 'REJECT' option synflood_protect '1' config zone option input 'ACCEPT' option output 'ACCEPT' option forward 'ACCEPT' option name 'nat_lan' list network 'nat_lan' config zone option name 'wan' option input 'REJECT' option output 'ACCEPT' option forward 'REJECT' option masq '1' list network 'wwan' config forwarding option dest 'wan' option src 'nat_lan' config rule option src 'nat_lan' option target 'REJECT' option dest 'wan' list dest_ip '10.0.0.0/8' option name 'Block - WAN - Class A IPs' list proto 'all' config rule option src 'nat_lan' option target 'REJECT' option dest 'wan' list dest_ip '172.16.0.0/12' option name 'Block - WAN - Class B IPs' list proto 'all' config rule option target 'REJECT' option src 'nat_lan' option dest 'wan' list dest_ip '192.168.0.0/16' option name 'Block - WAN - Class C IPs' list proto 'all' config rule option target 'ACCEPT' option proto 'tcp' option dest_port '80' option src 'wan' list dest_ip '10.0.0.3' option name 'Allow - WAN - LuCI (HTTP) ' config rule option target 'ACCEPT' option proto 'tcp' option dest_port '443' option src 'wan' list dest_ip '10.0.0.3' option name 'Allow - WAN - LuCI (HTTPS)' config rule option target 'ACCEPT' option src 'wan' option proto 'tcp' option dest_port '22' list dest_ip '10.0.0.3' option name 'Allow - WAN - SSH' config rule option name 'Allow-DHCP-Renew' option src 'wan' option proto 'udp' option dest_port '68' option target 'ACCEPT' option family 'ipv4' config rule option name 'Allow-Ping' option src 'wan' option proto 'icmp' option icmp_type 'echo-request' option family 'ipv4' option target 'ACCEPT' config rule option name 'Allow-IGMP' option src 'wan' option proto 'igmp' option family 'ipv4' option target 'ACCEPT' config rule option name 'Allow-DHCPv6' option src 'wan' option proto 'udp' option src_ip 'fc00::/6' option dest_ip 'fc00::/6' option dest_port '546' option family 'ipv6' option target 'ACCEPT' config rule option name 'Allow-MLD' option src 'wan' option proto 'icmp' option src_ip 'fe80::/10' list icmp_type '130/0' list icmp_type '131/0' list icmp_type '132/0' list icmp_type '143/0' option family 'ipv6' option target 'ACCEPT' config rule option name 'Allow-ICMPv6-Input' option src 'wan' option proto 'icmp' list icmp_type 'echo-request' list icmp_type 'echo-reply' list icmp_type 'destination-unreachable' list icmp_type 'packet-too-big' list icmp_type 'time-exceeded' list icmp_type 'bad-header' list icmp_type 'unknown-header-type' list icmp_type 'router-solicitation' list icmp_type 'neighbour-solicitation' list icmp_type 'router-advertisement' list icmp_type 'neighbour-advertisement' option limit '1000/sec' option family 'ipv6' option target 'ACCEPT' config rule option name 'Allow-ICMPv6-Forward' option src 'wan' option dest '*' option proto 'icmp' list icmp_type 'echo-request' list icmp_type 'echo-reply' list icmp_type 'destination-unreachable' list icmp_type 'packet-too-big' list icmp_type 'time-exceeded' list icmp_type 'bad-header' list icmp_type 'unknown-header-type' option limit '1000/sec' option family 'ipv6' option target 'ACCEPT' config rule option name 'Allow-IPSec-ESP' option src 'wan' option proto 'esp' option target 'ACCEPT' option dest 'nat_lan' config rule option name 'Allow-ISAKMP' option src 'wan' option dest_port '500' option proto 'udp' option target 'ACCEPT' option dest 'nat_lan' config rule option name 'Support-UDP-Traceroute' option src 'wan' option dest_port '33434:33689' option proto 'udp' option family 'ipv4' option target 'REJECT' option enabled '0' config include option path '/etc/firewall.user' config zone option name 'bridge_lan' option input 'ACCEPT' option output 'ACCEPT' option forward 'ACCEPT' list network 'bridge_lan' list network 'bridge_relay' config forwarding option src 'bridge_lan' option dest 'wan' config forwarding option src 'wan' option dest 'bridge_lan'
To get the most out of this tweaked OpenWRT router I am now going to add a guest WiFi network called 'Clients' which will be attached to the NAT network affording it all of the same isolation as that network.
We need to create a an AP on the 2.4GHz kit and bridge it to the NAT network
In pre OpenWrt 20.00/pre-DSA we were able to join the eth0.1 and wlan1 networks directly with in the nat_lan interface but this now not currently possible because it requires extra coding to be implemented in OpenWrt 20.00+ by the OpenWrt team, if ever.
These settings were located at (Network-->Interfaces-->NAT_LAN (br-nat_lan)-->Edit -->Common Configuration-->Physical Settings)
It should be noted when you try and setup a bridge device (Network-->Interfaces-->Devices) you are told that you cannot bridge WiFi and ethernet as you once did. Look at the 'Bridge ports' dropdown.
To resolve the missing bridge functionality we have to change the nat_lan device from eth0.1 to br-lan which also sort of follows the rule above. You cannot connect the WiFI to the following devices and have any routing happen. I also thinky the device must be a 'Bridge Device'.
- Traffic will now flow from the wireless on wlan0. My understanding that this traffic by default on br-lan should be on vlan1 so should still be isolated from eth0.2
- Rebooting the Router several times can sometimes help. It possible it to do with assigning new MAC addresses (my guess)
We are going to create a new 'Bridged device' (Virtualised Interface) that we can use to sit the WiFi and LAN on.
- There is currently a bug where if I delete br-lan and use br-nat_lan (or other name) to connect to eth0.1 then routing on the ethernet stops. This could well be to do with the migration to DSA and that br-lan is hardcoded somewhere to talk to eth0.1 so only use the method below for other VLANs and leave br-lan as is. Maybe a MAC addresses issue.
- You cannot have 2 'Bridge devices' on the same 'Bridge port(s)' as it breaks routing.
- You cannot have a 'Client mode' and an 'AP point' defined on the same Wireless interface, this breaks routing.
Notes
Name the VLANs for easy management
By changing the VLANs to which the ethernet socket belongs to you can change their network assignment.
There are 2 options to select from and just depends on what configuration your want
Option 1
All of the yellow sockets are on your secure 'clients' network and the red socket is on your private network.
Option 2
All of the yellow sockets are on your 'Private' network and the red socket ins on the 'clients network
If all is working set your admin password
I advise you to run through the following test to make sure that the different networks are blocked from each other as they should be before trusting this setup.
This are notes for a workaround for BT Home Hub 5A / Plusnet One to be able to access the LuCI admin and SSH services on the OpenWRT router on the bridged network.
General
Tutorials
Firewall
Distributed Switch Archeitecture (DSA)
This is replacing swconfig which uses the LuCI item (Network --> Switch)
Specifies the wired ports to attach to this bridge. In order to attach wireless networks, choose the associated interface as network in the wireless settings.
The vlan settings back in the days (eth0.1, eth0.2 and so on) where the
only way to separate the ports of the switch. With DSA the vlan hack
isn't required any longer. The whole idea of DSA is to expose each
switch port as a network device.
Mathias
Network
Bridge Tutorials
WiFi/Wireless
Still got questions, then hopefully they should be answered here. This is basically the research I used to make this series of articles.
General Alias Articles
Profile Images
Delete a Gmail profile picture
Forwarding Gmail email
Migrate my Android phone to new Gmail account
Delete an Android Calendar.
Google Play - You Don't Have Any Devices
Wipe contacts on my android phone but not from my Google account
Android Samsung Notes / S-Memo
How to Sync Google Calendar with Outlook
Google Play how to see my purchased apps
Gmail Aliases
Moving Google Services to another account
Moving Google Analytics Property
YouTube Channel
Google Maps vs Google Places
Feedburner
Moving an xbox profile
Move an email alias between Microsoft accounts
There is an element in risk because the aliases become available immediately after release or up to 30 days. Read these articles to decide.
Microsoft/Outlook.com aliases
Change Xbox Gamertag
Xbox Gamerpics
Installing Skype (not from the store)
I do not want to install skpe from the store because I do not want to login into windows with my Microsoft account.
Delete a Skype account
Things have changed now. If you have an old skype account you have to link it to a Microsoft account and then delete the Microsoft account which will delete both.
Change a Skype Username
The answer is you cannot. It is tied into your Microsoft account. I do not know if changing your primary alias will change your skype username.
What is my Skype ID
Multi Skype
outlook.com emails going into spam
Where to view my Microsoft/Xbox support requests ?
Close a Yahoo Account
Delete a Flickr Account
You can delete a Flickr account without deleting your Yahoo account and then create a new Flickr account if you want.
Forward Yahoo email
Switch between Classic and Basic Yahoo Mail
Yahoo Aliases
Flickr General
Change Flickr Screen Name / Real Name
Facebook app namespace is “Already used by some other app”
When I followed the instructions from EasyBlog I got this error. It is caused by the namespace easyblogapp is already used and you need to add your website.
Facebook app namespace is "Already used by some other app" - Stack Overflow
and
why I am unable to add apps domain to my app ? | Facebook Help Community | Facebook
Create a Facebook Page
Delete posts from Facebook
Facebook Instant Articles
General
Username
Gravatar
Change a GitHub username
Disqus
OneSignal
So your blog is now all setup, you have you Online Social Identities at the ready, autoposting and other integrations are all done and the question you are asking is: What now?
I will outline some of my thoughts on what is next but you have to appreciate that I have only just got to this stage myself and I have used the process of building my own blog to create these instructions to help me and othersas I go.
What not to do
This is important to get a well liked blog by both Google and the general internet public:
Don’t be scared to changes things
Social Marketing / SEM
Now you have your site up and running your need to advertise it or push it, 'just because you build it, does not mean they will come’. It will take a while for Google to find/index your new site/blog and this is especially true for new domains.
Newsletters
Monetise
General Advertising methods will be discussed in another tutorial.
Just some general ideas that need a mention. I might add to this as I go.
long articles: pagination / long page / separate articles
when you have to split an article into many parts, it is acceptable to use 1 folder as you might reference the same image through the article, imagine an article like 1 large word document.
All images and media will be stored in
This is a worked example of blog attribution ssing this orginal source Article - Repair a Broken Ethernet Plug: 10 Steps (with Pictures) | instructables
I will not descibe how to config every feature in EasyBlog and Komento, however below is a list of the main interaction features I would setup.
These features tend to focus on user interaction and social integration and just because you set all of these features up does not mean you have to use them but makes life easier to turn them on at a later date.
I think one of these will belong to facebook ssytem and one to facbook author
Now you have read all my research let’s just review what has been said and then read the final conclusions.
Unless you want to use WordPress as a dedicated blogging system there is only one system you should use for Joomla, Easyblog. Easyblog has additional features such as remote blogging, inbuilt commenting, automatic Twitter and Facebook posting, Team Blogging, configurable URLs and much more rather than just dealing with the content. The beauty is you do not need to start finding additional plugins to do all the basics as you would with Joomla (only) or K2. There are other blogging systems for Joomla but they are paid and even so Easyblog seems to get the most votes and support. I can highly recommend the support, second to none.
My choice: Easyblog
Reasons: Lots of social integrations, configurable URLs and excellent support. Best blogging system for Joomla by far.
Local
If I were going to use a local commenting system I would choose, kommento. I would choose this over Jcomments. Komento it is well supported and has extra features such as automatic comment moderations, technology borrowed from WordPress. It is also made by Stakideas, the same producer as Easyblog. There would be no lag in displaying comments as they are stored in my database.
Remote
There is only one kid on the block for this, Disqus. It is everywhere and you can control comments from multiple sites in one control panel. The downside is the comments are not stored on your website. The comments are Ajax driven and Google has only really just started indexing them.
My choice: Komento
Reasons: Well designed, allows my to control comments from different areas on my website and the comments are stored locally.
This is a simple one to answer because I am runing a website with more than a blog on it and it is 2018. but for completeness there is another option if you are runngin a company website giving 2 options
My choice: non-www
Reasons: It is 2018 and QuantumWarp is more personal than corporate.
Again because it is 2018 and security and privacy is an issue an easy one to answer for all types of website.
My choice: https
Reasons: This is required for good ranking and security.
One thing to consider is whether your blog is a dedicated blog, personal blog, company websitee witha blog.
My Choice: /blog/
Reasons: QuantumWarp is more personal than corporate and I have other stuff on my website.
The only options I would consider are the following basic structures
Date Based: If you do 5 articles a year why would you need to divide your articles up in too months and days? The answer is you wouldn’t and just using the year would probably be ok. For medium article volume sites using the year and the month seems enough this also seems quite popular online. See my notes from earlier on deciding the segmentation based on article post frequency for more information.
If you move your articles from category to category its URL will not get affected and therefore any link juice pointing to that page or indeed incoming links will not be affected. However if you change the article title it would be.
Article Tiltle Only: This URL structure is the simplest and a few large online blogs use it. Again like option 1 changing of an articles category will not affect it and so this is quite resilient. The articles are not arranged by a date in the slug but search engines do not really need this information in the slug anymore.
Not having category information in the URL does not seem to cause many online blogs issues.
My choice: https://www.mydemosite.com/{article_title}
Reasons: This slug is resistant to category change and is a popular method.
NB: This is only required if your bloggin system does not have an inbuilt method of handling assets.
Now this might sounds a really stupid thing to consider but when you are creating your blog articles you want to know where to put the images because of rules rather than having a guess each time or randomly creating a folder or worse, just dumping files anywhere. At first these methods will save you time but the longer you do it the harder it will be to find images, what to call folders and so on... until you wished you started doing things properly in the first place. After research I have came up with an excellent method for storing your images. It is expandable and prevents folders from becoming infinitely full (which can be a pain when enumerating folders with an FTP software) See my notes from earlier about deciding the segmentation level based on article post frequency where you should of already decided what level you requrie.
Again like URLs they can be slightly tweaked to match your needs. The above URLs use Joomla’s image folder as their root as do most content driven stuff in Joomla. I have denoted the blog content with its own folder. These URLs are to be used irrespective of how you actually set you SEF URLs, but that does not mean you cannot match them i.e. if you use in both /{year}/{month}/{day}/{article_title}/.
If you start off with just using the year you can always add in a month folder later if you find you are writing to much content for 1 folder. At the very least you can run with just the year, for one year and then after that start adding in month folders to accommodate your extra writings.
As for the article title, once you have finished tweaking the article you are not likely to ever want to change this, and in the unlikely event you need to alter the article and altering its links will not be the end of the world.
My choice: images/blog/{year}/{article title}
Reasons: My website will only a have a small posting frequency of high quality articles.
This is an overview of what I have chosen and will act as a checklist for my future blog developements.
My Choices
- Blogging System: Easyblog
- Commenting System: Komento
- Domain Prefix: non-www
- Protocol: https
- Location: /blog/
- Slug: /{article_title}
- Asset Storage: images/blog/{year}/{month}/{article_title}
- Full URL: https://mydemosite.com/blog/{article_title}
Commenting is very important for a blog it allows your audience to engage with you and your content. One other advantage is sometime other people can help you improve your content by spotting mistakes or giving you enhancements. I would always want comment system on my blogs.
There are basically 2 types of commenting systems, Local and Remote which i will now go into more depth below:
This is where the software and the comments are made, stored and maintained on your website. Some blogging systems come with commenting inbuilt and these enough for most people. Then there are the more complex commenting systems you can use to upgrade or replace default one or just install because you don't have one. Some of these systems can have some online services for auto moderating comments integrated to reduce spam, remove bad words and other such things but they do not store any data in the cloud but just the processing power of these services and then store the comments locally on your server after processing.
Pros | Cons |
|
|
This is a new and growing trend in the social internet. I will just list the main pros and cons of using one of these services:
Pros | Cons |
|
|
Apart form Disqus all of these commenting systems are for Joomla only.
K2 has its own internal commenting system
Pros | Cons |
|
|
Easyblog comes with its own in-built commenting system. It is similiar to Komento but i dont think it has all of the same functionality.
Pros | Cons |
|
|
This is a paid for extension from Stackideas, the makers of Easyblog and is constantly maintained.
Pros | Cons |
|
|
This is the orginal commenting system for Joomla and is free. It does not seem to be actively maintained anymore but still works.
Pros | Cons |
|
|
This is a cloud based commenting system that is free to use and offers the possibility of advertising revenue. However on large traffic sites you do have topay to use the service. End users never have to pay it is just for the website owners taht the costs can creep in. You need to take this into account if your website is going to scale up. For small websites using this service is an option.
Pros | Cons |
|
|
After reading all of this information, answers to the following questions will allow you to choose the commenting system you want to use:
Do I want local or remote comments?
Followed by:
Which blogging system am I going to use?
Visit loads of online and large blogs and examine their URLS to see how everyone else does it and then consider which is the best format for your blog. URL research online, is a great way to work out what URL you want to use
Below is my research of various blog sites and how they setup their URLs and asset storage.
I will list here the various CMS systems and their URLs. This will help to see what other people use and why.
URLs are purely controlled by the following things. This allows a lot manual control but can be time consuming.
URLs are purely controlled by the following things (same as Joomla). This allows a lot manual control but can be time consuming.
Below is the list of Easyblog URL options and I will go through each one.
Easyblog URL Pros and Cons
URL setting | Pros | Cons |
Default http://yoursite.com/menu/view/title |
|
|
Date Based http://yoursite.com/menu/view/year/month/date/title |
|
|
Category Based http://yoursite.com/menu/view/category/title |
|
|
Category & Date Based http://yoursite.com/menu/view/category/year/month/date/title |
|
|
Simple http://yoursite.com/menu/title |
|
|
Custom http://yoursite.com/menu/view/{%year_num%/%month_num%}/title Available values for custom SEF:
|
|
|
Overview Pros and Cons of Easyblog URLs
This will give an overview of the Easyblog URL setup because it has so many different internal options
Pros | Cons |
|
|
Now we will look at the WordPress URL options and list them here. WordPress calls SEF links Permalinks.
Primary URL Option
URL/Permalink Setting | Pros | Cons |
Plain http://www.yoursite.com/?p=123 |
|
|
Day and name http://www.yoursite.com/2018/02/18/sample-post/ |
|
|
Month and name http://www.yoursite.com/2018/02/sample-post/ |
|
|
Numeric http://www.yoursite.com/archives/123 |
|
|
Post name http://www.yoursite.com/sample-post/ |
|
|
Custom Structure http://www.yoursite.com/%year%/%monthnum%/%day%/%postname%/
|
|
|
Wordpress Optional URL Settings
If you like, you may enter custom structures for your category and tag URLs here. For example, using topics as your category base would make your category links like http://www.yoursite.com/topics/uncategorised/. If you leave these blank the defaults will be used.
Conclusion
As you can see, WordPress allows very specific configuration of its URL structure. This is by far the most configurable URL system. Most people running blogs use only the primary URL option as it suits most needs.
All of the URLs above (before adding ‘Category Base’ and ‘Tag Base)
Pros | Cons |
|
|
Planning your URLs is very important, it is how search engines access and index your website. You cannot change an established link without consequences but it can be done if needed. How often have you added a link to your bookmarks only to come back to it later to find the page is no longer there. I am trying to avoid this situation by having good planning.
Using the information from the research above I made the following notes and my Joomla Blog Software research
I recommend to use one of the following, no date or category in the url. However if you choose to use wordpress I would read the 'How many articles will you write?' section.
We now have addressed what URLs to use for the articles and blog but the articles will most likely have images or assets that need to go somewhere. The rules to where you store your article assets are separate to the URL format however they could match depending on your setup.
This is my attempt to create a generic system for storing your files and will reflect the frequency of new articles created in your blog and these rules really come into their own when the system you are using does not have an automatic system for handling assets. Using these rule will require you to manually place those assets according according to the rules unless you can configure the system you are using to follow these rules. These rules can be applied to systems that are not blogs.
The reason for these rules are:
How many articles will you write?
Before making your selection you should figure out how many articles are likely to be created on your blog. You can use any of these levels for any amount of articles but there is no point in overcomplicating things so these guidelines below will help you determine what the level of folder structure that is required to keep your files organised and prevent a single folder becoming bloated.
Once you have picked a level, you need to stick with it for a year. Come the next year you can then choose upgrade/downgrade/same depending on the amount of articles you have done or have not done. Doing this keeps all your files in order and maintains the 'year' container so the rules are not swapped mid-stream causing issue about which rules to follow.
You now need to check over the information and select which option is best for you:
Asset Location |
Pros | Cons | Notes |
images/blog/ |
|
|
Don’t use this one. |
images/blog/{article_title}/ |
|
|
|
images/blog/{category}/{article_title}/ |
|
|
|
images/blog/{year}/{article_title}/ |
|
|
{year} = 2013, 2014, 2015 Ideal format for small sites |
images/blog/{year}/{month}/ |
|
|
|
images/blog/{year}/{month}/{article_title}/ |
|
|
{WordPress format} 2013/08 Ideal format for medium sites |
images/blog/{year}/{month}/{day}/{article_title}/ |
|
|
{WordPress format} 2013/08/31 Ideal format for large sites |
images/blog/{article_id}/ |
|
|
|
images/blog/{category}/{article_id}/ |
|
|
|
images/blog/{year}/{article_id}/ |
|
|
{year} = 2013, 2014, 2015 Ideal format for small sites |
images/blog/{year}/{month}/{article_id}/ |
|
|
{WordPress format} 2013/08 Ideal format for medium sites |
images/blog/{year}/{month}/{day}/{article_id}/ |
|
|
{WordPress format} 2013/08/31 Ideal format for large sites |
Table Notes
Because I use Joomla I need to look at all of the different blogging systems available along with commenting systems. I will assess them to see shich is the best setup.
Using Joomla as is can be an option for some.
Pros | Cons |
|
|
Conclusion
Too basic and not enough control over URLs. This might be ok for a news section of a website.
This is a Joomla CCK with lots of content features but has blogging abilities. It does not have things like autoposting to social media built in.
Pros
Pros | Cons |
|
|
Conclusion
Has more than standard Joomla such as image auto resizing and an inbuilt commenting system but is still too basic without plugins for a dedicated blog. Too basic and not enough control over URLs. This might be all right for a news section of a website.
Easyblog seems to be a blogging system with all the tools built in.
Pros | Cons |
|
|
Conclusion
Easyblog is basically trying to be a clone of WordPress running as a native component in Joomla. It has all the features of a dedicated blogging system and allows the use of Joomla content plugins. One of the selling factors of Easyblog is that you can, like WordPress, configure the URLs separate to articles and categories. Easyblog also has a lot of social integration making it an ideal choise. This is a must as you won’t lose SEO ranking or traffic because you have a reorganise.
Links
There are 2 WordPress integrations for Joomla. Both of which have slightly different reviews. There are some bridges and post copier extensions but I would not count these as use for this project.
WordPress is the go to standalone blogging platform but I am looking at this whilst using Joomla as I want all the benefits of Joomla with a Blog. You could in theory run WordPress and Joomla side-by-side with the same themes but this is extra work and would take more configurations.
Pros | Cons |
|
|
Conclusion
WordPress is without doubt an excellent blogging system but that is all it is. It is similar to Joomla in that you can use plugins to extend the platform but when you start doing this it is much easier to use Joomla. WordPress for Joomla does not allow you to use Joomla plugins for the content in WordPress and not all WordPress plugins will work. So basically if you want to use WordPress, use it but without the Joomla wrapper anything else seems pointless
Joomla Integration Plugins
Now you have read my research you can either can look at some of the other platforms on the internet or pick one and move to the next step.